Skip to main content
Vercel

Delays in Logs and Observability data

Degraded Lasted 1h 2m · started · Vercel's page

Level
confirmed
Worst impact
Degraded
Components
Logs, Observability
Down Index
18of 100

What to do

  • Check whether you use Vercel Logs, Observability. 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 1h 2m it lasted.

    Anything that failed between 2026-10-23 16:31 UTC and 2026-10-23 17:32 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 2

  1. identified

    We have identified the issue causing delays in Logs and Observability data and are working on a fix. We will provide additional updates as they become available.

    provider

  2. resolved

    The issue causing delays in Logs and Observability data has been resolved.

    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-2ec317534e

Is Vercel still down?

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

How long did it last?

1h 2m, from 2026-10-23 16:31 UTC to 2026-10-23 17:32 UTC, by the times Vercel posted.

What was affected?

Vercel named Logs, Observability.

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.