Rewindex

CompaniesGitHubIncidents

GitHub: Issues enabling actions and running jobs on GitHub

MinorStatus: resolvedStarted Resolved (3.9 h)1 updatewww.githubstatus.com (opens in new tab)
Part of an outage event

Azure central us outage, Jul 18, 2024 · 9 vendors, 9 incidents

GitHub’s incident names Azure / central us (location or integration). (hop 1, posted +47 min vs the first vendor naming Azure)

“…r register self-hosted runners. This was caused by an unreachable backend resource in the Central US region. That resource is configured for geo-replication, but the replication configuration prevente…”

Swipe sideways to see the whole diagram.

Azure central usown incident not archivedWithin an hour5 vendors, 1 blamed AzureMongoDB Atlas, Confluent, GitHub, GitHub Copilot +1Later1 vendorContentstackGitHub (this incident)posted +47 min
Azure central usown incident not archivedWithin an hour5 vendors, 1 blamed AzureMongoDB Atlas, Confluent,GitHub, GitHub Copilot +1Later1 vendorContentstackGitHub (this incident)posted +47 min
GitHub is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Azure central us<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 1 blamed Azure<br/>MongoDB Atlas, Confluent, GitHub, GitHub Copilot +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor<br/>Contentstack"]:::names
  root --> later
  me["GitHub (this incident)<br/>posted +47 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    Beginning on July 18, 2024 at 22:38 UTC, network issues within an upstream provider led to degraded experiences across Actions, Copilot, and Pages services. Up to 50% of Actions workflow jobs were stuck in the queuing state, including Pages deployments. Users were also not able to enable Actions or register self-hosted runners. This was caused by an unreachable backend resource in the Central US region. That resource is configured for geo-replication, but the replication configuration prevented resiliency when one region was unavailable. Updating the replication configuration mitigated the impact by allowing successful requests while one region was unavailable. By July 19 00:12 UTC, users saw some improvement in Actions jobs and full recovery of Pages. Standard hosted runners and self-hosted Actions workflows were healthy by 2:10 UTC and large hosted runners fully recovered at 2:38. Copilot requests were also impacted with up to 2% of Copilot Chat requests and 0.5% of Copilot Completions requests resulting in errors. Chat requests were routed to other regions after 20 minutes while Completions requests took 45 minutes to reroute. We have identified improvements to detection to reduce the time to engage all impacted on-call teams and improvements to our replication configuration and failover workflows to be more resilient to unhealthy dependencies and reduce our time to failover and mitigate customer impact.

From GitHub’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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