已归档的官方INCIDENT

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

OpenRouter · 最近保存的提供方状态:resolved

当前服务报告 →

官方来源文字以原始语言显示。

这是历史证据。

最近保存的事件状态不是当前服务状态。来源列表可能不完整,事件从来源消失不确认恢复。请打开当前报告或官方来源查看较新证据。

已保存事件详情

提供方状态
resolved
提供方影响程度
not normalized
提供方记录创建时间
23 9月 2026, 17:11:15 UTC
提供方记录更新时间
23 9月 2026, 17:38:01 UTC
提供方明确报告的开始时间
不可用
提供方明确报告的结束时间
23 9月 2026, 17:38:01 UTC

提供方报告的受影响组件

  • Web & Application Services 2347916e-1f82-448c-b07d-8cfbbad57322

这些关联描述此事件的报告范围。不能确认当前组件可用性或已核实依赖关系。

记录创建时间未必是故障开始时间。未报告的时间保持不可用。我们不根据采集时间计算故障时长。

OpenRouter 已核对的七项网关与网页组件,以及官方报告的事件和维护;不代表上游提供方或单个模型的状态。

已保存修订中的提供方更新

最新优先。最多显示最近 20 份已保存内容修订中的 100 条不同更新。同一提供方时间的文字修订单独保留。

  1. 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.

    在 29 10月 2026, 08:08:16 UTC 的已保存修订中观察到
  2. monitoring

    The provider has disabled the affected rule and new sign-ins, we are monitoring the recovery.

    在 29 10月 2026, 08:08:16 UTC 的已保存修订中观察到
  3. 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.

    在 29 10月 2026, 08:08:16 UTC 的已保存修订中观察到
  4. 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.

    在 29 10月 2026, 08:08:16 UTC 的已保存修订中观察到

Cookie偏好设置

在您同意后,我们使用 Google Analytics 和 Umami 了解服务查询需求。这些工具会使用 Cookie 或浏览器存储。可选统计在您接受前保持关闭。

Cookie 与存储详情