Increased build and deployment failures
DegradedThis incident has been resolved.
Vercel is up and running. Vercel hosts front-end apps and serverless functions, and builds Next.js.
Worked out from the incidents Vercel reported, so it is an estimate and not a measurement.
Last incident: “Increased build and deployment failures”, 4 days ago.
This incident has been resolved.
All services have recovered.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Vercel’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Vercel reported was “Increased build and deployment failures”, 4 days ago (2026-10-12 13:35 UTC). Its last full outage started 36 days ago.
Vercel reports 59 components on its status page, including Dashboard, Builds, ARN1 - Stockholm, Sweden, Drains, Builds. Each is checked again whenever this page refreshes.
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
Deploys run on the build pipeline ('Builds', 'Build & Deploy'), separate from the CDN serving live traffic — a build incident delays shipping but doesn't take existing deployments down.
Vercel lists many regions as separate components (iad1, fra1, BOM1…). Only functions executing in the named region are affected — your function config shows which regions you deploy to.
If the status above is operational but Vercel still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.