← Live dashboard

Service impact: Increased invoke error rates

Incident still open, awaiting updatemajorOfficial source confirmedFirst recorded update 30-10-2026 02:28

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.

Amazon Web Services live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

This incident was reported earlier. Its current impact is not confirmed by a recent official check.

Last official update:
30-10-2026 02:28

Are you affected by this incident?

One tap, no account. Your report helps others see if the problem is just them.

Choose your status. You can add a comment next.

No visitor reports in the last 24 hours yet.

Updates (1)

  1. 30-10-2026 02:28
    Service impact: 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.

    Amazon Web Services ↗

What to do right now

  • Check the provider's own status page. Open Amazon Web Services's official status page ↗
  • Don't restart everything. If the outage is upstream (cloud provider, CDN, auth provider), redeploying your own service usually won't help and may make recovery slower.
  • Communicate early. Even a one-line update to your users referencing the upstream incident reduces support load dramatically.
  • Watch this page. We post each new vendor update and source as it lands. Bookmark or share the URL with your team.

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.