- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Logs
- Down Index
- 24of 100
What to do
Check whether you use Vercel Logs. 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 11m it lasted.
Anything that failed between 2026-08-20 11:14 UTC and 2026-08-20 11:25 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 a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.
provider
- monitoring
We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.
provider
- resolved
The system is operating normally and fully recovered.
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-bb765540a3
Is Vercel still down?
No, this incident was resolved 2026-08-20 11:25 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
11m, from 2026-08-20 11:14 UTC to 2026-08-20 11:25 UTC, by the times Vercel posted.
What was affected?
Vercel named Logs.
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.