Skip to main content
Vercel

Partial Observability Outage Affecting Compute Telemetry

Degraded Lasted 0m · started · Vercel's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on Vercel. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-04-25 00:54 UTC and 2026-04-22 23:00 UTC may need a replay.
  • Subscribe to Vercel's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vercel 1

  1. resolved

    We've identified an issue causing missing observability data for compute products between April 22, 2026 23:00 UTC and April 23, 2026 05:00 UTC affecting a subset of customers, resulting in missing or incomplete metrics in Observability dashboard during this period. All underlying compute services - including Vercel Functions, Workflows, and Cron Jobs - continued to operate normally. Logs were not affected and remain fully available.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-8485523497

Is Vercel still down?

No, this incident was resolved 2026-04-22 23:00 UTC. For Vercel's live state, see https://down.guide/vercel.

How long did it last?

0m, from 2026-04-25 00:54 UTC to 2026-04-22 23:00 UTC, by the times Vercel posted.

What caused it?

Vercel hasn't published a root cause. If it does, it shows here.

Where does this come from?

Vercel's official status page, https://www.vercel-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.