Is Vercel down?

This page asks Vercel’s own status feed, straight from your browser, when you open it and once a minute while it stays open. It shows what Vercel reports and never fills in a gap with a guess.

What this checks

Builds, deploys, and the copies of your site kept near your visitors. In short, whether your ship button works. On this page that means the parts on Vercel’s status page whose names include “build”, “deploy” or “cdn”.

• The list appears after the live check.

Open incidents

Recent incidents

If it is down

• A deploy that fails while Vercel reports a problem with builds or deploys is not proof your code is broken. When the incident clears, redeploy the same commit. If it fails again with the same error, it is yours: see Command “npm run build” exited with 1.
• If Vercel reports no problems and it still fails, the cause is more likely on your side: your key, your code or your network. The error explainers cover the common messages.
• A status page shows what the company has reported. A problem that has started but has not been reported yet will not show here, so if the answer above is no and something still fails for everyone you know, check again in a few minutes.
• Do not rewrite working code to chase an outage. Commit what you have now, so that when the service is back you can tell whether anything you changed in the meantime broke something.
• Down? Save your place before you switch tools: Cold Handoff writes the note you paste into the next session, so it picks up where this one stopped instead of starting over.

Where this comes from

Your browser reads www.vercel-status.com/api/v2/summary.json and, once per visit, www.vercel-status.com/api/v2/incidents.json for the history. The request goes straight to Vercel, without cookies, and does not pass through this site. The same feed drives the Vercel row on the Vibe Board, which shows all 7 services at once.

Other services

• Claude
• OpenAI
• Gemini
• Cursor
• GitHub Copilot
• Supabase
• All status pages