Vercel Outage History

Vercel reported degraded performance in the npm Registry within the Build & Deploy pipeline, causing npm package installs to timeout for some users and potentially leading to failed builds. The incident affected the Build & Deploy / npm Registry component. The outage began at 7:06 PM UTC and was resolved by 8:01 PM UTC, lasting approximately 55 minutes. The status page provided updates as the situation evolved, reflecting the degraded performance and subsequent restoration.

Vercel users attempting to create deployments from GitLab commits encountered errors. Existing deployments and live traffic were not affected. The outage began at Aug 21, 2025 11:26 AM UTC and was resolved by Aug 21, 2025 2:26 PM UTC. The Build & Deploy / Builds component was affected and Vercel posted 2 status updates during the incident.

Vercel experienced an outage that affected deployments and the Dashboard, with intermittent deployment failures and elevated latency in the dashboard UI. The incident began at 5:24 PM UTC and was resolved by 5:46 PM UTC. The status page indicated investigation followed by updates as the service returned to normal, with the issue centered on the Dashboard component and deployment workflows.

Vercel experienced a brief disruption affecting the Build & Deploy / Builds component, with an elevated error rate that prevented or slowed builds for a portion of users. The incident began with an investigation at Aug 6, 2025 9:16 PM UTC and the status page moved to a degraded state at Aug 6, 2025 9:21 PM UTC. The issue appeared limited to the Builds component and did not affect other parts of the platform. The outage lasted about 25 minutes, with builds returning to normal after Aug 6, 2025 9:46 PM UTC.

Vercel experienced a minor outage affecting access to Documentation, Guides, and Support Forms, with two dashboard-related components briefly degraded. The incident began at 1:11 PM UTC and was resolved by 2:31 PM UTC, lasting roughly 1 hour and 20 minutes. The provider issued 3 status updates during the event, describing the initial investigation, the ongoing outage, and eventual restoration. The affected components were Dashboard / Dashboard and Dashboard / Support Center.

Vercel experienced a partial disruption affecting deployments via the GitLab integration. The issue impacted GitLab authentication and deployment workflows, primarily within the Build & Deploy / Builds component, causing authentication and deployment failures for GitLab-based workflows. The status page indicated the team was investigating the problem.

Vercel experienced a partial outage affecting deployment workflows. Users attempting to create new deployments encountered MODULE_NOT_FOUND errors within the Build & Deploy / Builds component, blocking deployment activity while other platform features remained available. The issue was limited to deployment tasks and did not indicate a full platform failure.

A brief SSL certificate issuance delay on Vercel prevented access to new deployments over HTTPS for about 10 minutes, while production and preview traffic to existing deployments remained available. The incident began at 7:31 PM UTC and was resolved by 7:41 PM UTC. The SSL Certificates component was listed as degraded during the event and the provider issued two official updates as the issue was investigated and resolved.

An outage briefly affected the Vercel Dashboard, the v0 Dashboard, and the Vercel API, causing 5xx errors for a short period. Production and preview deployments were not affected. The outage began at 5:56 PM UTC and was resolved by 6:01 PM UTC, lasting about 5 minutes. The incident impacted three components: Dashboard, v0 Dashboard, and API.

The provider issued two status updates during the incident, first indicating investigation and later confirming recovery across the affected components.

Vercel experienced a partial outage affecting the Build & Deploy / Builds component, preventing new deployment builds from finishing and causing builds to queue. The outage began at 3:51 PM UTC and lasted about 30 minutes, impacting developers attempting to deploy applications or release new versions. Builds could be delayed or fail to complete during the incident.