Elevated GitHub Deployment Failures
Mar 12, 01:15 UTCMar 12, 01:15 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Vercel, 90 days
32 incidents
Affected
Not listed by the vendor.
Final update
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 https://www.githubstatus.com/incidents/02z04m335tvv
Timeline
- Resolved · Mar 12, 01:15 UTC
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 https://www.githubstatus.com/incidents/02z04m335tvv
More from Vercel
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1821:36 UTC | Deployment stuck in initializing state | minor | 55m |
| Sep 1820:32 UTC | Elevated Errors Triggering Deployments | major | 50m |
| Sep 1815:14 UTC | Elevated Vercel KMS and Connect Errors | none | 0m |
| Sep 1707:11 UTC | Failures delivering Logs to Drains | none | 0m |
| Sep 1616:58 UTC | Missing Web Analytics and Speed Insights data | minor | 0m |
| Sep 1603:21 UTC | Invoice Generation Paused | none | 0m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.