RewindexOutage eventsApr 21, 2020
GitHub outage, Apr 21, 2020
10 vendors posted 9 incidents between 14:00 on Apr 21 and 02:00 on Apr 22 UTC, against about 13 incidents from 10 vendors in the same hours on an ordinary week. 4 vendors named GitHub in 3 incidents (4 of them blamed it). GitHub posted “Incident on 2020-04-21 15:45 UTC” at 15:45 UTC.
Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.
Times are UTC; lags are from when GitHub posted (15:45).
- GitHub posted 15:45
How it spread
Vendors that named GitHub, grouped by when they posted, and vendors that blamed one of the vendors GitHub took down. Solid lines: the vendor named the other. Dashed: same window, not named.
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["GitHub<br/>posted 15:45 UTC"]:::root
h1["Within an hour<br/>4 vendors, 4 blamed GitHub<br/>v0, Vercel, Travis CI, Sentry"]:::blames
root --> h1Vendors that named GitHub
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
3 vendors
- Incident, no impact listed
+0 min
Blames GitHub
v0and VercelGitHub deployment and login errors
…GitHub deployment and login errors Due to a problem with GitHub, we experienced delayed deployments made with Vercel for GitHub and issues when using GitHub login. The issue was resolved after GitHub…
- Major incident
+27 min
Blames GitHub
Travis CIDegraded GitHub integration
…Degraded GitHub integration The service are operating normally. Our services are degraded due to GitHub's ongoing issues. The service are operating normally.…
- Minor incident
+31 min
Blames GitHub
SentryGitHub related Integrations Unstable due to GitHub Incident
…GitHub related Integrations Unstable due to GitHub Incident GitHub has reported their incident to be resolved.…
Same window, did not name anyone
6 incidents started during the event without naming GitHub or another vendor. Some are part of it, some are a normal day’s background (about 13 in these hours).
Show all 6
- −1 h 26 minMinor incident
- −1 h 20 minMinor incident
- −1 h 5 minMajor incident
- −30 minMinor incident
- +19 minMinor incident
- +34 minMinor incident
Detected automatically from 5 status pages opening incidents in the peak hour (normally at most 4). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.