Skip to main content
Vercel

Vercel Queues, and Vercel Workflow runs were delayed

Degraded Lasted 55m · started · Vercel's page

Level
confirmed
Worst impact
Degraded
Components
Queues, Workflow
Down Index
18of 100

What to do

  • Check whether you use Vercel Queues, Workflow. 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 55m it lasted.

    Anything that failed between 2026-05-09 04:45 UTC and 2026-05-09 05:40 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. monitoring

    Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is recovering, Vercel Queues backlogs are being processed, and Vercel Workflows are unblocked.

    provider

  2. resolved

    This incident 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-d9e3eea827

Is Vercel still down?

No, this incident was resolved 2026-05-09 05:40 UTC. For Vercel's live state, see https://down.guide/vercel.

How long did it last?

55m, from 2026-05-09 04:45 UTC to 2026-05-09 05:40 UTC, by the times Vercel posted.

What was affected?

Vercel named Queues, Workflow.

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.