Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Vercel down?

Right now

No. Vercel is operational.

No incidents reported.

Read from www.vercel-status.com · every 60s

For agents

proceed

Proceed.

GET upbutler.com/status/vercel/status.agent.json

MCP: upstream_status {"service":"vercel"}

Deployments, Functions, Edge Network and builds. A build incident blocks shipping a fix even while production serves traffic.

What Vercel reports

Operational

Taken as is from Vercel's own status page API. Incident titles and component names below are theirs.

Open www.vercel-status.com

UpButler's independent probe

API edge is answeringHTTP 403 · 543 ms

One request without credentials to api.vercel.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.

Checked · up since 2026-10-10 01:24 UTC

Vercel components

59 operational

Dashboard

  • DashboardOperational
  • Support CenterOperational
  • Support ChatOperational

Build & Deploy

  • BuildsOperational
  • npm RegistryOperational

CDN

  • ARN1 - Stockholm, SwedenOperational
  • BOM1 - Mumbai, IndiaOperational
  • CDG1 - Paris, France, EuropeOperational
  • CLE1 - Cleveland, East USOperational
  • CPT1 - Cape Town, South AfricaOperational
  • DUB1 - Dublin, IrelandOperational
  • DXB1 - Dubai, UAEOperational
  • FRA1 - Frankfurt, Germany, EuropeOperational
  • GRU1 - São Paulo, BrazilOperational
  • HKG1 - Hong KongOperational
  • HND1 - Tokyo, JapanOperational
  • IAD1 - Washington DC, USAOperational
  • ICN1 - Seoul, South KoreaOperational
  • KIX1 - Osaka, JapanOperational
  • LHR1 - London, UKOperational
  • PDX1 - Portland, West USOperational
  • SFO1 - San Francisco, CA, USAOperational
  • SIN1 - SingaporeOperational
  • SYD1 - Sydney, AustraliaOperational
  • YUL1 - Montréal, CanadaOperational

Observability

  • DrainsOperational
  • LogsOperational
  • ObservabilityOperational
  • Speed InsightsOperational
  • Web AnalyticsOperational

Secure Compute

  • BuildsOperational

Storage

  • BlobOperational
  • Global ConfigOperational

v0

  • Output GenerationOperational
  • DashboardOperational
  • AI GatewayOperational
  • APIOperational
  • CommunityOperational
  • Cron JobsOperational
  • Data CacheOperational
  • DNSOperational
  • Domain RegistrationOperational
  • FirewallOperational
  • FunctionsOperational
  • Image OptimizationOperational
  • MarketplaceOperational
  • QueuesOperational
  • Remote CachingOperational
  • Routing MiddlewareOperational
  • SAML Single Sign-OnOperational
  • SandboxOperational
  • TLS CertificatesOperational
  • WorkflowOperational
  • Container RegistryOperational
  • Key Management ServiceOperational
  • ConnectOperational

CI/CD

  • Deploy HooksOperational
  • Git IntegrationsOperational
  • Integration WebhooksOperational

Vercel incidents, last 90 days

4 finished incidents seen since UpButler started tracking on 2026-10-10, 2 of them rated major or critical by Vercel. A typical one lasted 27 min; the longest 1 h 21 min.

Started (UTC)IncidentImpactLasted
Delays in Drains, Observability, and Workflow in Washington (iad1)major1 h 21 min
Vercel Auth login failures for pages with Deployment Protection enabledmajor16 min
Elevated Sandbox error rates in Paris (cdg1)minor25 min
Build failures and 500 errors for functions using Edge runtimeminor27 min

Tell your outage from Vercel's

Declare that your project depends on Vercel. When one of your monitors fails while Vercel has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - vercel
Ask before you retry
curl -s https://upbutler.com/status/vercel/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "vercel",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": {
    "state": "up",
    "statusCode": 403
  }
}

Questions

Is Vercel down right now?
No. As of 2026-10-10 05:09 UTC, Vercel is operational. This page reads the status again every 60 seconds.
Where does this status come from?
From Vercel's own status page API at https://www.vercel-status.com. UpButler reads it once for everyone (not once per visitor) every 60 seconds with conditional requests, and shows it unchanged: incident titles and component names are Vercel's words.
What does UpButler's own Vercel check prove?
Every two minutes UpButler sends one request without credentials to the Vercel API edge (api.vercel.com). Any answer from the edge, usually HTTP 403, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Vercel reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
How can my agent or app check Vercel status?
Fetch https://upbutler.com/status/vercel/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"vercel"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Vercel's?
Add "vercel" to the dependencies of your UpButler workspace. When one of your monitors fails while Vercel has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in hosting and compute

UpButler is not affiliated with Vercel. Status and incident text belong to Vercel and are read from their public status source; the probe result is UpButler's own measurement.