Provider trouble · Nov 6, 2026

19 companies' status pages showed trouble at AWS us-west-2 (Oregon)

The first posted at Nov 6, 22:53 UTC, the last 88 minutes later. 7 companies wrote about it in their own words, and 12 more pages carried AWS's own status showing trouble.

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, 6, in Nov 6, 22:50–23:00 UTC.

Nov 6, 22:50 UTCNov 7, 00:20 UTC

What they said

Quoted from their status pages. Times are UTC.

  • Safe Software: “Issues with Instance actions in US West region (us-west-2)”
  • Dagster: “Elevated errors in launching serverless runs”
  • Databricks: “ES-2342108”
  • Atlan: “Delayed workflow execution for some tenants in the us-west-2 region”
  • Supabase: “Increased Errors with Project Lifecycle Operations in US-West-2”
  • Hevo Data: “Edge Pipeline Ingestion Delay- Due to AWS Outage”
  • Sigma Computing: “Degraded performance in AWS US-WEST-2 hosted organizations”

AWS's own status, shown on their pages

Parts on these companies' status pages that carry AWS's status, showing it in trouble. They repeat AWS rather than report in their own words.

  • Elastic: “AWS Oregon (us-west-2) / AWS EC2 Health: us-west-2: degraded”
  • Pulumi: “Third Party Services / AWS ec2-us-west-2: degraded”
  • Neo4j: “AWS (Amazon Web Services) / AWS ec2-us-west-2: degraded”
  • Superhuman: “Docs / Amazon Web Services: AWS ec2-us-west-2: degraded”
  • Sequel: “Third Party / AWS ec2-us-west-2: degraded”
  • Semgrep: “AWS / AWS ec2-us-west-2: degraded”
  • Hiver: “Infrastructure / AWS ec2-us-west-2: degraded”
  • Patlytics: “AWS ecs-us-west-2: degraded”
  • Cheqroom: “AWS ECS - US: degraded”
  • DigitalGenius: “AWS ecs-us-west-2: degraded”
  • Thepluginpeople: “Enterprise Mail Handler for Jira Cloud (JEMHC) / AWS ec2-us-west-2: degraded”
  • Atlassian Statuspage: “AWS rds-us-west-2: degraded”

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

Caught as it happened, by reading companies' status pages. Status pages say what each company chose to post; a company not listed may have had the same trouble and said nothing.