Sign-in and sign-up failures on openrouter.ai

Timeline

1. 17:11 UTC OpenRouter status page · Reported Sign-in and sign-up failures on openrouter.ai
2. 17:11 UTC OpenRouter status page · Investigating 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.
3. 17:19 UTC OpenRouter status page · Identified 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.
4. 17:25 UTC OpenRouter status page · Monitoring The provider has disabled the affected rule and new sign-ins, we are monitoring the recovery.
5. 17:38 UTC OpenRouter status page · Resolved 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…