rewindex

CompaniesGitHubIncidents

GitHub: Disruption with Dependabot Alerts

MinorStatus: resolvededitedStarted Resolved (3.9 h)8 updateswww.githubstatus.com (opens in new tab)

Timeline of updates

  1. investigating

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating

    We’re investigating delays in some Dependabot alerts closing after affected repositories have been updated to address a vulnerability. Alert processing is backed up. We’ll share more information as it becomes available.

  3. investigating

    We’re scaling alert processing capacity to reduce the backlog causing delays in some Dependabot alerts closing after affected repositories have been updated. We’re continuing to monitor and will share another update as more information becomes available.

  4. investigating

    We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring the rollout and will share another update as we learn more.

  5. investigating

    We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring progress and will share another update as we learn more.

  6. investigating

    Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability.
    We're continuing to investigate and work to restore normal processing.

  7. monitoring

    The degradation has been mitigated. We are monitoring to ensure stability.

  8. resolved

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).

GitHub profileRecent GitHub incidentsMarkdownJSON