Cloud & hosting
Is Vercel down?
Live Vercel status, measured independently. We probe 6 Vercel endpoints from monitoring regions on every continent and record every outage we detect.
Vercel is up
Our probes are reaching Vercel normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website99.99% uptime, 30 days6 regions, 76 to 171 msCheckingp50107 msMedian responsep95235 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- API99.63% uptime, 30 days6 regions, 53 to 961 msCheckingp50549 msMedian responsep95686 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Dashboard99.99% uptime, 30 days6 regions, 165 to 1331 msCheckingp50716 msMedian responsep95923 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Documentation99.99% uptime, 30 days6 regions, 99 to 185 msCheckingp50132 msMedian responsep95301 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- Edge network (nextjs.org)99.66% uptime, 30 days6 regions, 84 to 193 msCheckingp50152 msMedian responsep95280 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- Official status feed99.66% uptime, 30 days5 regions, 215 to 546 msCheckingp50358 msMedian responsep95556 msSlowest 5% of checks500 ms250024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Vercel goes down
Follow these 6 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Vercel goes down. They don't count against your monitor quota. Free plan, no card required.
About Vercel outages
Vercel hosts a large share of Next.js applications and runs their serverless functions, edge middleware, image optimisation, and cron jobs. A Vercel incident can mean deployments hang, functions time out, or a whole region of sites returns errors.
We probe vercel.com, the dashboard, the API, the documentation, and a large production site served from Vercel's edge, so an edge-network incident is visible even when vercel.com is fine.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website vercel.com is unreachable. The dashboard is likely affected too. | httpvercel.com | HTTP 200 | 1 min |
API The Vercel API is not responding normally. CLI deploys and integrations fail. | httpapi.vercel.com/v2/user | HTTP 403 | 2 min |
Dashboard The Vercel dashboard is unreachable. Manual deploys and configuration changes are blocked. | httpvercel.com/login | HTTP 200 | 2 min |
Documentation Vercel's documentation is unreachable. | httpvercel.com/docs | HTTP 200 | 5 min |
Edge network (nextjs.org) A high-traffic site served from Vercel's edge is failing, which points at the hosting network rather than the dashboard. | httpnextjs.org | HTTP 200 | 1 min |
Official status feed Vercel's status page is unreachable. | httpwww.vercel-status.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Vercel's official status page.
Embed a live Vercel badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/vercel?utm_source=badge)HTML
<a href="https://www.upti.my/status/vercel?utm_source=badge"><img src="https://www.upti.my/status/vercel/badge.svg" alt="Vercel status"></a>Recent Vercel outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Vercel is up. Is your Vercel integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Vercel and fail quietly. Here is what teams that rely on Vercel monitor on their side.
Vercel cron jobs fail silently
Vercel does not retry a failed cron invocation and a skipped run produces no log. Put a heartbeat on each cron so a missed run alerts you.
Vercel cron monitoring guideYour API routes and ISR pages
A 200 on the homepage says nothing about serverless functions timing out. Probe your API routes with body validation.
HTTP monitoring with body validationVercel status: frequently asked questions
Sometimes. Build queues are a separate Vercel component from the edge network, so sites stay up while deployments stall. Check the official page for the Builds component and compare with our API probe.
Look at the per-region results above. If our probes fail from every region, Vercel has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Vercel may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Vercel" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Vercel: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Uptimy is not affiliated with Vercel. Vercel and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.