- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Builds
- Down Index
- 24of 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 12m it lasted.
Anything that failed between 2026-03-31 21:11 UTC and 2026-03-31 21:23 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 3
- investigating
We are investigating reports of elevated errors when creating deployments. Existing deployments and live traffic are unaffected. We will provide updates as they become available.
provider
- monitoring
A fix has been applied for an issue where deployments were erroring with "invalid request" and we are monitoring the results. We recommend redeploying any failed deployments.
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-5cc063125d
Is Vercel still down?
No, this incident was resolved 2026-03-31 21:23 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
12m, from 2026-03-31 21:11 UTC to 2026-03-31 21:23 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.