Vercel Outage History

Vercel experienced a partial disruption where firewall observability data appeared delayed in the Vercel Dashboard, reducing visibility into firewall metrics. The issue affected two components, Firewall and Dashboard. The outage began at 10:41 PM UTC and caused data visibility issues for a period, with recovery efforts focusing on data from 9:58 PM UTC to 10:50 PM UTC. The incident lasted until 2:56 AM UTC, when the dashboards returned to normal operation.

Vercel experienced an outage starting at Feb 7, 2026 8:46 AM UTC with elevated dashboard load times and higher error rates on builds, impacting the Dashboard and Build & Deploy workflows. Users attempting to load dashboards or trigger builds would have faced delays and failures. The outage lasted approximately 2 hours and 35 minutes and was resolved by Feb 7, 2026 11:21 AM UTC. The incident involved two affected components: Dashboard and Builds, with updates posted during the incident.

The Vercel Dashboard experienced a partial outage due to delays in firewall observability. The incident began at Feb 5, 2026 4:16 PM UTC when the Dashboard moved from operational to degraded while engineers investigated firewall observability delays. The issue progressed to a degraded state by Feb 5, 2026 4:56 PM UTC and was resolved by Feb 5, 2026 8:51 PM UTC, with the Dashboard returning to normal after the incident. The outage lasted roughly 4 hours and 35 minutes. Users reported the issue mid-incident, including a single report from Dammam around 6:30 PM UTC describing the site as unresponsive.

Vercel experienced elevated error rates when creating new sandboxes and increased latency for new deployments, impacting developers attempting to create sandboxes and deploy builds. The issues affected Sandboxes and the Build & Deploy / Builds pipeline, causing sandbox creation to fail or slow and deployments to take longer than normal.

Timeline and response: The issue was first listed as a warning at 6:41 PM UTC. By 8:51 PM UTC latency for deployments was reported. A fix was implemented by Feb 3, 2026 9:46 PM UTC and monitoring continued. Service returned to normal by 9:56 PM UTC. The provider issued 4 status updates during the incident.

Duration and resolution: The incident lasted roughly 3 hours and 15 minutes, ending when the status moved back to up at 9:56 PM UTC.

On 2026-02-03, Vercel faced a multi-component outage affecting the Dashboard, API, and Builds. The incident began with elevated errors and slowness on the Dashboard at 3:26 PM UTC, while existing deployments and live traffic were initially unaffected. By 4:26 PM UTC, fixes were being applied and partial recovery was observed across API, Dashboard, and Builds. The outage escalated to a full disruption from 5:01 PM UTC to 5:31 PM UTC, with services restored by 5:31 PM UTC.

An incident affected Vercel's CI/CD / Git Integrations, causing elevated git clone durations that slowed build starts for a subset of projects. The issue began at 1:24 AM UTC and escalated to a warning at 2:46 AM UTC as engineers investigated clone performance and infrastructure behavior. The status page noted ongoing investigation into the root cause and clone performance metrics.

The issue was resolved by 11:11 AM UTC, with the status reverting to up. Over the course of the incident, Vercel issued 2 official updates describing progress and investigation. The impact remained limited to building workflows relying on Git integration, rather than a full service outage.

Vercel experienced elevated connection latency and intermittent timeouts in the Dublin edge region (DUB1), impacting traffic served from that location. The incident began at Jan 28, 2026 5:21 PM UTC when the status page indicated degraded performance and a fix was being rolled out. The affected component was Edge Network / DUB1, and users likely saw slower responses or intermittent timeouts for requests routed through the Dublin region.

The issue was resolved by Jan 28, 2026 8:21 PM UTC as the rollout completed. Vercel published two status updates during the incident, and normal service resumed after roughly three hours.

Vercel experienced delayed data ingestion and display across three components: Dashboard, Speed Insights, and Web Analytics. This caused delayed or stale metrics in Observability, Usage, and Audit Logs dashboards, impacting analytics workflows. The issue began around Jan 26, 2026 3:14 PM UTC when Vercel announced an investigation and persisted for approximately 2 hours and 47 minutes, with service restoring by Jan 26, 2026 6:01 PM UTC. The provider issued two status updates during the incident to communicate progress.

On Jan 23, 2026 3:36 AM UTC, Vercel reported an incident affecting Domain Registration, with domain purchases including dynamic registrant information failing. The outage lasted about 55 minutes and was resolved by Jan 23, 2026 4:31 AM UTC when the status returned to up. Users attempting to register domains or update registrant details during the window may have encountered errors or failed transactions.

The issue prompted two official status updates as Vercel investigated the cause and subsequently restored normal service for Domain Registration.

Vercel reported elevated build failure rates affecting a subset of projects. Builds in the Build & Deploy / Builds component failed for some users, while existing deployments and live traffic remained accessible. The incident began at 1:16 AM UTC and was resolved by 2:26 AM UTC, lasting about 1 hour and 10 minutes. The provider issued 2 status updates during the incident as engineers investigated and worked toward recovery.