- Level
- confirmed
- Worst impact
- Degraded
- Components
- Builds
- Down Index
- 20of 100
What to do
Check whether you use Vercel Builds. 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 3h 20m it lasted.
Anything that failed between 2026-07-16 06:07 UTC and 2026-07-16 09:27 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 2
- monitoring
We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
provider
- resolved
The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.
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-1b29fb1ad4
Is Vercel still down?
No, this incident was resolved 2026-07-16 09:27 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
3h 20m, from 2026-07-16 06:07 UTC to 2026-07-16 09:27 UTC, by the times Vercel posted.
What was affected?
Vercel named Builds.
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.