Sign-in and sign-up failures on openrouter.ai
This incident is resolved. Between approximately 11:50 and 17:11 UTC, a portion of sign-in and sign-up attempts on openrouter.ai were incorrectly blocked with the message "This action was detected as suspicious and has been blocked." The cause was an infrastructure issue at our authentication provider that made one of its bot-protection checks fail, which in turn triggered a blocking rule. The provider disabled the rule at 17:11 UTC and sign-ins have succeeded normally since then. Existing sessions and API keys were not affected at any point, and there was no security breach or exposure of account data. If you were unable to sign in earlier, please try again. We apologize for the disruption.
The latest update from OpenRouter.
State
Resolved
Started
39 d ago
2026-09-23 17:11 UTC
Lasted
27 min
until 2026-09-23 17:38 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
8 min 31%
Identified
5 min 20%
Monitoring
13 min 48%
Updates
Times in UTCAs posted by OpenRouter
This incident is resolved. Between approximately 11:50 and 17:11 UTC, a portion of sign-in and sign-up attempts on openrouter.ai were incorrectly blocked with the message "This action was detected as suspicious and has been blocked." The cause was an infrastructure issue at our authentication provider that made one of its bot-protection checks fail, which in turn triggered a blocking rule. The provider disabled the rule at 17:11 UTC and sign-ins have succeeded normally since then. Existing sessions and API keys were not affected at any point, and there was no security breach or exposure of account data. If you were unable to sign in earlier, please try again. We apologize for the disruption.
The provider has disabled the affected rule and new sign-ins, we are monitoring the recovery.
We have identified the cause. An infrastructure issue at our authentication provider caused one of its bot-protection checks to fail, which incorrectly blocked a portion of sign-in and sign-up attempts.
We are investigating the issue. Since approximately 11:50 UTC, a portion of sign-in and sign-up attempts on openrouter.ai are failing with the message "This action was detected as suspicious and has been blocked." This affects all login methods. Workaround: Retrying the sign-in usually succeeds within a few attempts.
Affected components
1OpenRouter in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
13
Median duration
1 h 54 min
This incident
77% shorter than the median
Other OpenRouter incidents
All incidentsOpenRouter·Failing inference requests
The issue is now resolved.
OpenRouter·Video webhooks are not being called
Video webhooks are firing correctly again, and all backlogged video webhooks have been replayed.
OpenRouter·Activity logs, usage metrics reporting are experiencing delays
The issue is now resolved.
OpenRouter·Increased errors and latency on API requests in the US Pacific Northwest
The issue is now resolved. Cloudflare moved traffic to nearby locations. Other locations were not affected, and no change on our side caused it.
OpenRouter·Usage Reporting Delays in Web App
The issue is now resolved.
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.
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.
https://outages.cc/feed.xml?providers=openrouter/feed subscribe https://outages.cc/feed.xml?providers=openrouterFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane