v0: GitHub deployment and login errors
GitHub outage, Apr 21, 2020 · 12 vendors, 14 incidents
v0’s incident blames GitHub as the cause. (hop 1, posted +0 min vs GitHub’s own post)
“…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…”
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 --> h1
me["v0 (this incident)<br/>posted +0 min"]:::me
h1 --- 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
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 applied a fix.
From v0’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.vercel-status.com (opens in new tab).