Sign-in and sign-up failures on openrouter.ai
OpenRouter · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- not normalized
- Provider record created
- 23 Sep 2026, 17:11:15 UTC
- Provider record updated
- 23 Sep 2026, 17:38:01 UTC
- Explicit provider start
- Not available
- Explicit provider end
- 23 Sep 2026, 17:38:01 UTC
Affected components reported by the provider
- Web & Application Services
2347916e-1f82-448c-b07d-8cfbbad57322
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
OpenRouter's seven reviewed gateway and web components, including its reported incidents and maintenance. It does not establish the status of upstream providers or individual models.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- 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.
Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC - monitoring
The provider has disabled the affected rule and new sign-ins, we are monitoring the recovery.
Seen in a saved revision at 29 Oct 2026, 08:08:16 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.
Seen in a saved revision at 29 Oct 2026, 08:08:16 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.
Seen in a saved revision at 29 Oct 2026, 08:08:16 UTC