← Back to Vercel History
minor✓ Resolved

Elevated errors across multiple services in IAD1

VercelFri, May 8, 2026, 01:18 AM
Status
resolved
Duration
5h 21m
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedFri, May 8, 2026, 06:40 AM
This incident has been resolved.
monitoringFri, May 8, 2026, 04:54 AM
We implemented a fix and are monitoring the results. Backlogs for Workflows and Queues will be processed within the next few hours.
identifiedFri, May 8, 2026, 02:33 AM
New workflow runs and queue messages are being processed now. Processing the backlog of existing workflow runs and queued messages is still being investigated.
identifiedFri, May 8, 2026, 02:18 AM
We are continuing to work on a fix for this issue.
identifiedFri, May 8, 2026, 02:13 AM
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.
identifiedFri, May 8, 2026, 01:47 AM
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.
identifiedFri, May 8, 2026, 01:18 AM
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.

📊 TECHNICAL DETAILS

Internal ID
39a2ae3b-68bd-48ca-a903-663373cf792b
External ID
c5zv0h9jh4g4
🕐 Started
Fri, May 8, 2026, 01:18 AM
🔄 Last Updated
Fri, May 8, 2026, 06:40 AM
✓ Resolved
Fri, May 8, 2026, 06:40 AM
MINOR
Impact Level
5h 21m
Total Duration
6
Status Updates
Affected Components
Edge FunctionsEdge MiddlewareServerless FunctionsQueuesWorkflow
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed