Amazon API Gateway · Oregon: [RESOLVED] Increased invoke error rates
AWS · Last saved provider status: Provider code 0
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
- Provider code 0
- Provider impact
- not normalized
- Provider record created
- 30 Oct 2026, 01:28:38 UTC
- Provider record updated
- 30 Oct 2026, 01:28:38 UTC
- Explicit provider start
- Not available
- Explicit provider end
- Not available
Affected components reported by the provider
Component associations were not provided or have not been recovered for this saved revision.
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.
Public event records returned by the AWS Health dashboard feed, with reported services, regions and updates. Numeric provider status codes are retained without interpreting severity or resolution, so the aggregate remains unknown. This is not account health, a complete component matrix or independent regional testing; an empty feed does not confirm availability.
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.
- 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.
Seen in a saved revision at 30 Oct 2026, 01:32:56 UTC