Vercel incident history

Right now: clear, by Vercel's own status page, mirrored every five minutes.

57
incidents kept since 18 May 2026
3
in the last 30 days
55m
median time to resolve, once posted
56%
resolved within an hour

How far back this goes: Vercel's feed exposed its 50 most recent incidents when we began mirroring on 25 September 2026, so this page covers 175 days so far and grows from here. Impact labels (17 major or critical) are Vercel's own. We don't compare providers on this page; the windows aren't equal yet.

What our probes saw

18 of these incidents had monitors depending on Vercel under evaluation, from three continents. In none of them did all three probes agree on a failure: the sites behind it never noticed. Single-region blips aren't counted; they're what the engine suppresses.
5 Nov 2026
Build delays and degraded Vercel Dashboard performance
418 evals, no confirmed failure
23 Oct 2026
Delays in Logs and Observability data
523 evals, no confirmed failure
12 Oct 2026
Increased build and deployment failures
1539 evals, no confirmed failure
10 Oct 2026
Delays in Drains, Observability, and Workflow in Washington (iad1)
600 evals, no confirmed failure
6 Oct 2026
Vercel Auth login failures for pages with Deployment Protection enabled
407 evals, no confirmed failure
6 Oct 2026
Elevated Sandbox error rates in Paris (cdg1)
432 evals, no confirmed failure
28 Sept 2026
Build failures and 500 errors for functions using Edge runtime
438 evals, no confirmed failure
18 Sept 2026
Deployment stuck in initializing state
505 evals, no confirmed failure

Which parts of Vercel the incidents touched

Builds
19
Dashboard
11
Functions
6
Observability
5
Workflow
4
Logs
4

Every incident we hold, newest first

16 Sept 2026
none
—
1 Sept 2026
major
59m 6s
6 Aug 2026
minor
1h 52m
25 Jul 2026
maintenance
22h 48m
23 Jul 2026
critical
54m 57s
10 Jul 2026
minor
2h 6m
10 Jul 2026
minor
2h 42m
10 Jul 2026
none
—
8 Jul 2026
minor
—
25 May 2026
minor
1h 23m
21 May 2026
minor
6h 29m
18 May 2026
minor
40m 41s

Source: Vercel's public status page at www.vercel-status.com, mirrored every five minutes. Data as JSON: /upstream/vercel/incidents.json. CC BY 4.0.

If your site depends on Vercel, Repose holds the page when the cause is upstream. How the hold decision works →