Vercel Outage History

The issue has been identified and a fix is being implemented.

Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.

We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.

Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments. If your existing deployments that use the dxb1 region are experiencing elevated function invocation errors, we strongly recommend switching to the nearest region (such as bom1) and redeploy until capacity is restored in dxb1. Deployments using multiple regions or failover regions are not affected since traffic is automatically routed to the nearest region based on the configured settings.

We are continuing to work on a fix for this issue.

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.

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.

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.

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.

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.

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.

Deployments for customers that use Static IPs are failing when deploying functions to the Dubai region. Customers can remove the Dubai region from the Static IPs configuration to avoid deployment failures. Our team is actively investigating the issue. Deployments to other regions are not affected.

We have identified the issue and begun applying a fix. We are beginning to see partial recovery across builds and parts of the dashboard. We will provide additional updates as they become available.

The issue has been identified and a fix is being implemented.

We are continuing to implement a fix for delays in data appearing in the dashboard for firewall, billing, and observability. We will share additional updates as they become available.

We have identified an issue while creating new sandboxes. We are working on a fix for the issue.

We are continuing to work on a fix for this issue.

We are releasing a fix and are continuing to work on stabilizing sandbox creation.

The issue has been identified, and we are working on a fix.

We have begun applying fixes and are seeing partial recovery across API, dashboard, and builds. We are continuing to apply fixes. We will share additional updates as they become available.