StatOSS

Vercel uptime

Vercel, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

api.vercel.com/v2/userEvery 5 minutes

Vercel is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:52 UTC from Singapore: 403 in 342 ms.

Last 24 hours

Up for 51 d 10 h100% passed

287 checks, median 203 ms from Falkenstein, all passed

95% under 234 ms

Response time by region
EuropeEurope203 ms
N. AmericaNorth America99 ms
AsiaAsia362 ms
OceaniaOceania191 ms

Medians over this range, on one scale up to 800 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,804 checks, median 434 ms from Falkenstein, all passed

95% under 553 ms

Response time by region
EuropeEurope434 ms
N. AmericaNorth America186 ms
AsiaAsia584 ms
OceaniaOceania423 ms

Medians over this range, on one scale up to 800 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Vercel passed 8,862 of 8,862 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,014 of 2,0140
30 days100%8,862 of 8,8620
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany200 ms377 ms218 ms421
Helsinki, Finland221 ms255 ms233 ms42
Ashburn, USA109 ms207 ms120 ms502
Copenhagen, Denmark257 ms313 ms270 ms42
Singapore399 ms738 ms446 ms505
Sydney, Australia269 ms644 ms308 ms503

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Hosting for front ends and Next.js apps, with builds, serverless and edge functions.

StatOSS sends GET https://api.vercel.com/v2/user and counts the check as passed on status 403 within 10 seconds. The REST API's user endpoint, which the CLI talks to. Without a token Vercel answers 403 Forbidden and says the request is missing an authentication token.

It checks Vercel's API, not the sites deployed on Vercel, which are served from its edge network.

Vercel reports its own incidents at www.vercel-status.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 403.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.