outages.live
Live
OpenRouterIncident · 2026-10-14 04:12 UTC

Increased errors and latency on API requests in the US Pacific Northwest

ResolvedOfficial update

The issue is now resolved. Cloudflare moved traffic to nearby locations. Other locations were not affected, and no change on our side caused it.

The latest update from OpenRouter.

State

Resolved

Started

19 d ago

2026-10-14 04:12 UTC

Lasted

42 min

until 2026-10-14 04:54 UTC

Worst impact

Degraded

Timeline

2 updates
04:1204:2204:3304:4304:54
DegradedUpdate postedTimes in UTC

Investigating

42 min 100%

Updates

Times in UTC

As posted by OpenRouter

Resolved2026-10-14 04:54 UTC

The issue is now resolved. Cloudflare moved traffic to nearby locations. Other locations were not affected, and no change on our side caused it.

Investigating2026-10-14 04:12 UTC

We are investigating the issue. Requests that reached OpenRouter through Portland were slow or failed.

Affected components

1
Chat (/api/v1/chat/completions)

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

63% shorter than 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

OpenRouter·Failing inference requests

The issue is now resolved.

Resolvedresolved 6 d ago

OpenRouter·Video webhooks are not being called

Video webhooks are firing correctly again, and all backlogged video webhooks have been replayed.

Resolvedresolved 7 d ago

OpenRouter·Activity logs, usage metrics reporting are experiencing delays

The issue is now resolved.

Resolvedresolved 16 d ago

OpenRouter·Usage Reporting Delays in Web App

The issue is now resolved.

Resolvedresolved 24 d ago

OpenRouter·Meta Provider API calls are failing on OpenRouter with error 401.

The issue is now resolved. Root cause was identified as an authentication issue on the Meta Developer API Platform impacting all Managed Meta Accounts including OpenRouter's.

Resolvedresolved 38 d ago

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