Vercel outage history

An incident affected Vercel's Dashboard and Cron Jobs, causing degraded performance and delays in deployment updates. The issue began at 9:06 PM UTC and persisted until 11:46 PM UTC, lasting about 2 hours and 40 minutes. Users experienced cron updates taking longer to take effect after deploys, and dashboard interactions were intermittently slower during the window. The incident affected two components: Dashboard and Cron Jobs.

Vercel issued four status updates during the incident, describing investigation, monitoring, and recovery progress. By 9:31 PM UTC, cron updates were observed to take effect immediately after deploys, and full restoration occurred with the final update at 11:46 PM UTC.

Vercel reported a brief incident in which elevated GitHub API errors affected the CI/CD Git Integrations and the Dashboard, causing degraded functionality for builds and project dashboards. The outage began on 10:36 AM UTC and was resolved by 11:26 AM UTC, lasting approximately 50 minutes.

During the incident, the status page published two updates, describing ongoing investigation and eventual restoration as the affected components returned to normal.

Vercel experienced a brief issue where the Data Cache did not respect manual purge events. On-demand, tag-based, and time-based revalidations continued to operate normally, but manual purge requests could be ignored by the Data Cache. The incident began at Feb 5, 2025 1:06 PM UTC and the status changed to a warning at Feb 5, 2025 1:11 PM UTC. The problem lasted about 55 minutes, with the Data Cache returning to normal by Feb 5, 2025 2:01 PM UTC. The issue affected the Data Cache component, potentially causing stale content to persist after purge actions.

A minor incident affected Vercel's deployment workflow, with cron jobs not updating for new deployments. This caused cron-based deployment triggers and related builds to misreport changes for a period. The issue began at 5:26 AM UTC and was resolved by 7:06 AM UTC, lasting roughly 1 hour and 40 minutes. The Build & Deploy / Builds component moved to a degraded state during the incident, and Cron Jobs recovered once the issue was resolved. The provider issued 2 status updates as the team investigated and communicated progress.

The outage affected Vercel Preview Environments, with users unable to add domains as the Dashboard component experienced related issues. The incident began at 8:01 PM UTC and was resolved by 8:31 PM UTC, lasting about 30 minutes. The Vercel status page posted two updates, starting with an investigation and then confirming resolution, with the impact confined to Preview Environments.

The incident affected Vercel deployments for GitHub and GitHub login, with the Dashboard and API components showing degraded status. The outage lasted about 20 minutes, beginning at 2:56 PM UTC and resolving by 3:16 PM UTC. During this window, users may have experienced delays deploying projects via GitHub and issues logging in with GitHub.

The provider published two status updates during the incident, with the first at Jan 30, 2025 2:56 PM UTC indicating a degraded state and a follow-up at Jan 30, 2025 3:16 PM UTC restoring services. The issue affected 2 components: Dashboard and API, and was resolved when those components returned to normal.

Vercel experienced a brief degradation in build processing, with elevated queue times reported for a small number of customers. Existing deployments and live traffic were not affected. The incident began at 3:56 PM UTC and was resolved by 5:16 PM UTC, lasting about 1 hour 20 minutes. The issue was centered on the Build & Deploy / Builds component.

Vercel posted two status updates during the incident to communicate the investigation and resolution, noting that the issue affected Builds but did not impact existing deployments or live traffic.

Vercel users attempting to purchase domains via the Vercel Dashboard encountered intermittent errors affecting the Domain Registration feature. Some customers were unable to complete domain purchases during the incident. The outage began at 7:41 AM UTC and was resolved by 8:51 AM UTC.

Vercel’s status page tracked the issue under Domain Registration, with the component listed as degraded during the event and restored after about one hour. The provider issued 2 status updates over the course of the incident, and the total duration was approximately 1 hour 10 minutes.

An outage impacted Vercel's verification endpoints, causing 502 errors across multiple verification endpoints. This led to partial disruption for users relying on verification APIs and the Dashboard UI.

The outage began at Jan 14, 2025 9:01 AM UTC and was resolved by Jan 14, 2025 10:31 AM UTC, lasting about 1 hour and 30 minutes. The Vercel status page issued 3 updates during the incident, describing the investigation and later recovery. By Jan 14, 2025 10:31 AM UTC both the API and the Dashboard had returned to normal operation.

Vercel reported elevated error rates for builds due to npm registry network errors, impacting some builds in the Build & Deploy path. The incident began at Jan 8, 2025 11:31 PM UTC and was resolved by Jan 9, 2025 1:01 AM UTC, lasting about 1 hour 30 minutes. The status page issued two updates during the incident describing elevated build errors and ongoing monitoring before returning to normal. Affected component: Build & Deploy / npm Registry.