Vendor Status Watch

← all vendors

Vercel status history

Current state: operational — “All Systems Operational” per https://www.vercel-status.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

9incidents, last 30 days
30incidents, last 90 days
52incidents on record
Incidents per week, last 12 weeks:

How long do Vercel incidents last?

62 minmedian incident duration51 measured
6.0 h90th percentile1 in 10 ran longer
56 minmedian, major/critical only14 incidents

From 51 incidents with a vendor-posted start and resolve time. Longest on record: Missing Build CPU Minutes Usage Data — 10.0 h (2026-05-20 20:07 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (52)

StartedIncidentStatusImpactDuration
2026-09-10 17:42 UTCElevated error rate on Connect and Passportresolvedmajor1 h 33 min
2026-09-04 19:11 UTCElevated latency in VCR, Blob, and Sandbox APIresolvedminor1 h 15 min
2026-09-01 19:59 UTCIncreased deployment failuresresolvedmajor59 min
2026-08-26 03:06 UTCFailures logging in with Vercel CLIresolvedmajor1 h 22 min
2026-08-25 19:27 UTCElevated build initialization timesresolvedminor37 min
2026-08-20 17:46 UTCNew container functions are failingresolvedmajor47 min
2026-08-20 11:14 UTCLogs unavailable to query in Dashboardresolvedmajor11 min
2026-08-18 23:00 UTCElevated errors for Workflow streamsresolvednone0 min
2026-08-17 14:30 UTCPartial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboardresolvedminor6 h 54 min
2026-08-14 13:08 UTCDynamic API routes returned 404 errors for some deploymentsresolvednone0 min
2026-08-06 16:37 UTCDelays delivering log drainsresolvedminor1 h 52 min
2026-07-25 18:57 UTCVercel Community temporarily unavailableresolvedmaintenance22 h 48 min
2026-07-23 19:00 UTCTelemetry data loss for Drainsresolvedmajor0 min
2026-07-23 07:33 UTCTimeouts loading charts and observability data in Dashboardresolvedmajor45 min
2026-07-23 06:47 UTCDashboard authentication errorsresolvedcritical54 min
2026-07-17 14:12 UTCIncreased invocation failures for Hobby Team functionsresolvedminor1 h 06 min
2026-07-16 23:09 UTCGitHub-linked deployments and authentication affectedresolvedminor1 h 32 min
2026-07-16 08:39 UTCSAML Single Sign-On (SSO) errorsresolvedmajor2 h 05 min
2026-07-16 06:07 UTCMissing Build CPU Minutes Usage Dataresolvedminor3 h 20 min
2026-07-15 23:04 UTCErrors accessing teams that require 2FAresolvedminor30 min
2026-07-10 21:22 UTCIncreased Build failure ratesresolvedminor2 h 06 min
2026-07-10 19:15 UTCErroneous budget notificationsresolvedminor3 h 20 min
2026-07-09 13:16 UTCDelays loading Build Logsresolvednone0 min
2026-07-08 18:05 UTCDelays Processing Buildsresolvedminor1 h 08 min
2026-07-02 16:31 UTCDegraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)resolvedminor14 min
2026-07-01 16:57 UTCIncrease in Workflow runs stuck in pending, failedresolvedminor1 h 33 min
2026-06-26 13:08 UTCIntermittent Login Failures on Vercel Dashboardresolvedmajor2 h 05 min
2026-06-25 07:45 UTCIncrease in Workflow runs stuck as pendingresolvedmajor5 h 58 min
2026-06-23 23:24 UTCDegraded Domain Search in Vercel Dashboardresolvedminor10 min
2026-06-19 17:54 UTCResolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functionsresolvednone0 min
2026-06-16 13:39 UTCPartial disruption of Observability, Analytics, Firewall, and Usage in dashboardresolvedminor2 h 00 min
2026-06-14 21:03 UTCElevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)resolvedmajor4 h 20 min
2026-06-09 14:09 UTCElevated Build Errors for Secure Compute/Static IPs Projectsresolvedmajor36 min
2026-06-08 18:57 UTCElevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Regionresolvedminor1 h 02 min
2026-06-01 19:21 UTCElevated Errors Creating New Deploymentsresolvedminor40 min
2026-05-28 16:00 UTCElevated Function Invocation Errors in Stockholm region (ARN1)resolvedminor59 min
2026-05-27 04:50 UTCElevated Errors on Vercel Dashboard (Project Overview Page)resolvedminor11 min
2026-05-25 14:58 UTCDelays Loading Runtime Logsresolvedminor1 h 23 min
2026-05-23 10:43 UTCElevated Build Failures (GitHub connected projects)resolvedminor8 h 00 min
2026-05-22 17:11 UTCBuild Failures for Some Next.js Deploymentsresolvednone0 min
2026-05-21 15:01 UTCElevated Build Errorsresolvedminor6 h 29 min
2026-05-20 20:07 UTCMissing Build CPU Minutes Usage Dataresolvedminor10 h 00 min
2026-05-18 21:42 UTCIncreased Function Invocation Errors - ERR_MODULE_NOT_FOUNDresolvedminor2 h 09 min
2026-05-18 15:00 UTCSupport cases cannot be submittedresolvedminor40 min
2026-05-15 10:34 UTCWorkflow usage amounts are incorrectly calculatedresolvedminor5 h 43 min
2026-05-09 04:45 UTCVercel Queues, and Vercel Workflow runs were delayedresolvedminor54 min
2026-05-08 18:30 UTCSSL Certificate Generation Delaysresolvednone45 min
2026-05-08 16:30 UTCDelays Processing Buildsresolvedminor10 min
2026-05-08 01:18 UTCElevated errors across multiple services in IAD1 (Washington, D.C., USA)resolvedminor5 h 20 min
2026-05-07 21:14 UTCElevated Errors Creating New Deploymentsresolvedminor33 min
2026-05-05 23:30 UTCIncreased error rate in Workflowsresolvedmajor49 min
2026-05-05 15:15 UTCFailures to load data across multiple services on the Vercel dashboard, API, and CLIresolvedminor9 h 22 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Vercel with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "vercel"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}