Skip to content

Vercel outage history and postmortems

Cloud and hosting · San Francisco, US · 32 incidents in 90 days · 99.97% implied uptime · last 6d ago

Status page Compare

Incidents

132 on file
StartedIncidentDuration
Sep 1821:36 UTCDeployment stuck in initializing state55m
Sep 1820:32 UTCElevated Errors Triggering Deployments50m
Sep 1815:14 UTCElevated Vercel KMS and Connect Errors0m
Sep 1707:11 UTCFailures delivering Logs to Drains0m
Sep 1616:58 UTCMissing Web Analytics and Speed Insights data0m
Sep 1603:21 UTCInvoice Generation Paused0m
Sep 1017:42 UTCElevated error rate on Connect and Passport1h 34m
Sep 419:11 UTCElevated latency in VCR, Blob, and Sandbox API1h 16m
Sep 119:59 UTCIncreased deployment failures59m
Aug 2603:06 UTCFailures logging in with Vercel CLI1h 22m
Aug 2519:27 UTCElevated build initialization times38m
Aug 2017:46 UTCNew container functions are failing47m
Aug 2011:14 UTCLogs unavailable to query in Dashboard11m
Aug 1900:28 UTCElevated errors for Workflow streams0m
Aug 1714:30 UTCPartial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard6h 55m
Aug 1413:08 UTCDynamic API routes returned 404 errors for some deployments0m
Aug 616:37 UTCDelays delivering log drains1h 53m
Jul 2518:57 UTCVercel Community temporarily unavailable22h 49m
Jul 2319:00 UTCTelemetry data loss for Drains0m
Jul 2307:33 UTCTimeouts loading charts and observability data in Dashboard45m
Jul 2306:47 UTCDashboard authentication errors55m
Jul 1714:12 UTCIncreased invocation failures for Hobby Team functions1h 7m
Jul 1623:09 UTCGitHub-linked deployments and authentication affected1h 33m
Jul 1608:39 UTCSAML Single Sign-On (SSO) errors2h 6m
Jul 1606:07 UTCMissing Build CPU Minutes Usage Data3h 20m
Jul 1523:04 UTCErrors accessing teams that require 2FA30m
Jul 1021:22 UTCIncreased Build failure rates2h 7m
Jul 1019:53 UTCErroneous budget notifications2h 42m
Jul 1017:44 UTCDelays loading Build Logs0m
Jul 819:13 UTCDelays Processing Builds0m
Jul 216:31 UTCDegraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)15m
Jul 116:57 UTCIncrease in Workflow runs stuck in pending, failed1h 33m
Jun 2613:08 UTCIntermittent Login Failures on Vercel Dashboard2h 6m
Jun 2507:45 UTCIncrease in Workflow runs stuck as pending5h 58m
Jun 2323:24 UTCDegraded Domain Search in Vercel Dashboard10m
Jun 1917:54 UTCResolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions0m
Jun 1613:39 UTCPartial disruption of Observability, Analytics, Firewall, and Usage in dashboard2h 1m
Jun 1421:03 UTCElevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)4h 21m
Jun 914:09 UTCElevated Build Errors for Secure Compute/Static IPs Projects36m
Jun 818:57 UTCElevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region1h 2m
About Vercel

Vercel Inc. is an American cloud application company. The company created and maintains the Next.js web development framework.

The last year, day by day

No incident Minor Major CriticalDeeper colour: longer outage

Downtime, added up

Cloud and hosting median
43m

Vercel: 39m weighted downtime in range, category median 43m.

32 incidents, 10 major or critical, 32h 3m of incident time (9h 21m major or critical, 22h 42m partial), longest 22h 49m, implied uptime 99.97%, between Jun 28, 2026 and Sep 25, 2026.

Stated causes

131 incidents with no cause stated.

Across fru.dev:Company profileComplianceFree tiersPaydaysChangefeedSLAsTechConfUptime

Questions

Is Vercel down right now?

Check Vercel's own status page at https://www.vercel-status.com for the live state. This page shows Vercel's incident history from that page; the most recent incident started 2026-09-18: "Deployment stuck in initializing state".

How often does Vercel have outages?

Vercel posted 32 incidents in the last 90 days and 132 in the last year, 10 of them major or critical in the last 90 days. The median incident lasted 53m.

When was Vercel's last major outage?

2026-09-18: "Elevated Errors Triggering Deployments", lasting 50m.

What usually causes Vercel incidents?

Where Vercel explained the cause, the most common was software bug (1 incidents). Most status updates do not name a cause.

Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Outages by email

Saturday mornings: the week's major outages, new postmortems and disclosed breaches, only in weeks that had some.

Double opt-in. Unsubscribe any time.