- Level
- confirmed
- Worst impact
- Partial outage
- Vercel says
- 2026-11-10 19:16 to 19:34 UTC (18m)
- Components
- Blob, Sandbox
- Down Index
- 33of 100
What to do
Check whether you use Vercel Blob, Sandbox. 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 0m it lasted.
Anything that failed between 2026-11-10 21:04 UTC and 2026-11-10 21:04 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 1
- resolved
On November 10, 2026, between 19:16 and 19:34 UTC, some Sandbox and Blob API requests in iad1 region experienced elevated latency and errors. A fix was applied, restoring service at 19:34 UTC and preventing this issue from recurring. This incident lasted 18 minutes and is being reported retroactively. We apologize for the disruption.
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-a37531d964
Is Vercel still down?
No, this incident was resolved 2026-11-10 21:04 UTC. For Vercel's live state, see https://down.guide/providers/vercel.
How long did it last?
0m, from 2026-11-10 21:04 UTC to 2026-11-10 21:04 UTC, by the times Vercel posted.
What was affected?
Vercel named Blob, Sandbox.
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.