Elevated deployment and function invocations failures

Update timeline

1. identified Mar 02, 2026, 06:06 AM UTC

   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.

2. identified Mar 02, 2026, 06:24 AM UTC

   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.

3. identified Mar 02, 2026, 07:56 AM UTC

   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.

4. identified Mar 02, 2026, 10:50 AM UTC

   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.

5. identified Mar 02, 2026, 11:59 AM UTC

   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.

6. identified Mar 02, 2026, 01:00 PM UTC

   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.

7. monitoring Mar 02, 2026, 02:59 PM UTC

   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.

8. resolved Mar 02, 2026, 03:20 PM UTC

   This incident has been resolved.