outages.live
Live
VercelIncident · 2026-10-10 00:15 UTC

Delays in Drains, Observability, and Workflow in Washington (iad1)

ResolvedOfficial update

All services have recovered.

The latest update from Vercel.

State

Resolved

Started

22 d ago

2026-10-10 00:15 UTC

Lasted

1 h 21 min

until 2026-10-10 01:37 UTC

Worst impact

Partial outage

Timeline

4 updates
00:1500:3600:5601:1601:37
Partial outageUpdate postedTimes in UTC

Investigating

20 min 25%

Identified

37 min 45%

Monitoring

25 min 30%

Updates

Times in UTC

As posted by Vercel

Resolved2026-10-10 01:37 UTC

All services have recovered.

Monitoring2026-10-10 01:12 UTC

Delayed Drains deliveries, Observability data, and Build logs have been processed now. We are continuing to monitor and we will provide additional updates as they become available.

Identified2026-10-10 00:35 UTC

A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor.

Investigating2026-10-10 00:15 UTC

We've identified an issue where some customers may experience delayed drain delivery, delayed logs, metrics, and traces, and Workflow runs that remain pending in Washington (iad1). We are investigating this issue. We will provide additional updates as they become available.

Affected components

8
DrainsLogsObservabilityQueuesWorkflowObservability - DrainsObservability - LogsObservability - Observability

Vercel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

20

Days with an incident

17

Median duration

53 min

This incident

1.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 55 min
median 53 min
90 days agoToday

Other Vercel incidents

All incidents

Vercel·Delays in Logs and Observability data

The issue causing delays in Logs and Observability data has been resolved.

Resolvedresolved 9 d ago

Vercel·Increased build and deployment failures

This incident has been resolved.

Resolvedresolved 20 d ago

Vercel·Vercel Auth login failures for pages with Deployment Protection enabled

This incident has been resolved.

Resolvedresolved 26 d ago

Vercel·Elevated Sandbox error rates in Paris (cdg1)

This incident has been resolved.

Resolvedresolved 26 d ago

Vercel·Build failures and 500 errors for functions using Edge runtime

This incident has been resolved.

Resolvedresolved 34 d ago

Follow Vercel

Your coding agent knows when Vercel is down, and tells you when a failure is theirs, not yours. You can also get Vercel incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "vercel" and tell me if Vercel has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=vercel
Slack
/feed subscribe https://outages.cc/feed.xml?providers=vercel

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane