Live

Delays in observability data

Partial outageOfficial update
0

Vercel reports a partial outage in AI Gateway, Observability, Queues, and Workflow. Observability and billing data is delayed, and the Workflows dashboard can show a run as pending after it started or finished. Vercel implemented a fix and is monitoring the recovery.

State

Monitoring

Started

Ongoing for

2 h 12 min

Worst impact

Partial outage

Timeline

5 updates
20:4421:1721:5022:2322:57
Partial outageUpdate postedTimes in UTC

Investigating

16 min 12%

Identified

33 min 25%

Monitoring

1 h 24 min 63%

Updates

Times in UTC

As posted by Vercel

Monitoring

A fix has been implemented, and recovery is in process. We are monitoring the results and will provide additional updates as we have them.

Identified

The issue has been identified and a fix is being implemented.

Investigating

We are investigating an issue where observability and billing data is delayed. Run status on the Workflows dashboard on Vercel may be reported as “pending” even though the run may have already started or finished. Observability data on the AI Gateway dashboard is delayed and users may see low traffic. We will provide additional updates as we have them.

Identified

The issue has been identified and a fix is being implemented.

Investigating

We are investigating an issue where observability and billing data is delayed. Run status on the Workflows dashboard on Vercel may be reported as “pending” even though the run may have already started or finished. Observability data on the AI Gateway dashboard is delayed and users may see low traffic. We will provide additional updates as we have them.

Affected components

5
AI GatewayObservabilityQueuesWorkflowObservability - Observability

Vercel in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

18

Days with an incident

16

Median duration

50 min

This incident

2.7× the median

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

6 h 36 min
median 50 min
90 days agoToday

Other Vercel incidents

All incidents

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.live/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.live/feed.xml?providers=vercel
Slack
/feed subscribe https://outages.live/feed.xml?providers=vercel

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane