- Level
- confirmed
- Worst impact
- Degraded
- Components
- Builds, Logs
- Down Index
- 19of 100
What to do
Check whether you use Vercel Builds, 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 18m it lasted.
Anything that failed between 2026-04-07 07:19 UTC and 2026-04-07 08:37 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 build logs stuck in loading state.
provider
- monitoring
We identified the cause of build logs stuck in the loading state affecting iad1 and are working around the issue for new builds. Please redeploy to your build to view build logs.
provider
- resolved
The incident has been resolved. If you don't see build logs for a specific deployment, please redeploy.
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-d55f7e75e4
Is Vercel still down?
No, this incident was resolved 2026-04-07 08:37 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
1h 18m, from 2026-04-07 07:19 UTC to 2026-04-07 08:37 UTC, by the times Vercel posted.
What was affected?
Vercel named Builds, 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.