Skip to main content
Vercel

Elevated errors across multiple services in IAD1 (Washington, D.C., USA)

Degraded Lasted 5h 21m · started · Vercel's page

Level
confirmed
Worst impact
Degraded
Components
Functions, Queues, Routing Middleware, Workflow
Regions
us

What to do

  • Check whether you use Vercel Functions, Queues, Routing Middleware, Workflow in us. 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 5h 21m it lasted.

    Anything that failed between 2026-05-08 01:18 UTC and 2026-05-08 06:39 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 7

  1. identified

    Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available.

    provider

  2. identified

    Traffic to the IAD1 region has been re-routed to nearby regions. Functions configured in IAD1 will be invoked in a different region if failover regions are configured, but if no other regions are configured, the function will still be invoked in IAD1.

    provider

  3. identified

    New messages to Vercel Workflows and Vercel Queues are being queued, but message processing is paused. Queued messages will be processed when service is restored.

    provider

  4. identified

    We are continuing to work on a fix for this issue.

    provider

  5. identified

    New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated.

    provider

  6. monitoring

    We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours.

    provider

  7. resolved

    We've deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in the IAD1 region.

    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-817b7a85eb

Is Vercel still down?

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

How long did it last?

5h 21m, from 2026-05-08 01:18 UTC to 2026-05-08 06:39 UTC, by the times Vercel posted.

What was affected?

Vercel named Functions, Queues, Routing Middleware, Workflow in us.

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.