GitHub: Incident with Git Operations
GitHub outage, May 9, 2023 · 4 vendors, 6 incidents
GitHub’s incident is the root of the event (the provider’s own post). (root, posted +14 h 32 min vs GitHub’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["GitHub<br/>posted 08:07 UTC"]:::root
h4["1 to 4 hours later<br/>2 vendors, 2 blamed GitHub<br/>v0, Vercel"]:::blames
root --> h4
class root meFull 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
- 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.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub, started 2023-05-09 22:39 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Incident with Git Operations
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/wj1qbq7r9tcl
GitHub profileRecent GitHub incidentsAll outages on May 9, 2023GitHub in May 2023MarkdownJSON