Amazon API Gateway · Oregon: [RESOLVED] Increased invoke error rates
AWS · 最近儲存的提供方狀態：Provider code 0
官方來源文字以原始語言顯示。
最近儲存的事件狀態不是當前服務狀態。來源列表可能不完整，事件從來源消失不確認恢復。請開啟當前報告或官方來源檢視較新證據。
已儲存事件詳情
- 提供方狀態
- Provider code 0
- 提供方影響程度
- not normalized
- 提供方記錄建立時間
- 30 10月 2026, 01:28:38 UTC
- 提供方記錄更新時間
- 30 10月 2026, 01:28:38 UTC
- 提供方明確報告的開始時間
- 不可用
- 提供方明確報告的結束時間
- 不可用
提供方報告的受影響元件
此已儲存修訂未提供元件關聯，或尚未恢復這些關聯。
這些關聯描述此事件的報告範圍。不能確認當前元件可用性或已核實依賴關係。
記錄建立時間未必是故障開始時間。未報告的時間保持不可用。我們不根據收集時間計算故障時長。
AWS Health 儀表盤源返回的公開事件記錄，包含已報告的服務、地區和更新。保留提供方的數字狀態程式碼，不解釋嚴重程度或解決狀態，因此彙總仍為未知。不是賬戶健康、完整元件矩陣或獨立地區測試；源為空不能確認可用性。
已儲存修訂中的提供方更新
最新優先。最多顯示最近 20 份已儲存內容修訂中的 100 條不同更新。同一提供方時間的文字修訂單獨保留。
- Provider code 1
Reported service: Amazon API Gateway (apigateway-us-west-2). Reported region: Oregon. Increased invoke error rates Between 7:27 AM and 8:47 AM PDT, and between 10:47 AM and 4:15 PM PDT, we experienced intermittent invoke error rates and latencies for HTTP APIs in the US-WEST-2 Region. During this time, customers would have observed increased latency or errors when invoking HTTP APIs, with elevated errors occurring between 3:12 PM and 3:45 PM PDT. This represented the period of highest customer impact with the majority of affected customers experiencing errors or increased latencies during this window. Majority of retry attempts for affected requests were succeeding. We communicated to impacted customers via the Your Account view of the AWS Health Dashboard during both impact windows. We identified the root cause to be an issue with an internal subsystem and by 3:45 PM we applied the necessary mitigation actions to remediate the issue. By 4:00 PM, we saw initial signs of recovery and continued to monitor for sustained recovery. We confirmed full recovery at 4:15 PM. We recommend that customers retry failed requests. The issue is resolved and the service is operating normally.
在 30 10月 2026, 01:32:56 UTC 的已儲存修訂中觀察到