Vercel Outage History

Services have recovered. We are still working to ingest missing observability data during this period.

Services have recovered. We are still working to ingest missing observability data during this period.

Login with TOTP has completely recovered. We are still working to ingest missing observability data during this period. We will share more information as it becomes available.

We are continuing to monitor for any further issues.

We have implemented a fix for the disruption, and services have started to recover. We will share more information as it becomes available.

We are also investigating an issue where some customers may be unable to sign in to Dashboard with time-based one-time passwords (TOTP). We will share updates as they become available.

We are continuing to investigate this issue. We will share updates as they become available.

We are investigating a partial disruption to Observability, Web Analytics, Speed Insights, Firewall, and Usage in Dashboard. We will share updates as they become available.

This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.

Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed.

We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available.

We've identified the issue and are working on a fix. We will provide updates as they become available.

We continue to investigate this issue and will provide updates as they become available.

We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.

This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected.

We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment.

We have identified the source of errors and are implementing a fix.

There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.

This incident has been resolved.

Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered.

We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available.

We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.

The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.

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.

A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available.

We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.

This incident has been resolved.

We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC. A rollback is in progress to mitigate this issue. We will provide additional updates as they become available. Failed deployments can be retried and should succeed.

We have unpaused all impacted deployments. We will continue to monitor the situation.

We are still working to unpause affected teams that were erroneously paused due to the spend management budget miscalculation. We will provide additional updates as they become available.

We've compiled a list of deployments that were paused due to this incident and are now unpausing them in batches. If your deployment was paused, you can also navigate to the Vercel dashboard and click the unpause button in the banner.

We've identified and fixed the underlying issue. Our team is now unpausing deployments that were inadvertently paused as a result.

We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.

This incident has been resolved.

The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected. We are continuing our internal root cause analysis.

Build queues have returned to normal levels, and build processing should be restored. We are monitoring to ensure the service remains stable. We will provide additional updates as they become available.

We are seeing signs of recovery and the affected build queue has started to drain. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available.

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

This incident has been resolved.

A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor.

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

We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.

The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state.

We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted.

We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and 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 an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.

The incident has been resolved.

The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor.

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 continuing to investigate partial disruption to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are also investigating delayed usage alerts.

We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.

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.

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. If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue.

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.

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 some customers experiencing elevated errors creating new deployments. 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've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.

This incident has been resolved. We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC.

We are currently investigating this issue.

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