Provider trouble · Nov 15, 2026

14 companies' status pages showed trouble at AWS us-east-1 (N. Virginia)

OverAWS marked it resolved at .

First company post
, Check Point
AWS's own post
, 3 minutes later
Wrote in their own words
1 company + 13 pages repeating AWS's status
Rely on AWS
2,100 companies in our directory

AWS's last update

Posted

“We are seeing significant signs of recovery and are continuing to monitor for full recovery.”

Read it on AWS's status page

Is a tool you use affected?

Add the tools your team uses. We check whether each one posted about this on its status page, or relies on AWS by its own subprocessor list.

What companies named

Parts of AWS named in their posts. A company can name more than one.

  • Load balancers8

6 companies named AWS without a part.

What they said

Quoted from their status pages, newest first, at the time each one appeared. Pages only repeating AWS's own status are marked.

  • Check Point: “Playblocks Automation Failures in the US Region”
  • : TonicDM: “Amazon Web Services (platform host) / AWS elasticsearch-us-east-1: degraded” · repeats AWS's status
  • Honeybadger: “AWS elb-us-east-1: degraded” · repeats AWS's status
  • Tiny: “AWS elb-us-east-1: degraded” · repeats AWS's status
  • Disco: “AWS elb-us-east-1: degraded” · repeats AWS's status
  • Complif: “Vendors / [AWS] Load balancer: degraded” · repeats AWS's status
  • Tavus: “AWS elb-us-east-1: degraded” · repeats AWS's status
  • Extole: “AWS elb-us-east-1: degraded” · repeats AWS's status
Show all 14
  • Clar: “AWS / AWS ELB: degraded” · repeats AWS's status
  • Apify: “External services / AWS ELB: degraded” · repeats AWS's status
  • Spline: “AWS Infrastructure / AWS cloudwatch-us-east-1: degraded” · repeats AWS's status
  • Ambassador: “AWS cloudwatch-us-east-1: degraded” · repeats AWS's status
  • ModernLoop: “Cloud Hosting / AWS CloudWatch: degraded” · repeats AWS's status
  • HackerRank: “Cloud Services / AWS: major outage” · repeats AWS's status

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.