- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 100
What to do
Check whether your product depends on Vercel. 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 1h 34m it lasted.
Anything that failed between 2026-09-10 17:42 UTC and 2026-09-10 19:16 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've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
Connect and Passport have fully recovered. 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-b577d1008e
Is Vercel still down?
No, this incident was resolved 2026-09-10 19:16 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
1h 34m, from 2026-09-10 17:42 UTC to 2026-09-10 19:16 UTC, by the times Vercel posted.
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.