Vercel incident history

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

50
incidents kept since 18 May 2026
9
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 130 days so far and grows from here. Impact labels (14 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

11 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.
18 Sept 2026
Deployment stuck in initializing state
505 evals, no confirmed failure
18 Sept 2026
Elevated Errors Triggering Deployments
489 evals, no confirmed failure
17 Sept 2026
Failures delivering Logs to Drains
357 evals, no confirmed failure
16 Sept 2026
Invoice Generation Paused
358 evals, no confirmed failure
10 Sept 2026
Elevated error rate on Connect and Passport
616 evals, no confirmed failure
4 Sept 2026
Elevated latency in VCR, Blob, and Sandbox API
565 evals, no confirmed failure
1 Sept 2026
Increased deployment failures
122 evals, no confirmed failure
17 Aug 2026
Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard
803 evals, no confirmed failure

Which parts of Vercel the incidents touched

Builds
16
Dashboard
10
Functions
6
Web Analytics
3
Speed Insights
3
Firewall
3

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 →