Vercel Incident History

We are currently investigating this issue.

Some users may have experienced issues accessing v0 from 17:04 UTC - 17:10 UTC. This issue has since been resolved.

Some users may have experienced issues deploying from v0 if Radix tabs were used between 15:50 and 17:05 UTC. This issue is now fixed.

Between 07:40 and 07:58 UTC, some users experienced increased latency and error rates for traffic served through the hnd1 (Tokyo, Japan) region. The issue has been resolved, and services are now operating normally.

We have observed authentication issues to private registries using npm access tokens. Affected users may see 4xx errors when installing private packages. Manually regenerating tokens appears to resolve this issue. At this time, there is no official statement from npm or GitHub regarding the root cause.

We're investigating some monthly performance emails that were sent in error.

We are currently investigating reports of elevated projects being paused despite the specified Spend Limit not being reached. We will share updates as they become available.

The Vercel Community site is currently unavailable to some users. We are investigating and will provide further updates as the incident progresses.

We are currently investigating missing OTEL traces for Datadog exports since ~17:37 UTC. Other providers are unaffected.

We are currently investigating an issue where the Vercel Integrations page is down. This affects the Integrations tab in the Vercel Dashboard. Integration connections with your projects are not affected and it is only the Vercel Dashboard that is unavailable. Integrations can also still be viewed from the Storage tab on the Vercel Dashboard.

We are currently investigating the issue.

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

We have identified the root cause of service disruption and are currently working on a fix.

We are currently investigating this issue.

We have identified a delay in log delivery specifically affecting bom1 and pdx1. We will continue to investigate and provide updates as this progresses.

During a 4-minute window today between 12:47-12:51 UTC, we experienced a brief increase in 500 errors affecting a small subset of Edge Functions invocations. The issue was isolated to the following regions: lhr1, bom1, hkg1, cdg1, hdn1, iad1. Edge Middleware and Serverless Functions were unaffected.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.Deployments created after this time (13:44 UTC) should no longer face the issue.

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

Some builds are erroneously being cancelled with the message:The Deployment has been cancelled as a result of running the command defined in the "Ignored Build Step" setting.

This incident has been resolved.

We are currently investigating an increase in 400 errors related to Blob Storage.

This incident has been resolved.

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

We are currently investigating an issue where the Vercel Marketplace and Integrations pages are down. This affects the Integrations tab in the Vercel Dashboard and https://vercel.com/marketplaceIntegration connections with your projects are not affected and it is only the dashboard that is unavailable. Integrations can also still be viewed from the Storage tab on the Vercel Dashboard.