Vercel Outage History

Developers relying on Vercel's Build & Deploy experienced delays as builds did not start promptly and some remained in an initializing state. The issue began at 6:06 PM UTC and affected build pipelines across projects.

Status updates indicated a progression toward recovery. By 6:41 PM UTC there were signs of recovery as the affected build queue began to drain. By 7:16 PM UTC build queues had returned to normal levels and processing was expected to be restored, and by 9:36 PM UTC the service was reported back to a stable state.

Vercel experienced a brief degradation across its CDN, Dashboard, and Functions in the iad1 (Washington, DC) and cle1 (Cleveland) regions. Users likely faced slower page loads, longer function execution times, and delayed dashboard responses during the incident. The issue began at 4:36 PM UTC. A fix was implemented and recovery began at 4:41 PM UTC, with full restoration by 4:51 PM UTC.

Some Vercel workflow runs became stuck in pending or failed states, causing delays for affected automations. The issue mainly affected older runs created between Jun 30, 2026 10:24 PM UTC and Jul 1, 2026 4:08 PM UTC; new workflow runs continued to process normally. Impact began around Jul 1, 2026 5:01 PM UTC as engineers started work on a fix.

Status updates indicated ongoing recovery, and the Workflow component returned to up by 6:31 PM UTC. During this time, new workflow runs were not impacted and normal operation resumed after the incident window.

Users trying to sign in to the Vercel Dashboard faced elevated errors beginning at 1:11 PM UTC, escalating to a partial outage by 1:26 PM UTC. The disruption persisted for about two hours, with intermittent login failures and degraded dashboard access reported across regions including the United States, Poland and Türkiye. The issue affected core dashboard functionality, hindering sign-ins and access to dashboard data.

An outage affected Vercel's Workflow feature, with recently deployed Workflow projects stalling in a pending state and not delivering queued messages. The issue began at 7:46 AM UTC and caused degraded operation across the platform as workflows failed to start or complete as expected.

Engineering teams identified the root cause and rolled out a fix. To minimize disruption, an instant rollback to a working deployment created before Jun 24, 2026 9:00 PM UTC was made available to resume operation on new runs. By 1:46 PM UTC, the fix had been fully rolled out and the Workflow component had returned to normal operation.

An incident affected the Domain Registration feature in the Vercel Dashboard, preventing customers from searching for and purchasing domains. The issue began at 11:26 PM UTC and impacted domain search for about ten minutes. A fix was implemented and monitoring started at 11:31 PM UTC, with the functionality returning to normal by 11:36 PM UTC. Vercel confirmed investigation and deployment of the fix, and subsequently restored full domain search capabilities.

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.