Vercel Outage History

Vercel's AI Gateway experienced a brief outage that made model requests and metadata API calls unavailable. The incident began at 8:01 PM UTC and was resolved by 8:41 PM UTC, lasting about 40 minutes. Vercel posted two status updates acknowledging the issue, first noting an investigation and AI Gateway being down, then confirming that the gateway was back online. The impact appeared isolated to the AI Gateway component, with no broader service disruption reported for other Vercel features.

Vercel reported a brief degradation in Edge Config within Storage, with an elevated rate of HTTP errors affecting Edge Config endpoints for a subset of users. The issue began when the status moved to a degraded state at 6:16 PM UTC after initial checks at 6:14 PM UTC and was resolved by 6:41 PM UTC, lasting about 27 minutes. Vercel issued two status updates during the incident, including an initial Investigating message and a follow-up stating Edge Config had returned to normal. The affected component was Storage / Edge Config.

Vercel faced intermittent errors affecting public APIs and new builds, causing API request failures and build disruptions for developers. The incident impacted two components: API and Build & Deploy / Builds, leading to degraded developer experience during the outage. The outage began at 5:16 PM UTC and was resolved by 6:01 PM UTC. The incident lasted about 45 minutes. The provider issued 2 status updates over the course of the incident, first noting an investigation into intermittent errors and later confirming restoration of API and Build services.

Vercel reported intermittent build failures for new deployments that use Secure Compute or Static IPs, while existing deployments remained unaffected. Users deploying new projects could experience failed or stalled builds and were advised to redeploy once the issue was resolved. The outage began at Oct 28, 2025 11:16 PM UTC and was resolved by Oct 29, 2025 12:56 AM UTC, lasting roughly 1 hour and 40 minutes.

The provider issued 2 status updates during the incident, confirming the intermittent failures and the fix that restored build reliability.

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.