Vercel Outage History

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.

This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt

GitHub has implemented a fix, and we are monitoring the results.

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

We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops.

We are continuing to investigate this issue.

We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs. CLI deployments are unaffected at this time.

We are currently investigating this issue.

This incident has been resolved.

The mitigation was successfully rolled out, and builds are stable.

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

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.

This incident has been resolved. Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up over the next business day as we backfill the data for the affected window.

We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.

This incident has been resolved. Some deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments created outside of this window are unaffected. The fix is being rolled out to existing deployments retrospectively and is expected to finish in the next few hours.

We are continuing to monitor for any further issues.

A fix is rolled out for the function invocation errors affecting React Router 7 deployments. To recover, redeploy your application or use Instant Rollback to a previous deployment from the dashboard. We're continuing to monitor.

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 issue has been identified and a fix is being implemented.

We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.

The incident is resolved and support cases can be submitted again.

We have implemented a fix. New support cases can be created. We continue to monitor.

We are investigating an issue where support cannot be submitted through the dashboard.

The usage tracking system is fully recovered.

The team fixed the incorrect calculations. We are resuming usage tracking and continuing to monitor.

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

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

Workflow Storage Retention and Workflow Storage Writes are being incorrectly calculated in usage data. The team is investigating and working to resolve the discrepancy.

This incident has been resolved.

Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is recovering, Vercel Queues backlogs are being processed, and Vercel Workflows are unblocked.

This incident has been resolved.

We have applied a fix and are observing recovery across all builds. We'll provide additional updates as-needed.

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.

We've deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in the IAD1 region.

We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours.

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 continuing to work on a fix for this issue.

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

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.

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.

This issue has been resolved and new deployments are being created successfully.

We are investigating an issue affecting new deployments that are stuck in the provisioning state. We will share more information as it becomes available.

All services remain operational. New data is being processed as expected. The majority of the backfill is complete and a long tail of data will be processed within the next couple of hours.

All systems are operational. We are continuing to monitor the backfill process, which is expected to take a couple of hours. New data is being processed as expected.

We are continuing to monitor for any further issues.

Impacted services have recovered. We are continuing to monitoring, while backfilling remaining missing data.

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

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

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

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

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

We are currently investigating this issue.

This incident has been resolved.

A fix has been applied and we are seeing signs of recovery across domains operations. We are continuing to monitor and will provide additional updates as needed.

We are investigating an issue causing elevated error rates across domains operations, including renewals, nameserver changes, search, and checkout. We will provide additional updates as they become available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We're investigating reports of unexpected errors when trying to create and deploy new projects from templates. We will provide additional updates as they become available.

We have identified an issue resulting in delayed and/or missing usage data for observability events between 9:00 - 10:30 UTC and 16:50 - 19:30 UTC. The issue has been identified and resolved. Usage data for observability events for the affected time buckets have been recovered. The affected windows will continue to show missing data - the recovered data will show up as additional usage at recovery timestamps. The total usage count for the period is accurate and no additional actions are required for customers at this time.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We're continuing to investigate reports of customers being unable to checkout with domains purchases. We're also investigating reports of being unable to purchase AI gateway credits. We'll provide additional updates as they become available.

We're investigating reports of customers being unable to checkout with domains purchases. We'll provide additional updates as they become available.

This incident has been resolved.

A fix has been implemented for the issue causing delays in loading logs and we are seeing signs of recovery. We'll provide additional updates as-needed.

We've identified an additional issue causing delays in loading logs. We'll provide additional updates as they become available.

A fix has been implemented for the issue causing delays in loading logs and we are seeing signs of recovery. We'll provide additional updates as-needed.

We are continuing to implement a fix for the issue causing delays in loading logs. We will provide additional updates as they become available.

We are continuing to implement a fix for the issue causing delays in loading logs. We will provide additional updates as they become available.

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

We're investigating an issue causing delays in loading logs. We will provide additional updates as they become available.

We've identified an issue causing missing observability data for compute products between April 22, 2026 23:00 UTC and April 23, 2026 05:00 UTC affecting a subset of customers, resulting in missing or incomplete metrics in Observability dashboard during this period. All underlying compute services - including Vercel Functions, Workflows, and Cron Jobs - continued to operate normally. Logs were not affected and remain fully available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We are currently investigating this issue.

This incident has been resolved.

We have implemented a fix targeted at usage anomalies and are now observing recovery across all anomaly alerts. We will share any additional updates as-needed.

We are continuing to work on a fix for usage anomalies. We'll provide additional updates as they become available.

We are continuing to work on a fix for usage anomalies. We'll provide additional updates as they become available.

We have resolved the issue for error anomalies, and are continuing to work on a fix for usage anomalies.

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

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

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

We are currently investigating Observability Alerts not detecting new events. We will share more updates as soon as we have more information.

This incident has been resolved.

A fix has been implemented and we are observing recovery in error rates across the Vercel Dashboard and API endpoints. We will continue to monitor and share any additional updates as they become available.

We have identified an issue causing elevated error rates on the Vercel Dashboard and API endpoints. Some users may experience an issue creating new deployments, but existing deployments are not impacted. We will share more updates as they become available.

This incident has been resolved.

A fix has been implemented and we are seeing recovery. No action is required - data may continue to be partially delayed as it is backfilled.

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

We are currently experiencing delays in loading Observability, Analytics and Speed Insights data on the dashboard. This may also affect User Activity Events and Firewall UI. Vercel Alerts may also be delayed. We will provide additional updates as they become available.

This incident has been resolved.

A fix has been rolled out, and we are monitoring the results. Queued deployments are being processed and new deployments are building normally now.

We have identified an issue causing elevated queue times for deployments on the Hobby plan. We are investigating a fix and will share more updates as soon as we have more information.

The incident has been resolved. If you don't see build logs for a specific deployment, please redeploy.

We identified the cause of build logs stuck in the loading state affecting iad1 and are working around the issue for new builds. Please redeploy to your build to view build logs.

We are investigating reports of build logs stuck in loading state.

This incident has been resolved.

The fix has been rolled out and we are monitoring the results. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.

We have identified the issue and are rolling out a fix. Deployments created between 16:10 to 19:12 UTC may be affected. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.

We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.

This incident has been resolved.

The root cause has been identified, a fix has been rolled out, and we are actively monitoring. Newly deployed Vercel Functions on Node.js 20 in cle1 and dub1 no longer terminate with SIGSEGV. We recommend redeploying affected Vercel Functions if you are still seeing issues.

We are continuing to investigate increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV in Vercel's cle1 and dub1 regions. Other regions are unaffected. We recommend redeploying affected Vercel Functions or upgrading them to either Node js 22 or 24.

We are currently investigating increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV. We recommend redeploying affected Vercel Functions or upgrading them to either Node.js 22 or 24.

This incident has been resolved.

A fix has been implemented and we are monitoring the results. Webhook events are being delivered normally, and deployments with integrations are building successfully.

We have identified an issue causing elevated latency and errors with delivering webhooks and creating deployments that use integrations. We are working on a fix for this issue and will provide further updates as soon as they become available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating reports of elevated error rates on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating reports of elevated error rates loading the Deployment Overview on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are observing elevated errors creating Vercel Functions in the `sin1` region. To mitigate errors creating deployments, we have temporarily disabled provisioning new Vercel Functions in this region. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.

Due to ongoing issues in the dxb1 region, traffic and regional Vercel services are currently re-routed to bom1. We will share more details on recovery when they become available.

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.

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.

This incident has been resolved.

A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.

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.

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.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

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.

This incident has been resolved.

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.

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.

This incident has been resolved.

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.

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.

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

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

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.

This incident was resolved.

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 continuing to work on a fix for this issue.

We are currently investigating issues collecting Logs and Traces in Dubai (dxb1). We will share updates as they become available.