Vercel

Mar 6, 21:38 UTC
Resolved - This incident has been resolved.

Mar 6, 21:20 UTC
Monitoring - A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

Mar 6, 19:18 UTC
Update - 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.

Mar 6, 15:25 UTC
Identified - Some deployments created between 11:20 UTC and 15:14 …

Mar 6, 21:22 UTC
Resolved - This incident has been resolved.

Mar 6, 21:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 6, 21:00 UTC
Identified - The issue has been identified and a fix is being implemented.

Mar 6, 20:53 UTC
Investigating - We are investigating reports of elevated queue message latency and message retry latency in iad1, as well as elevated sleep times and increased step retries in Workflow. We will provide additional updates as they become available.

Mar 3, 21:10 UTC
Resolved - This incident has been resolved.

Mar 3, 19:14 UTC
Monitoring - A fix has been implemented and we are seeing recovery for data loading and ingestion across services. We are continuing to monitor and will provide additional updates as they become available.

Mar 3, 17:10 UTC
Investigating - Dashboard pages that use Observability data, including Observability, Speed Insights, Web Analytics, Usage, Firewall, and Activity, are experiencing delays while loading data. These pages are also experiencing delays ingesting new data. We are investigating this issue and will provide additional updates as they become available.

Mar 2, 18:23 UTC
Monitoring - We are monitoring the situation and continue to work toward restoring capacity in the dxb1 region. We will send further updates when new information is available.

Mar 2, 15:29 UTC
Identified - 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 …

Mar 2, 15:20 UTC
Resolved - This incident has been resolved.

Mar 2, 14:59 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.

Mar 2, 13:00 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 …

Mar 2, 12:08 UTC
Resolved - This incident was resolved.

Mar 2, 08:49 UTC
Monitoring - 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.

Mar 2, 08:01 UTC
Identified - We are continuing to work on a fix for this issue.

Mar 2, 06:54 UTC
Investigating - We are currently investigating issues collecting Logs and Traces in Dubai (dxb1). We will share updates as they become available.

Mar 2, 00:22 UTC
Resolved - A fix has been implemented and new deployments are no longer failing.

Mar 1, 21:17 UTC
Identified - 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.

Feb 28, 06:28 UTC
Resolved - This incident has been resolved.

Feb 28, 05:46 UTC
Monitoring - We experienced delays in loading Observability, Analytics and Speed Insights data on the dashboard. We will provide additional updates as they become available.

Feb 13, 02:56 UTC
Resolved - The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC.

Feb 13, 01:52 UTC
Update - The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC.

Feb 12, 22:59 UTC
Monitoring - The issue with delayed firewall observability data has been identified. New data has recovered and old data may be delayed.

Feb 12, 22:41 UTC
Investigating - We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become …

Feb 11, 15:00 UTC
Resolved - On February 11, 2026, between 15:00 and 19:26 UTC, AI Gateway experienced elevated error rates due to an issue affecting Vercel Functions infrastructure in the cle1 and fra1 Vercel Regions. Requests routed to these regions, including requests originating from other regions, may have experienced failed requests or timeouts during this time. We have resolved the issue, and the service is now operating normally. We apologize for the disruption.