v0 change history

v0 reported a major incident affecting builds and Git integrations from 2026-10-12 13:35 UTC to 2026-10-12 20:11 UTC, lasting 6 h 36 min. Some builds failed or deployments failed to start; v0 cited an upstream GitHub incident affecting GitHub-connected projects. Deployment-status events were also delayed; the backlog was processed and the incident resolved.

v0 reported a major degradation in Washington (iad1): some customers experienced delayed Drains delivery, logs, metrics and traces, with Workflow runs remaining pending. It started at 2026-10-10 00:15 UTC and resolved at 2026-10-10 01:37 UTC, lasting 1 h 21 min. A fix restored delivery, delayed data was processed, and all services recovered.

Vercel Auth logins failed for pages with Deployment Protection enabled, affecting Routing Middleware in a major-impact outage. It started at 2026-10-06 16:10 UTC and was resolved at 2026-10-06 16:26 UTC; the reported duration was 15 min. A fix was implemented, but no cause was stated.

v0 reported a major incident causing elevated errors triggering deployments in Build & Deploy - Builds, Builds, from 2026-09-18 20:32 UTC to 2026-09-18 21:22 UTC (49 min). A fix was implemented and the incident resolved; existing deployments and traffic were unaffected, and no customer action was required.

Some customers experienced increased errors from Connect and Passport in a major-impact incident starting 2026-09-10 17:42 UTC and resolved at 2026-09-10 19:16 UTC, lasting 1 h 33 min. v0 reported implementing a fix and confirmed both services fully recovered; no cause was stated.

v0 reported a major incident causing some deployments using IAD1 Function regions or Routing Middleware to fail. It lasted 59 min, from 2026-09-01 19:59 UTC to 2026-09-01 20:58 UTC; a fix was deployed and Builds recovered.

Vercel CLI login (vc login) experienced errors in a major-impact incident from 2026-08-26 03:06 UTC to 2026-08-26 04:28 UTC, lasting 1 h 22 min. The vendor reported identifying the source and testing a fix before marking the incident resolved; affected customers had trouble logging in through the CLI.

v0 reported a major Functions incident: newly deployed container functions could return 5XX errors starting at 2026-08-20 17:46 UTC. Customers could temporarily use a previously working deployment; a fix was deployed at 2026-08-20 18:23 UTC. The incident was resolved at 2026-08-20 18:34 UTC, lasting 47 min.

v0 reported a major outage preventing runtime log queries in the Dashboard from 2026-08-20 11:14 UTC to 2026-08-20 11:25 UTC, lasting 11 min. Log ingestion and build-log queries were unaffected. A fix restored runtime-log queries at 11:21 UTC, with full recovery confirmed at 11:25 UTC.

v0 resolved a major Drains incident, recorded as starting 2026-07-23 19:00 UTC with a computed duration of 0 min. Its update reports unrecoverable traces and events between 19:12 and 19:18 UTC on July 23, 2026; undelivered logs remain accessible and exportable in the Logs UI dashboard. A fix was deployed.

v0 reported a major incident causing Dashboard chart and observability-data timeouts for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. It started at 2026-07-23 07:33 UTC and was resolved at 2026-07-23 08:18 UTC, lasting 45 min. The team identified the source and implemented a fix, but did not specify the cause.

v0 reported a critical incident involving dashboard authentication errors that made the dashboard inaccessible for some users. It started at 2026-07-23 06:47 UTC and lasted 54 min, resolving at 2026-07-23 07:41 UTC; a fix was implemented by 2026-07-23 07:08 UTC.

A major SAML Single Sign-On (SSO) outage prevented login and access to SSO-protected teams through the Vercel dashboard and CLI. It started at 2026-07-16 08:39 UTC and was resolved at 2026-07-16 10:45 UTC, lasting 2 h 5 min. The vendor reported implementing a fix but did not specify the root cause.

Some users experienced intermittent Vercel Dashboard login errors; impact was major. The incident was recorded as starting at 2026-06-26 13:08 UTC, though the vendor reported onset at 11:30 AM UTC, and resolved at 2026-06-26 15:14 UTC; computed duration was 2 h 5 min. A fix was implemented; no cause was stated.

A major Workflow degradation left some recently deployed projects stuck pending and not delivering queued messages from 2026-06-25 07:45 UTC to 2026-06-25 13:43 UTC, lasting 5 h 58 min. A fix was rolled out; the interim workaround was an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume new runs.

A major incident caused elevated latency and errors in FRA1 (Frankfurt, Germany), affecting the region and its CDN. It started at 2026-06-14 21:03 UTC and was resolved at 2026-06-15 01:24 UTC, lasting 4 h 20 min. Traffic was rerouted to CDG1 to mitigate impact, then fully restored to FRA1.

v0 reported a major incident with elevated build errors for Secure Compute/Static IPs projects, affecting Builds and Secure Compute - Builds. It started at 2026-06-09 14:09 UTC and was resolved at 2026-06-09 14:46 UTC, lasting 36 min; a fix was implemented, but no cause was stated.