V
Vercel Status - Incident History
Vercel-status
RSSen
Information
Followers
Following
AI Overview
2 posts analyzed·Updated 3/7/2026

Key Highlights

  • Elevated latency on queue messages and message retry latency in iad1 (Ashburn, Virginia, US) was resolved after investigation and fix implementation. 1 post

  • Elevated errors on middleware invocations for deployments created between 11:20 UTC and 15:14 UTC were resolved, with fixes applied and recovery observed. 1 post

  • Both incidents on March 6 were resolved after monitoring and fixes, with no action required for unaffected deployments. 2 posts

Main Topics (3)

Latest posts

website-logo

Elevated Latency on Queue Messages, Increased Message Retry Latency in iad1

Vercel Status - Incident History

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 investigati

website-logo

Elevated Errors on Middleware Invocations

Vercel Status - Incident History

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

website-logo

Delays Loading Observability, Usage, Analytics, and Speed Insights Data

Vercel Status - Incident History

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

website-logo

Dubai region (dxb1) is unavailable and traffic is being re-routed

Vercel Status - Incident History

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-route

website-logo

Degraded Logs and Traces in Dubai region (dxb1)

Vercel Status - Incident History

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 conti

website-logo

Elevated deployment and function invocations failures

Vercel Status - Incident History

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 pr

website-logo

Deployments are failing for customers using Static IPs in Dubai region (dxb1)

Vercel Status - Incident History

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 configur

website-logo

Delays Loading Observability, Analytics and Speed Insights Data

Vercel Status - Incident History

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.

website-logo

Delayed Firewall Observability Data

Vercel Status - Incident History

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

website-logo

Elevated Error Rate on AI Gateway in cle1 and fra1

Vercel Status - Incident History

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 regio

website-logo

Problems Loading Dashboard & Elevated Builds Error Rate

Vercel Status - Incident History

Feb 7, 11:18 UTC Resolved - This incident has been resolved. Feb 7, 10:23 UTC Monitoring - We have applied a fix and are seeing recovery across builds and dashboard. We are continuing to monitor. Feb 7, 09:35 UTC Identified - We have identified the issue and begun applying a fix. We are beginning

website-logo

Delays Loading Firewall, Billing, and Observability Data

Vercel Status - Incident History

Feb 5, 20:51 UTC Resolved - This incident has been resolved. Feb 5, 19:35 UTC Monitoring - A fix has been implemented and we are beginning to see gradual recovery. We are actively monitoring results and will share more updates as they become available. Feb 5, 18:28 UTC Update - We are continuing

website-logo

Elevated Error Rates on Sandboxes

Vercel Status - Incident History

Feb 3, 21:54 UTC Resolved - This issue has been resolved and sandboxes are creating normally. Feb 3, 20:14 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 3, 19:51 UTC Update - We are releasing a fix and are continuing to work on stabilizing sandbox creation. Fe

website-logo

Elevated latency creating new deployments

Vercel Status - Incident History

Feb 3, 21:36 UTC Resolved - The issue has been resolved and all deployments are building normally. Feb 3, 21:12 UTC Monitoring - A fix has been applied resolving the queue for new deployments. We are continuing to monitor the results. Feb 3, 20:48 UTC Investigating - We are investigating elevated

website-logo

Elevated Errors on API & Dashboard, Delayed Builds

Vercel Status - Incident History

Feb 3, 17:30 UTC Resolved - This incident has been resolved. Feb 3, 16:50 UTC Monitoring - A fix has been implemented, and we are monitoring results. Feb 3, 16:22 UTC Update - We have begun applying fixes and are seeing partial recovery across API, dashboard, and builds. We are continuing to appl

website-logo

Elevated error rates in sin1 (Singapore) Edge Region

Vercel Status - Incident History

Feb 1, 08:57 UTC Resolved - There were elevated error rates in the sin1 (Singapore) edge region between 08:57 and 09:04 UTC. The issue has been resolved, and all systems are operating normally.

website-logo

Elevated git clone duration at build time

Vercel Status - Incident History

Jan 30, 11:08 UTC Resolved - This incident has been resolved. Jan 30, 10:42 UTC Monitoring - The new build routing has addressed the issue. We are monitoring the results. Jan 30, 10:24 UTC Update - We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we conti

website-logo

Elevated Connection Latency in dub1 (Dublin, Ireland) Edge Region

Vercel Status - Incident History

Jan 28, 20:21 UTC Resolved - This incident has been resolved, and traffic has been fully routed back to the dub1 region. Jan 28, 19:56 UTC Monitoring - A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results. Jan 28, 18:27 UTC Update - We have rerou

website-logo

Delayed Dashboard Data Across Multiple Services

Vercel Status - Incident History

Jan 26, 17:57 UTC Resolved - This incident has been resolved. Jan 26, 17:35 UTC Update - A fix is currently being rolled out. Most customers should now be seeing recovery, and we expect this incident to be fully resolved shortly. Jan 26, 16:04 UTC Update - We are continuing to work on a fix for this

website-logo

Some domain purchases are failing

Vercel Status - Incident History

Jan 23, 04:28 UTC Resolved - After monitoring, we do not see the issue persisting. This incident is resolved. Jan 23, 03:49 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan 23, 03:48 UTC Identified - The issue has been identified and a fix is being implemented. Jan

website-logo

Elevated build failure rates

Vercel Status - Incident History

Jan 14, 10:50 UTC Resolved - After monitoring our fix, we found no new occurrences of build errors. This issue has been resolved. Jan 14, 02:22 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan 14, 01:43 UTC Update - We're continuing to investigate this issue and wil

website-logo

Errors creating Support Center cases

Vercel Status - Incident History

Dec 12, 15:34 UTC Resolved - This incident has been resolved. Dec 12, 14:45 UTC Monitoring - We've identified the issue, and we are working on a fix. Vercel customers should be able to create cases normally while we monitor case operation metrics closely. Dec 12, 13:12 UTC Investigating - We are inv

website-logo

Web Analytics and Speed insights data not recorded on some projects

Vercel Status - Incident History

Dec 12, 11:47 UTC Resolved - This incident has been resolved. Dec 12, 11:17 UTC Monitoring - A fix has been implemented and we are monitoring the results. Dec 12, 11:16 UTC Identified - The issue has been identified and a fix is being implemented. Dec 12, 10:17 UTC Investigating - On some projects,

website-logo

Elevated error rates across new deployments and Vercel API

Vercel Status - Incident History

Dec 10, 06:22 UTC Resolved - Vercel API errors have been resolved and dashboard access is restored across all regions. Queued deployments are recovering automatically, but failed deployments may need to be redeployed manually. Dec 10, 06:16 UTC Update - We are continuing to investigate this issue. D

website-logo

Elevated errors creating deployments with Neon and Supabase integrations

Vercel Status - Incident History

Dec 9, 05:51 UTC Resolved - This incident has been resolved. Dec 9, 04:15 UTC Update - Deployments using the Supabase integration are now working as expected. We are continuing to work on `Resource provisioning timed out` errors related to the Neon integration. Dec 9, 03:29 UTC Identified - We've