Vercel Outage History

The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard.

We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.

The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.

The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.

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

The issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period.

We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.

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

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

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

We have identified the issue and are working closely with GitHub to resolve it.

We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.

The root cause has been identified and we are rolling out a mitigation.

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

We're continuing to work on rolling out a fix. In the mean time, customers may use Instant Rollback to a previous deployment version as an immediate workaround in order to recover.

The team has identified the source of the incorrect usage data calculations and has paused usage tracking while a fix is being prepared.

We are continuing to work on the fix. Usage tracking for Workflow Storage remains paused. The incorrect calculations will not be charged.

We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are applying a fix and will provide additional updates as they become available.

Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available.

Traffic to the IAD1 region has been re-routed to nearby regions. Functions configured in IAD1 will be invoked in a different region if failover regions are configured, but if no other regions are configured, the function will still be invoked in IAD1.

New messages to Vercel Workflows and Vercel Queue are being queued, but message processing is paused. Queued messages will be processed when service is restored.

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

New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated.

We are experiencing increased error rates with Workflows running on Vercel. We have identified the issue and are implementing a fix.

We've identified an issue where various services in the Vercel dashboard, API, and CLI are failing to load data. These services include Observability, Speed Insights, Alerts, Usage, Web Analytics, Firewall, and CDN observability. Broadly, areas backed by analytical data are affected. We have identified the issue and are working on a fix. Production applications running on Vercel are not impacted.

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

We are seeing services start to recover as we incrementally apply the fix.

Reading data from impacted services has recovered. We are working to backfill any missing data in Observability.

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