Overview

Amazon Web Services (AWS) has confirmed a significant outage originating in the US-EAST-1 (Northern Virginia) region. The incident was linked to an internal subsystem managing network load balancers, leading to temporary disruption across globally integrated platforms.

Although the fault was contained to a single AWS region, its impact was global – demonstrating how dependencies within shared cloud infrastructure can cascade beyond regional boundaries.

The Flow-On Effect

Many AWS-hosted services rely on control systems in US-EAST-1 for critical operations such as authentication, routing, and orchestration. When these systems went offline, applications hosted in other regions, including Australia, experienced performance degradation and delayed responses.

This event serves as a reminder that resilience in cloud environments depends on understanding the interconnected nature of global control planes. Even when core data remains hosted locally, reliance on centralised systems can cause widespread flow-on effects during regional outages.

Known Affected Services

  • Xero

  • Coinbase

  • Signal

  • Snapchat

  • Roblox

  • Prime Video

  • Duolingo

  • MyFitnessPal

  • Fortnite

  • Disney+

  • Zoom

  • Slack

  • Hinge

  • PlayStation Network

  • Epic Games

  • Peloton

  • Venmo

  • Netflix (partial)

Current Status

AWS has confirmed services are operational and stable. Some platforms may continue to experience residual latency or delayed log synchronisation while systems clear backlogs. AWS has also confirmed the issue was not the result of a cyber-attack.

ctrl:cyber analysts continue to monitor the situation and maintain oversight of global service stability.

Recommended Actions

For organisations leveraging AWS or AWS-hosted platforms:

  1. Review system performance and connectivity to confirm all services have restored full functionality.

  2. Validate log ingestion and alerting continuity to ensure no data gaps occurred during the outage window.

  3. Confirm redundancy for critical workloads, particularly those reliant on single-region or shared control services.

  4. Include multi-region outage scenarios within business continuity and disaster recovery planning.

Incidents like this highlight the importance of resilience beyond infrastructure. Readiness, verification, and proactive response are central to maintaining business continuity in complex, cloud-connected environments.

Contact the ctrl:cyber team for guidance on strengthening cloud resilience.

For ongoing updates, visit the AWS Health Dashboard.