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 的已保存修订中观察到