Live

Scheduled site maintenance

MaintenanceOfficial update

We are conducting site maintenance. Certain dashboard functionality (eg adding credits, creating or modifying API keys, or updating user settings) is not available. Inference is not affected.

The latest update from OpenRouter.

State

In progress

Started

60 min ago

2026-11-01 21:00 UTC

Ongoing for

1 h

Worst impact

Maintenance

Timeline

2 updates
21:0021:1421:2921:4421:59
MaintenanceUpdate postedTimes in UTC

Scheduled

1 min 0%

In progress

1 h 100%

Updates

Times in UTC

As posted by OpenRouter

In progress2026-11-01 21:00 UTC

We are conducting site maintenance. Certain dashboard functionality (eg adding credits, creating or modifying API keys, or updating user settings) is not available. Inference is not affected.

Scheduled2026-11-01 17:39 UTC

We will be conducting site maintenance. Certain dashboard functionality (eg adding credits, creating or modifying API keys, or updating user settings) will not available during this period. Inference is not affected.

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

Not comparable

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