outages.live
Live
VercelIncident · 2026-09-17 07:11 UTC

Failures delivering Logs to Drains

ResolvedOfficial update

Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.

The latest update from Vercel.

State

Resolved

Started

45 d ago

2026-09-17 07:11 UTC

Lasted

1 min

until 2026-09-17 07:11 UTC

Worst impact

Notice

Timeline

1 update
07:1107:1107:1107:1107:12
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Vercel

Resolved2026-09-17 07:11 UTC

Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.

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

100% shorter than 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·Delays in Drains, Observability, and Workflow in Washington (iad1)

All services have recovered.

Resolvedresolved 22 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

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