← Voltar ao feed

AWS US-EAST-1 outage on 15 Nov 2026 disrupts 11 services, including IAM Identity Center sign-in; no root cause or malicious activity reported

1 fonte(s) · 1 atualização(ões) · publicado 16/11/2026 04:37 · coletado há 24 minutos

Amazon Web Services confirmed an operational incident in its US-EAST-1 (Northern Virginia) region on November 15, 2026. It disrupted 11 services, including IAM Identity Center, AWS Sign Up, Kiro, Amazon Connect and Network Load Balancer connectivity. Problems began at 3:05 AM PST. The authentication issue was mitigated at 5:20 AM PST, and AWS posted its final resolution update at 6:53 AM PST. AWS has not disclosed a root cause, and its status updates do not attribute the event to malicious activity. This is an availability incident with no reported exploitation or data exposure. The article is based only on AWS status updates, and no web research was done.

Detalhes técnicos

  • Affected services: IAM Identity Center, IoT Device Management, NAT Gateway, Sign Up, Step Functions, CloudWatch, Connect, Elastic Load Balancing, OpenSearch Service, VPC Lattice and Kiro.
  • Impact: authentication errors when signing into the Management Console and dependent services. Kiro users who signed in through social sign-in were unaffected.
  • Residual impact: a subset of Network Load Balancers in a single cell of Availability Zone use1-az1, resolved at 6:21 AM PST.

Remediação

  • AWS advised customers to retry failed requests.
  • As an immediate workaround for the load balancer issue, AWS advised creating a new Network Load Balancer with targets across multiple Availability Zones.

Linha do tempo

  1. gbhackers.com ↗ · pub. 16/11/2026 04:37 · coletado 16/11 05:00 primeiro registro

    AWS US-EAST-1 outage on 15 Nov 2026 disrupts 11 services, including IAM Identity Center sign-in; no root cause or malicious activity reported

    ler a análise desta fonte

    Amazon Web Services confirmed an operational incident in its US-EAST-1 (Northern Virginia) region on November 15, 2026. It disrupted 11 services, including IAM Identity Center, AWS Sign Up, Kiro, Amazon Connect and Network Load Balancer connectivity. Problems began at 3:05 AM PST. The authentication issue was mitigated at 5:20 AM PST, and AWS posted its final resolution update at 6:53 AM PST. AWS has not disclosed a root cause, and its status updates do not attribute the event to malicious activity. This is an availability incident with no reported exploitation or data exposure. The article is based only on AWS status updates, and no web research was done.

    Technical Details

    • Affected services: IAM Identity Center, IoT Device Management, NAT Gateway, Sign Up, Step Functions, CloudWatch, Connect, Elastic Load Balancing, OpenSearch Service, VPC Lattice and Kiro.
    • Impact: authentication errors when signing into the Management Console and dependent services. Kiro users who signed in through social sign-in were unaffected.
    • Residual impact: a subset of Network Load Balancers in a single cell of Availability Zone use1-az1, resolved at 6:21 AM PST.

    Remediation

    • AWS advised customers to retry failed requests.
    • As an immediate workaround for the load balancer issue, AWS advised creating a new Network Load Balancer with targets across multiple Availability Zones.