Delays delivering log drains
This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.
The latest update from Vercel.
State
Resolved
Started
87 d ago
2026-08-06 16:37 UTC
Lasted
1 h 53 min
until 2026-08-06 18:29 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
29 min 26%
Identified
1 h 14 min 65%
Monitoring
10 min 9%
Updates
Times in UTCAs posted by Vercel
This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.
Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed.
We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available.
We've identified the issue and are working on a fix. We will provide updates as they become available.
We continue to investigate this issue and will provide updates as they become available.
We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.
Affected components
2Vercel in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
17
Median duration
53 min
This incident
2.1× the median
Other Vercel incidents
All incidentsVercel·Delays in Logs and Observability data
The issue causing delays in Logs and Observability data has been resolved.
Vercel·Increased build and deployment failures
This incident has been resolved.
Vercel·Delays in Drains, Observability, and Workflow in Washington (iad1)
All services have recovered.
Vercel·Vercel Auth login failures for pages with Deployment Protection enabled
This incident has been resolved.
Vercel·Elevated Sandbox error rates in Paris (cdg1)
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=vercel/feed subscribe https://outages.cc/feed.xml?providers=vercelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane