v0: Elevated GitHub Deployment Failures
Timeline of updates
- resolved
Between 01:15 and 05:45 UTC, customers might have experienced elevated GitHub deployment failures, including delays in triggering new deployments for commits and redeploy errors displaying the message "There is no GitHub account connected to this Vercel account". This was due to GitHub API degradations, which they have since resolved. https://www.githubstatus.com/incidents/lw6j95nyw3py (opens in new tab) https://www.githubstatus.com/incidents/02z04m335tvv (opens in new tab)
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).
Cite this
Status incident (vendor impact label: none) posted by v0, started 2026-03-12 01:15 UTC, resolved after 0 min, 1 update(s).
- Title
- Elevated GitHub Deployment Failures
- Vendor
- v0
- Date
- URL
- https://rewindex.com/company/v0/incidents/4wsjq8gn2tsk
v0 profileRecent v0 incidentsAll outages on March 12, 2026v0 in March 2026MarkdownJSON