OpenRouter
OpenRouter is operational
Checked 2 min ago Operational
History
90 days agoToday
Incidents in 90 days
10
Days with an incident
13
Median duration
1 h 54 min
Longest incident
37 h 53 min
Components
7API - Gateway
Chat (/api/v1/chat/completions) Operational
90 days ago5 days with an incidentToday
Video (/api/v1/videos) Operational
90 days ago3 days with an incidentToday
Image (/api/v1/image) Operational
90 days agoNo incidentsToday
TTS (/api/v1/audio/speech) Operational
90 days ago2 days with an incidentToday
STT (/api/v1/audio/transcriptions) Operational
90 days ago2 days with an incidentToday
Embeddings (/api/v1/embeddings) Operational
90 days agoNo incidentsToday
Web & Application Services Operational
90 days ago7 days with an incidentToday
Maintenance
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=openrouterSlack
/feed subscribe https://outages.cc/feed.xml?providers=openrouterGo from tracking outages to fixing production issues with Polylane.
Try Polylane