Provider trouble · Sep 3, 2026

10 companies posted about trouble at AWS us-west-2 (Oregon)

The first posted at Sep 3, 21:12 UTC, the last 86 minutes later. 10 companies wrote about it in their own words.

2,093 companies in our directory rely on AWS.

Share on LinkedInShare on X

When they first posted

Companies by when their status page first showed it, 10 minutes a column. The most, 2, in Sep 3, 21:10–21:20 UTC.

Sep 3, 21:10 UTCSep 3, 22:30 UTC

What they said

Quoted from their status pages. Times are UTC.

  • Superblocks: “Clark editing and related cloud services are degraded due to an AWS outage”
  • Temporal: “Elevated Errors in us-west-2 Region”
  • Semgrep: “SMS Scans Degraded”
  • Materialize: “Degraded availability for Cloud customers in us-west-2 due to upstream AWS credential service disruption”
  • Archil: “Issues with disk operations in aws-us-west-2”
  • Jamf: “Jamf Pro Partial Outage”
  • Grafana: “Tempo and Mimir Read and Write Failures”
  • Sailpoint CIEM: “Identity Security Cloud is currently experiencing a service disruption.”
  • Trusona: “ATO Protect - Impact due to AWS Issues”
  • SurveyMonkey: “Possible service degradation due to AWS outage”

AWS's page: its status, and who relies on it

Find out when the next one touches your vendors

Start with your domain. We read its DNS for the services it uses, you add the rest of your vendors, and we email you when one of them posts trouble on its status page, or when trouble like this reaches them.

Start with your domain

More moments

We found this one later, by running the same rules over the status-page posts we had kept from before Oct 20, 2026. Status pages say what each company chose to post; a company not listed may have had the same trouble and said nothing.