Elevated deployment and function invocations failures

Incident Report for Vercel

Resolved

This incident has been resolved.
Posted Mar 02, 2026 - 15:20 UTC

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.
Posted Mar 02, 2026 - 14:59 UTC

Update

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.
Posted Mar 02, 2026 - 13:00 UTC

Update

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.
Posted Mar 02, 2026 - 11:59 UTC

Update

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.
Posted Mar 02, 2026 - 10:50 UTC

Update

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.
Posted Mar 02, 2026 - 08:43 UTC

Update

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.
Posted Mar 02, 2026 - 06:24 UTC

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.
Posted Mar 02, 2026 - 06:06 UTC
This incident affected: Build & Deploy (Builds) and Edge Functions, Edge Middleware, Serverless Functions.