Vercel Outage History

From 1:21 AM UTC, Vercel listed a degraded condition for the Dashboard due to delayed issuance of on-demand usage invoices. The status message noted that invoicing would be delayed and issued within the next 24 hours, impacting users relying on up-to-date invoice data. The issue persisted for about two days and three hours, with the Dashboard as the primary surface affected. The incident ended when the status returned to normal on 5:11 AM UTC and Vercel issued updates outlining the resolution timeline.

During the event, the provider issued two official status updates detailing the delay and the expected resolution window.

The incident affected the Vercel v0 Dashboard as upgrading v0 teams to Business or Team plans and adding v0 credits experienced issues. The event began at 1:36 AM UTC and was resolved by 1:46 AM UTC, lasting about 10 minutes. During this period, users attempting to upgrade plans or apply credits on the v0 path may have encountered service limitations. The provider issued 2 status updates while investigating the problem, and the v0 / Dashboard component returned to normal after the fix.

On Oct 21, 2025 5:11 PM UTC, Vercel flagged a degraded state for Log Drains in the us-east-1 region, warning that data delivered to drains—logs, traces, web analytics, and speed insights—may be delayed. The incident reference notes delays observed around Oct 21, 2025 5:06 PM UTC in the iad1 deployment. The issue appeared regional to the us-east-1 environment and affected the timely delivery of data to drains.

The outage began at Oct 20, 2025 8:01 PM UTC and lasted a little over 11 hours, severely impacting API access, dashboard functionality, and deployment creation. Users experienced API errors, failed deployments, and dashboard instability as the incident unfolded. Early in the incident, traffic in the IAD1 region was rerouted to healthy regions while engineers worked to isolate impact and restore service. The issue spread across multiple components over the course of the event, with ongoing updates indicating degraded performance across several services before full recovery.

Vercel issued frequent status updates throughout the incident, detailing progress across many components including Secure Compute / Builds, v0 / Output Generation, Domain Registration, Edge Functions, and Edge Network in IAD1. The company described steps to reroute traffic, backfill data, and restore deployments, and reported milestones as services came back online. By Oct 21, 2025 7:06 AM UTC, several core services had returned to normal operation with lingering backfill tasks for some components.

Vercel experienced a brief issue in the Dashboard where domain detail pages for domains owned by account scopes could not be accessed. This prevented viewing or editing domain settings for affected domains and impacted domain-management workflows.

The incident began at Oct 16, 2025 5:26 AM UTC and was resolved by Oct 16, 2025 8:51 AM UTC, lasting approximately 3 hours and 25 minutes. The Dashboard component briefly operated in a degraded state, and Vercel issued two status updates as the situation evolved.

Vercel experienced an outage that prevented creating new deployments, while existing deployments and live traffic remained functional. The disruption began at 1:41 PM UTC and primarily impacted the Build & Deploy / Builds component, with users unable to deploy new builds via Git integrations, the CLI, or the API. The issue progressed with API and Dashboard reporting degraded status before all services recovered.

Over about 3 hours, Vercel issued 3 status updates detailing the progression from deployment failures to recovery. By 4:41 PM UTC, the Build & Deploy / Builds, API, and Dashboard components had returned to normal operation.

Vercel reported delays in updating DNS records for domains using Vercel Nameservers, including new domains acquired through Vercel, domains that recently switched to Vercel Nameservers, and new DNS records added to domains already using Vercel's Nameservers. DNS propagation could be slowed for affected sites and configurations during the incident. The DNS component entered a degraded state at Sep 16, 2025 7:06 PM UTC and remained until Sep 17, 2025 10:01 AM UTC when the service returned to normal, following two official updates.

During the incident, Vercel issued two status updates; the DNS service was degraded for about 14 hours and 55 minutes before returning to normal.

Vercel experienced a partial outage tied to Edge Config, affecting Edge Functions and Edge Middleware. During the incident, users may have encountered elevated errors on edge routes and requests processed by middleware. The issue was first investigated at Sep 5, 2025 5:39 PM UTC and the status page listed a partial outage at Sep 5, 2025 5:41 PM UTC. The outage lasted about 57 minutes, with service restored by Sep 5, 2025 6:36 PM UTC.

Two official status updates were published during the incident to communicate progress. Edge Functions and Edge Middleware returned to normal operation after remediation.

Vercel experienced a brief degradation in its user registration service, with signup attempts failing for some users and others taking longer than usual. Existing user logins were not affected, and no other parts of the platform were reported as impacted.

The outage began at Sep 3, 2025 10:56 AM UTC and was resolved by 11:51 AM UTC, lasting about 55 minutes. The provider issued two status updates during the incident, describing an ongoing investigation and eventual recovery, with the signup service returning to normal after the event.

Vercel experienced an outage in its Secure Compute builds service that prevented builds from starting and disrupted deployment workflows for affected users. The issue affected two components: Secure Compute / Builds and Build & Deploy / Builds. The outage began at Aug 26, 2025 3:46 PM UTC and was resolved by Aug 26, 2025 5:11 PM UTC, lasting about 1 hour and 25 minutes. Status page updates indicated initial investigation around Aug 26, 2025 3:44 PM UTC, escalation to a full outage by Aug 26, 2025 4:06 PM UTC, and restoration by Aug 26, 2025 5:11 PM UTC. The provider issued 3 status updates during the incident.