CheckUpstream measured Vercel at 100.000% availability across 2817 independent checks (global · api). 56 incidents were recorded in the past 12 months; the most recent resolved 6 days ago after 1 hour. Status signals are polled from Vercel's official Atlassian Statuspage status page, alongside independent probes and community reports. Vercel publishes 1 product-level SLA uptime commitment (up to 99.99%), and service credits must be claimed within 30 days of a breach.
30 days measured availability how this is computed
100.000%
global · api · n=2817 · p95 464ms (30d)
Share of our own checks against Vercel endpoints that returned Vercel's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 9 incidents · 28 of 30 days with none posted · 2h 37m of declared impact
Within Vercel's published 99.99% target for this window.
Fewer incidents in the last 30 days than 11% of 232 tracked services.
Share of each window with no impact declared by Vercel
7d
99.977%
30d
99.635%
90d
99.762%
180d
99.288%
1y
99.649%
Downtime like this can be refundable
If you're a paying Vercel customer, outages in these windows may count against Vercel's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Vercel entitlement →Does Vercel actually matter to you?
A Vercel outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 9 incidents Vercel published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Vercel takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 26, 03:06 UTC · resolved in 1h 24m · Resolved
Aug 25, 19:27 UTC · resolved in 43m · Resolved
Aug 25, 19:27 UTC · resolved in 7m · Resolved
Live Vercel status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/vercel)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Vercel is currently Operational. CheckUpstream tracks Vercel in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Vercel's last resolved incident started 6 days ago and lasted 1h 24m (a partial outage).
Looking for the live "is Vercel down" view? See the Vercel Live status page.
Aug 20, 17:46 UTC · resolved in 53m · Resolved
Aug 20, 17:46 UTC · resolved in 8m · Resolved
Aug 6, 16:37 UTC · resolved in 3m · Resolved
Jul 23, 06:47 UTC · resolved in 1h 3m · Resolved
Jul 17, 14:12 UTC · resolved in 1h 12m · Resolved
Jul 16, 23:09 UTC · resolved in 1h 35m · Resolved
Jul 16, 08:39 UTC · resolved in 2h 10m · Resolved
Jul 16, 06:07 UTC · resolved in 3h 27m · Resolved
Jul 15, 23:04 UTC · resolved in 35m · Resolved
Jul 10, 21:22 UTC · resolved in 2h 8m · Resolved
Jul 10, 19:15 UTC · resolved in 3h 29m · Resolved
Jul 8, 18:05 UTC · resolved in 4h 25m · Resolved
Jun 1, 19:21 UTC · resolved in 48m · Resolved
Vercel's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Vercel endpoints. It is the share of checks that returned the expected response, not a figure taken from Vercel's status page.
Sign up to CheckUpstream and add Vercel to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Vercel's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.