Live / Vercel / Incident
Vercel: Delays in Drains, Observability, and Workflow in Washington (iad1)
Vercel · vercel.comMajor incidentResolved2026-10-10 01:37 UTC
Public — what happened
Summary
Vercel said that starting at 00:15 UTC on October 10, 2026, some customers in its Washington (iad1) region could see late delivery of log drains, slowed arrival of logs, metrics and traces, and Workflow runs stuck waiting to start. By 00:35 UTC the company reported it had put a fix in place, deliveries were flowing again, and the backlog was being worked through. At 01:12 UTC Vercel said the delayed drain data, observability data and build logs had all caught up, and it marked the incident resolved at 01:37. The company did not give a cause.
Affected
Drains, Logs, Observability, Queues, Workflow
Timeline
- Started — 2026-10-10 00:15 UTC
- Investigating — 2026-10-10 00:15 UTC
- Identified — 2026-10-10 00:35 UTC
- Monitoring — 2026-10-10 01:12 UTC
- Resolved — 2026-10-10 01:37 UTC · 1h 21m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Vercel against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Vercel: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Vercel report →
More from Vercel
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.