Vercel Status: How to Check If Vercel Is Down Right Now (2026)
Updated June 2026 · 7 min read · By API Status Check
Quick Answer: Check Vercel Status Now
Vercel powers millions of frontend deployments for startups, enterprises, and individual developers — including the official Next.js hosting platform. When Vercel goes down, it can take live websites offline, block deployments, and break serverless functions. This guide explains how to diagnose Vercel issues quickly and interpret what you see on their status page.
Understanding Vercel's Status Page (vercel-status.com)
Vercel operates vercel-status.com — its official status page. Each component represents a different layer of the platform, which is critical to understand since deployment failures and live site issues are completely separate.
Edge Network
Serves live traffic from Vercel's global CDN. If degraded, your deployed sites are slow or unreachable for end users.
Deployments
The build and deployment pipeline. Build failures here don't affect live traffic from previously successful deployments.
Dashboard
The vercel.com web interface. If down, you can't manage projects or view logs, but your sites may still work.
Serverless Functions
API routes and Edge Functions. Can be degraded independently from the edge network serving static files.
Vercel KV
Redis-compatible key-value store. Outages here only affect apps that use Vercel KV — not all deployments.
Vercel Postgres
Managed PostgreSQL. Outages affect apps using Vercel Postgres but not the edge network or other services.
Vercel Blob
Object storage for files. Can be down independently of other components.
Analytics
Vercel Speed Insights and Analytics. Outages here affect data collection but not site performance.
What Vercel Status Colors Mean
Monitor your Vercel deployments automatically
Better Stack monitors your Vercel-hosted apps and alerts you the moment they go down — independently of Vercel's own status page. Get Slack, PagerDuty, or SMS alerts. Free plan available.
Try Better Stack Free →5 Ways to Check If Vercel Is Down
vercel-status.com (Official)
Vercel's official status page. Updated during incidents by Vercel's team. Can lag behind real outages by 10–20 minutes.
Check vercel-status.com →API Status Check (Independent)
Independent third-party monitoring that pings Vercel endpoints continuously and reports separately from Vercel's own status page.
Check independent Vercel status →Check your build logs
For deployment failures, the first stop is your Vercel dashboard build logs. Most failures are code or config errors — not Vercel outages. Error messages like 'FUNCTION_INVOCATION_FAILED' with no code changes suggest a platform issue.
Vercel Dashboard →X / Twitter (@vercel)
Search 'Vercel down' on X or check @vercel. Developers report Vercel issues quickly on X, often faster than official status updates.
Search X for 'vercel down' →Test a deployment manually
Run `vercel --prod` from the CLI on a minimal project. If it hangs or returns an internal error with no code issue, the build system may be down.
vercel --prod --debug 2>&1 | grep -E "error|Error|failed|Failed"Common Vercel Error Messages During Outages
"FUNCTION_INVOCATION_FAILED"Serverless function crashed at runtime. During outages, this appears without any code changes. Check if the error is new or existing — new means Vercel issue."DEPLOYMENT_BLOCKED"Deployment was blocked by Vercel's system, often during incidents affecting the build infrastructure. Retry after checking vercel-status.com."502 Bad Gateway"Vercel's edge network couldn't reach your serverless function. If it's happening site-wide without code changes, check Edge Network and Functions components."Build failed with exit code 1"Usually a code error, not an outage. Check the specific build log error. If it's a generic 'internal error' with no code changes, suspect a build system issue."Error: Command failed: npm run build"Build command failed. 99% code or dependency issue. Only suspect Vercel if builds were working 10 minutes ago with no code changes."EDGE_FUNCTION_INVOCATION_TIMEOUT"Edge Function exceeded the 30-second timeout (or Starter plan 10s limit). During outages, normally fast functions can time out due to network delays."Request Entity Too Large"Your response payload exceeds Vercel's 4.5MB response limit — not an outage. Reduce response size or use streaming.Vercel Outage History: What the Data Shows
Vercel's edge network (serving live traffic) is extremely reliable — most reported incidents are deployment slowdowns, not live site outages. Build infrastructure incidents are more common, particularly during peak deployment hours (9–11 AM UTC). If you're hosting with Vercel, the bigger risk is usually deployment failures from code issues, not Vercel platform outages. Use our Vercel monitoring to track real-time availability independently.
What to Do When Vercel Is Down
If Deployments Are Failing
- Check build logs for code errors first (not an outage)
- Confirm on vercel-status.com (Deployments component)
- Your live site continues serving existing deployment
- Queue your deployment — Vercel will retry when service recovers
- Follow @vercel on X for incident timeline
If Live Sites Are Down (Edge Network)
- This is rarer — check vercel-status.com Edge Network immediately
- If confirmed: notify your users/stakeholders
- Check if a previous deployment can be rolled back
- For critical apps: consider a Cloudflare Pages or Netlify failover
- Open a Vercel support ticket if on a paid plan
Frequently Asked Questions
Where is the official Vercel status page?
Vercel's official status page is vercel-status.com. It shows real-time status for the edge network, deployments, dashboard, serverless functions, Vercel KV, Vercel Postgres, and Vercel Blob. You can subscribe to email notifications directly on the page.
My Vercel deployment is failing — is it Vercel's fault or my code?
Most deployment failures are code or configuration issues — missing environment variables, build errors, invalid package.json, or TypeScript errors. Check your build log first. If you see a specific code error, it's yours to fix. If you see a generic internal error with no code changes, or if many developers report failures simultaneously, check vercel-status.com.
Is Vercel deployment down different from the edge network being down?
Yes — and this distinction matters. Build/deployment failures mean new code can't be deployed, but your existing live site continues serving traffic from the last successful deployment. Edge network failures mean your live sites are unreachable. Edge incidents are rarer but more impactful. Check the specific component on vercel-status.com.
Does a Vercel outage affect Netlify or Cloudflare Pages?
No — Vercel, Netlify, and Cloudflare Pages are completely separate platforms. A Vercel outage doesn't affect other hosting providers. If you have a critical app, maintaining a backup deployment on Cloudflare Pages or Netlify (pointing to the same repo) is a common resilience strategy.
How do I get alerts when Vercel goes down?
Subscribe to email notifications at vercel-status.com, follow @vercel on X for incident updates, or use Better Stack / API Status Check Alert Pro for automated monitoring of your Vercel-hosted sites with custom alert thresholds and Slack/PagerDuty/SMS notifications.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Vercel goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Vercel + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial