已歸檔的官方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 與儲存詳情