- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs
- Down Index
- 18of 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 1h 24m it lasted.
Anything that failed between 2026-05-25 14:58 UTC and 2026-05-25 16:22 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 4
- investigating
We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-5c96b0cd12
Is Vercel still down?
No, this incident was resolved 2026-05-25 16:22 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
1h 24m, from 2026-05-25 14:58 UTC to 2026-05-25 16:22 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.