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

What to do

• Check whether your product depends on OpenRouter. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-09-23 17:38 UTC and 2026-09-23 17:38 UTC may need a replay.

• Subscribe to OpenRouter's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=openrouter works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

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.

Updates from OpenRouter 1

1. resolvedSep 23, 2026, 5:38 PM UTC

   Sep 23, 17:38 UTC 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 account data. If you were unable to sign in earlier, please try again. We apologize for the disruption. Sep 23, 17:25 UTC Monitoring - The provider has disabled the affected rule and new sign-ins, we are monitoring the recovery. Sep 23, 17:19 UTC 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. Sep 23, 17:11 UTC 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.