Live

Activity logs, usage metrics reporting are experiencing delays

The issue is now resolved.

The latest update from OpenRouter.

State

Resolved

Started

17 d ago

2026-10-15 14:50 UTC

Lasted

37 h 53 min

until 2026-10-17 04:43 UTC

Worst impact

Degraded

Timeline

9 updates
Oct 15Oct 16Oct 16Oct 16Oct 17
DegradedUpdate postedDates in UTC

Investigating

7 h 42 min 20%

Identified

26 h 43 min 71%

Monitoring

3 h 28 min 9%

Updates

Times in UTC

As posted by OpenRouter

Resolved2026-10-17 04:43 UTC

The issue is now resolved.

Monitoring2026-10-17 01:15 UTC

Logs and usage metrics are now up to date in almost all cases. A small fraction are still delayed.

Identified2026-10-17 00:09 UTC

Logs latency continues to be elevated. Inference is not affected.

Identified2026-10-16 19:26 UTC

Logs latency has been significantly reduced, though is still elevated. Inference is not affected.

Identified2026-10-16 09:45 UTC

We have identified the issue and are deploying remediations. Inference is not affected.

Identified2026-10-16 05:44 UTC

We have identified the issue and are deploying remediations. Inference is not affected.

Identified2026-10-15 22:32 UTC

We have identified the issue and are deploying remediations. Inference is not affected.

Investigating2026-10-15 18:20 UTC

We are continuing to investigate the issue. Inference is not affected.

Investigating2026-10-15 14:50 UTC

We are investigating the issue.

Affected components

1
Web & Application Services

OpenRouter in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

13

Median duration

1 h 54 min

This incident

20× the median

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

37 h 53 min
median 1 h 54 min
90 days agoToday

Other OpenRouter incidents

All incidents

Follow OpenRouter

Your coding agent knows when OpenRouter is down, and tells you when a failure is theirs, not yours. You can also get OpenRouter 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 "openrouter" and tell me if OpenRouter 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=openrouter
Slack
/feed subscribe https://outages.cc/feed.xml?providers=openrouter

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane