Vercel reported this minor-impact incident on its official status page on May 23, 2026, 18:44 UTC. It was resolved after under a minute.
Right now Vercel is operational. Live Vercel status →
This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt
GitHub has implemented a fix, and we are monitoring the results.
We have identified the issue and are working closely with GitHub to resolve it.
We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops.
We are continuing to investigate this issue.
We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs. CLI deployments are unaffected at this time.
We are currently investigating this issue.
Our 5-minute checks didn't record a change in Vercel's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Vercel reported 24 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 59 min. See Vercel's uptime and incident history