Is Vercel down right now?
Live status for vercel.com isn't set up in this environment yet - check any URL manually instead.
Checking vercel.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
About Vercel outages
Written by the HostTracker monitoring team · updated from live probe data.
Vercel hosts the build pipeline and edge network behind a huge number of production websites and apps, and one of the more counterintuitive things about a Vercel incident is that it doesn't always mean sites go offline. Build pipeline problems and edge network problems are separate failure modes: a build outage blocks new deployments from going live while every site already deployed keeps serving traffic from the edge exactly as before, and the reverse - an edge incident - can degrade or drop already-live traffic while builds still complete normally in the background. Knowing which layer is affected changes what you'd actually expect to see as a visitor versus as a developer waiting on a deploy.
Common causes of Vercel downtime
Build pipeline incidents that block new deployments from completing, while every site already live on the edge keeps serving traffic unaffected
Edge network degradation in a specific region, which can slow or drop requests to live sites without any problem in the build system
Serverless function cold starts or timeouts under sudden traffic spikes, producing failed or slow requests on specific routes rather than a full site outage
Domain or DNS verification problems that block a custom domain from resolving correctly, separate from whether the underlying deployment itself is healthy
The dashboard and management console running on different infrastructure from production traffic, so a slow or unreachable dashboard doesn't necessarily mean deployed sites are affected
Not sure whether it's Vercel or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests vercel.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Vercel being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
Run the live check at the top of this page - it tests vercel.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Vercel is reachable for everyone or only failing for you.
Run the live check at the top of this page - it tests vercel.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Vercel is reachable for everyone or only failing for you.
It can be, and it's actually a distinctive pattern for Vercel. The build pipeline and the edge network serving already-deployed sites are separate systems, so a build-side incident blocks new deployments from going out while every site currently live keeps serving traffic normally from the edge. This is a real outage worth checking against a status result, just a narrower one than a full platform failure - your visitors aren't affected even though your own deploys are stuck.
Not necessarily. Serverless functions can experience cold-start delays or timeouts under a sudden spike in traffic to a specific route, which produces failures on that one function while the rest of the site, and the platform generally, keeps working fine. This is more often a scaling or configuration issue tied to your own function's traffic pattern than a Vercel-wide incident, though a widespread timeout pattern across many unrelated sites at once would point the other way.
It's often a domain or DNS verification issue rather than a platform outage. A custom domain needs to be correctly verified and pointed at Vercel's infrastructure, and a misconfigured record, an expired verification, or a DNS propagation delay can leave a domain unreachable while the underlying deployment itself is completely healthy and reachable at its default vercel.app address. Checking whether the site loads on its default domain is a quick way to isolate a DNS problem from an actual hosting incident.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.