Vercel Outage History

A transient issue affected Vercel's Build & Deploy / npm Registry, causing private npm package installations to fail with 4xx errors. This disrupted builds that depend on private packages, with authentication problems reported to prevent token-based access. The outage began at Apr 11, 2025 2:41 AM UTC and was resolved by Apr 11, 2025 3:21 PM UTC, lasting about 12 hours and 40 minutes. The root cause was tied to private registry authentication, and a recommended workaround involved regenerating tokens. The incident included two official status updates during its course. Note that there was no public guidance from npm or GitHub regarding the root cause.

Vercel experienced a brief incident where the Dashboard indicated elevated reports of projects being paused even though the Spend Limit had not been reached. The Dashboard component was affected, and users may have seen paused statuses within the UI, impacting project management for a period. The incident lasted approximately 1 hour and 40 minutes, beginning at 1:16 PM UTC and resolving by 2:56 PM UTC. Vercel issued two official status updates during the incident, moving from warn to up as the issue was resolved.

Between Apr 8, 2025 8:11 PM UTC and Apr 8, 2025 8:26 PM UTC, the Vercel Community site experienced a brief outage that made the Community section inaccessible to some users. The Community component was listed as degraded during this window and returned to normal by Apr 8, 2025 8:26 PM UTC. The incident lasted about 15 minutes, and Vercel issued 2 status updates during the event, acknowledging the investigation and later confirming recovery.

Vercel reported a degraded condition in the Logs component due to missing OTEL traces for Datadog exports. The issue affected telemetry data used by Datadog integrations, with users potentially seeing incomplete traces. The incident began with an investigation at 5:37 PM UTC and was reflected on the status page at 10:36 PM UTC. The problem persisted for about 1 hour and 20 minutes and was resolved by 11:56 PM UTC when the component returned to normal. Other aspects of Vercel's services were reported as unaffected.

The outage affected the Vercel Dashboard Integrations page, rendering the Integrations tab inaccessible. Integration connections with your projects were not affected, and you could still view Integrations from the Storage tab in the Dashboard. The outage began at 3:36 PM UTC and was resolved by 5:16 PM UTC.

The provider issued 2 official updates during the incident, and the Dashboard recovery restored access to the Integrations page. The issue was isolated to a single Dashboard component and lasted about 1 hour and 40 minutes.

Vercel's CPT1 Edge Network in Cape Town, South Africa experienced elevated latency that affected requests routed through that region. The incident was regional in nature and did not indicate a global outage. The degradation lasted about 1 hour and 35 minutes, with latency returning to normal by the time the CPT1 node was restored. Status updates indicated an ongoing investigation during the degradation period.

Vercel reported a brief disruption in the Build & Deploy builds due to some Enhanced Build Machines being queued, resulting in short build and deployment delays for users. The issue began at Apr 3, 2025 3:01 PM UTC and was resolved by Apr 3, 2025 3:36 PM UTC after engineers identified the cause and rolled out a fix. The incident prompted two status updates from Vercel as the situation evolved, and services returned to normal once the fix was implemented. The impact appeared limited to builds and deployments, with no confirmed widespread service outage.

Vercel's Edge Network in the IAD1 region (Washington DC) encountered intermittent traffic issues, causing degraded performance for requests routed through that edge location. The incident began with an investigation at Apr 3, 2025 1:37 AM UTC and was later described as an intermittent regional issue affecting the IAD1 edge.

Two status updates were issued during the incident, with the issue resolving by Apr 3, 2025 3:51 AM UTC. The outage lasted roughly 2 hours from the initial investigation to restoration, and users may have experienced intermittent connectivity or slower responses while routing through IAD1.

Impact was limited to the IAD1 edge location with no wider, system-wide disruption reported. User report volume remained low during the event.

From Apr 1, 2025 4:41 PM UTC to Apr 1, 2025 7:46 PM UTC, Vercel reported a partial degradation of the Optional Third Party Dependencies / npm Package installation component. Builds and deployments that rely on npm install may have experienced slower installs or intermittent failures. The incident lasted about 3 hours and 5 minutes. The Vercel status page issued two updates during the event, first noting the degradation and later confirming service restoration.

The outage began at 6:26 AM UTC, with Vercel reporting a delay in runtime logs affecting the bom1 and pdx1 regions. The Logs component entered a degraded state while Log Drains were briefly impacted; the status page later confirmed that Log Drains were unaffected and operating normally by 6:31 AM UTC. Three status updates were issued as the issue was investigated, and by 8:36 AM UTC the Logs component had returned to normal and services resumed typical operation. The incident lasted approximately 2 hours and 10 minutes and was geographically limited to bom1 and pdx1 regions.