Vercel incident

Elevated GitHub Deployment Failures

Resolved on March 12, 2026.

resolved Mar 12, 2026, 06:17 AM 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

Started
Mar 12, 2026, 01:15 AM UTC
Resolved
Mar 12, 2026, 01:15 AM UTC
Duration
–
Detected by Pingoru
Mar 12, 2026, 01:15 AM UTC

Update timeline

  1. resolved Mar 12, 2026, 06:17 AM 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

Your product runs on more than Vercel

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →