Vercel statusLiveFetched seconds agoSource: vercel-status.com
Is Vercel down?
Live status check · All systems operational
Live status pulled from vercel-status.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Vercel status
Vercel powers the frontends behind a huge chunk of the modern web. When the edge network or deployments stall, your marketing site, dashboard, and serverless functions can all stop responding at once.
Components and surfaces that can break
- Surface 01
Production deployments and preview URLs (*.vercel.app and custom domains).
- Surface 02
Serverless and Edge Functions, plus Vercel Cron Jobs scheduled in vercel.json.
- Surface 03
Vercel Postgres, Vercel KV, Vercel Blob, and the Dashboard API.
Recent Vercel incidents
Vercel maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Vercel is actually down
Confirm scope before you page anyone
Check the official status page for the specific component (Edge Network vs Deployments vs Serverless Functions). A regional Edge Network blip is very different from a global Deployments outage.
Failover to the previous deployment
Promote the last known-good deployment from the Vercel Dashboard or via the CLI. This rules out a bad deploy as the cause and gives you a stable rollback while Vercel investigates.
Move scheduled work off Vercel Cron temporarily
If a Vercel Cron run failed during the incident, do not redeploy just to retry it. Trigger the same handler URL once from an external HTTP cron (Crontap, curl from a laptop) so the job catches up and you can verify recovery.
Keep firing through the incident
Schedule your own Vercel health check with Crontap
Vercel Cron is tied to your deployment lifecycle: scheduled jobs pause when a deploy fails, and the minimum cadence on Hobby is one hour. Crontap fires the same handler URL from outside Vercel's plane, so your billing rollup or webhook retry still runs when the platform is degraded.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Vercel status: FAQ
- Where can I see the official Vercel status?
- Vercel publishes real-time component status at vercel-status.com with separate indicators for Deployments, Serverless Functions, Edge Network, and the Dashboard. The history page shows recent incidents with post-mortems.
- Why does my Vercel Cron job stop firing when there's an outage?
- Vercel Cron runs inside the same plane as your deployments. If Deployments or Serverless Functions degrade, scheduled invocations can be skipped or delayed. There is no native retry, so a missed cron means the work simply did not happen.
- How do I keep cron jobs running when Vercel is degraded?
- Move the trigger off Vercel. Crontap calls your handler URL from external infrastructure on the schedule you pick (down to one minute on Pro), retries 5xx responses, and stores the request body. If Vercel recovers mid-window, your job still runs.