Rewindex

CompaniesGitHubIncidents

GitHub: Incident with Actions

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

Azure outage, Jan 25, 2023 · 14 vendors, 14 incidents

GitHub’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +2 h 14 min vs the first vendor naming Azure)

Swipe sideways to see the whole diagram.

same windowAzureown incident not archivedWithin an hour1 vendor, 1 blamed AzureMongoDB Atlas1 to 4 hours later3 vendors, 2 blamed AzureGrafana Cloud, Retool, InfluxData (InfluxDB Cloud)GitHub (this incident)posted +2 h 14 min
same windowAzureown incident not archivedWithin an hour1 vendor, 1 blamed AzureMongoDB Atlas1 to 4 hours later3 vendors, 2 blamed AzureGrafana Cloud, Retool,InfluxData (InfluxDB Cloud)GitHub (this incident)posted +2 h 14 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<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>1 vendor, 1 blamed Azure<br/>MongoDB Atlas"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 2 blamed Azure<br/>Grafana Cloud, Retool, InfluxData (InfluxDB Cloud)"]:::blames
  root --> h4
  me["GitHub (this incident)<br/>posted +2 h 14 min"]:::me
  root -.->|"same window"| 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

    This incident has been resolved.

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