- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Builds, Git Integrations
- Down Index
- 33of 100
What to do
Check whether you use Vercel Builds, Git Integrations. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 6h 36m it lasted.
Anything that failed between 2026-10-12 13:35 UTC and 2026-10-12 20:11 UTC may need a replay.Subscribe to Vercel's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
Due to an upstream incident at GitHub (https://www.
Category: Upstream dependency
Read the postmortemUpdates from Vercel 7
- investigating
We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available.
provider
- identified
We have identified the issue and are working on a fix. We will provide additional updates as they become available.
provider
- identified
Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
provider
- identified
We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.
provider
- identified
Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available.
provider
- monitoring
The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-316eaef9b7
Is Vercel still down?
No, this incident was resolved 2026-10-12 20:11 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
6h 36m, from 2026-10-12 13:35 UTC to 2026-10-12 20:11 UTC, by the times Vercel posted.
What was affected?
Vercel named Builds, Git Integrations.
What caused it?
Upstream dependency. Vercel wrote: "Due to an upstream incident at GitHub (https://www." The postmortem: https://stspg.io/cfrfjg8fqxfr
Where does this come from?
Vercel's official status page, https://www.vercel-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.