Incidentsby GlyphElevated GitHub Deployment Failures
Mar 12, 01:15 UTCMar 12, 01:15 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Vercel, 90 days
23 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 historyBuild delays and degraded Vercel Dashboard performancelasted 25mDelays in Logs and Observability datalasted 1h 2mIncreased build and deployment failureslasted 6h 36mDelays in Drains, Observability, and Workflow in Washington (iad1)lasted 1h 21mVercel Auth login failures for pages with Deployment Protection enabledlasted 16mElevated Sandbox error rates in Paris (cdg1)lasted 25m