- Level
- confirmed
- Worst impact
- Degraded
- Components
- Builds, Functions, Routing Middleware
- Regions
- me
- Down Index
- 26of 100
What to do
Check whether you use Vercel Builds, Functions, Routing Middleware in me. 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 9h 14m it lasted.
Anything that failed between 2026-03-02 06:06 UTC and 2026-03-02 15:20 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 8
- identified
Starting from 5:00 am UTC, we have started seeing failures to deploy and invoke functions in Dubai region (dxb1). Deployments with Middleware Functions are also impacted in all regions, because Middleware Functions are deployed globally for production deployments. Our team is actively investigating the issue.
provider
- identified
We have rolled out mitigations and are seeing recovery. If you are still seeing build failures and are using Dubai (dxb1) as your primary Vercel Functions region, you can switch to another region as a workaround.
provider
- identified
The dxb1 Edge traffic is currently being rerouted to the nearest Edge region (bom1) to mitigate the impact. We will provide additional updates as they become available.
provider
- identified
We are still seeing elevated errors in Builds in all regions, because Middleware and Edge Functions may be deployed globally. Builds that don't use Middleware and Edge Functions are not impacted. We are continuing to work on a fix for this issue.
provider
- identified
We are currently deploying a mitigation for elevated Build errors. Builds that use Middleware or Edge Functions will exclude the Dubai region (dxb1) from their deployment targets as a temporary measure. We will provide additional updates as they become available.
provider
- identified
We have rolled out a first mitigation for elevated Build errors. Builds that use Middleware are now excluding the Dubai region (dxb1) from their deployment targets as a temporary measure, and should complete successfully again. We are now working on a mitigation for Builds that are using Edge Functions.
provider
- monitoring
We have rolled out a second mitigation for elevated Build errors and are seeing recovery. All builds are now excluding the Dubai region (dxb1) from their deployment targets as a temporary measure. We will provide additional updates as they become available.
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-434838561f
Is Vercel still down?
No, this incident was resolved 2026-03-02 15:20 UTC. For Vercel's live state, see https://down.guide/vercel.
How long did it last?
9h 14m, from 2026-03-02 06:06 UTC to 2026-03-02 15:20 UTC, by the times Vercel posted.
What was affected?
Vercel named Builds, Functions, Routing Middleware in me.
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.