- Level
- confirmed
- Worst impact
- Degraded
- Components
- Builds
- Down Index
- 16of 100
What to do
Check whether you use Vercel Builds. 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 27m it lasted.
Anything that failed between 2026-09-28 13:44 UTC and 2026-09-28 14: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.
Updates from Vercel 2
- monitoring
A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.
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-b44cad223e
Is Vercel still down?
No, this incident was resolved 2026-09-28 14:11 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
27m, from 2026-09-28 13:44 UTC to 2026-09-28 14:11 UTC, by the times Vercel posted.
What was affected?
Vercel named Builds.
What caused it?
Vercel hasn't published a root cause. If it does, it shows here.
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.