Skip to content

Outage tracker

Vercel: availability history

Measured availability by region over 18 days of our own probe history, plus every outage RealUptime detected in that window.

← Back to Vercel's live status

We started measuring Vercel on 8/8/2026, which is 18 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%2332
US-West100.00%2235
Europe100.00%2224
Asia-Pacific100.00%2200

Monthly summary

Tracking Vercel since Aug 20, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Sep 2025not tracked
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 20, 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Vercel: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Vercel's own status page contribute nothing to these figures.

Incident log

Every outage our own probes detected for Vercel in the last 90 days, or since we started measuring it if that is more recent. Nothing here comes from a user report or the vendor's own status feed; see the live page for those, kept in their own labeled blocks.

No outages detected for Vercel since we started measuring it on 8/20/2026. We show nothing from before that date.

Full detail on what a probe does and does not prove is in the methodology page.