Is Vercel down right now?

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.

No - as of the most recent check, vercel.com is responding normally to HostTracker's monitoring network, and has been up for 43d 23h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is usually local - your network, DNS cache, or a regional route - or a problem behind the sign-in, which a check from outside cannot see. The live probe results above show which locations, if any, are affected.

No - as of the most recent check, vercel.com is responding normally to HostTracker's monitoring network, and has been up for 43d 23h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is usually local - your network, DNS cache, or a regional route - or a problem behind the sign-in, which a check from outside cannot see. The live probe results above show which locations, if any, are affected.

No - as of the most recent check, vercel.com is responding normally to HostTracker's monitoring network, and has been up for 43d 23h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is usually local - your network, DNS cache, or a regional route - or a problem behind the sign-in, which a check from outside cannot see. The live probe results above show which locations, if any, are affected.

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.