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

As listed on Vercel’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Vercel status & history page.

Related: Vercel status & history. SquidGrid is not affiliated with Vercel.