Is OpenRouter down?
No, OpenRouter is not down.
OpenRouter’s status page reports no incidents, openrouter.ai responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.openrouter.ai
- Reachable6 of 6 regionsOpenRouter API · openrouter.ai
- Reports in the last hour0Normal
OpenRouter’s status page
From status.openrouter.ai. Read at
- Chat (/api/v1/chat/completions) API - GatewayOperational
- Video (/api/v1/videos) API - GatewayOperational
- Image (/api/v1/image) API - GatewayOperational
- TTS (/api/v1/audio/speech) API - GatewayOperational
- STT (/api/v1/audio/transcriptions) API - GatewayOperational
- Embeddings (/api/v1/embeddings) API - GatewayOperational
- Web & Application ServicesOperational
Planned maintenance, to : Scheduled site maintenance.
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 30 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (openrouter.ai)
By region
| Region | OpenRouter API openrouter.ai |
|---|---|
| N. Virginia us-east-1 | 401 · 30 ms |
| Oregon us-west-2 | 401 · 29 ms |
| Frankfurt eu-central-1 | 401 · 19 ms |
| Singapore ap-southeast-1 | 401 · 104 ms |
| Tokyo ap-northeast-1 | 401 · 19 ms |
| São Paulo sa-east-1 | 401 · 28 ms |
Two regions check OpenRouter every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked OpenRouter ourselves since Oct 28, 2026. Earlier days come from its status page.
13 days with problems in the last 90 days.
Recent incidents
Incidents: 5 in the last 30 days and 10 in the last 90, lasting a median of 1 h 53 min.
- Failing inference requestsPartial outage12 min
- Video webhooks are not being calledMajor outage2 h 9 min
- Activity logs, usage metrics reporting are experiencing delaysDegraded1 day
- Increased errors and latency on API requests in the US Pacific NorthwestDegraded42 min
- Usage Reporting Delays in Web AppDegraded6 h 38 min
- Meta Provider API calls are failing on OpenRouter with error 401.Degraded1 h 37 min
- Sign-in and sign-up failures on openrouter.aiDegraded26 min
- Degraded video generation APIDegraded2 h 45 min
- Web application degradedDegraded15 h 28 min
- Elevated 429s on Anthropic and OpenAIDegraded4 min
If OpenRouter isn’t working for you
OpenRouter is a single API that routes requests to hundreds of AI models from many providers, with one key and one bill.
Common OpenRouter errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
402: Your account or API key has insufficient credits. | Your OpenRouter balance or the key's credit limit is used up. | Your side | Add credits and retry the request. Source |
429: You are being rate limited | You exceeded a request or token rate limit. | Your side | Wait for the Retry-After interval, then retry. Source |
502: Your chosen model is down or we received an invalid response from it | The upstream provider for that model failed or returned a bad response. | An outage | Retry, or switch to another model or provider for now. Source |
503: There is no available model provider that meets your routing requirements | No provider for that model can take the request with your current routing settings. | Heavy load | Loosen provider restrictions or pick a different model. Source |
403: Budget limit exceeded | A key, workspace or guardrail budget is spent, so the request was rejected before reaching a provider. | Your side | Raise the budget or wait for the reset date shown in the message. Source |
Is it just you?
- A 502 or 503 usually means one upstream provider or model is failing; try a different model before assuming OpenRouter is down.
- Check your credits and per-key limits in the OpenRouter dashboard, since 402 and 403 budget errors look like outages.
- Compare with the model's own provider status (for example OpenAI or Anthropic) to see where the failure is.
- Check status.openrouter.ai and the reports on this page.
Alternatives to OpenRouter
Questions
That 502 error means the upstream provider serving that model failed or sent an invalid response. OpenRouter itself may be fine; try another model or provider.
OpenRouter depends on many upstream providers, so one provider's outage can break specific models while others keep working. Compare this page with the provider's own status page.
Sources: openrouter.ai, status.openrouter.ai
Get alerted when OpenRouter breaks your app.
If your product or your team depends on OpenRouter, its outage is your outage, and your users will blame you, not OpenRouter. Point a Site Qwality monitor at the OpenRouter endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.