Availability Zone (use1-az4) Impacted

Identified
Update

AWS is still continuing to work through the thermal event in Availability Zone use1-az4 within the US-EAST-1 Region. There is currently no ETA from AWS for full recovery of services.

Current VMC on AWS impact includes:

  1. No new host provisioning.
  2. No new SDDC deployments.
  3. Failure of auto-remediation for host failures.
Update

Operational issue - Amazon Elastic Compute Cloud (N. Virginia)

The AWS team are continuing to address a thermal event causing elevated temperatures, error rates, and latencies in Availability Zone use1-az4 within the US-EAST-1 Region. While cooling system restoration is progressing slower than anticipated, AWS has shifted traffic away from the impacted zone for most services.

The current impact includes:

  1. No new host provisioning
  2. No new SDDC deployments
  3. Failure of auto-remediation for host failures
Identified

Operational issue - Amazon Elastic Compute Cloud (N. Virginia)

The AWS team are continuing to address a thermal event causing elevated temperatures, error rates, and latencies in Availability Zone use1-az4 within the US-EAST-1 Region. While cooling system restoration is progressing slower than anticipated, AWS has shifted traffic away from the impacted zone for most services.

The current impact includes:

  1. No new host provisioning
  2. No new SDDC deployments
  3. Failure of auto-remediation for host failures

Next update 10:30pm PDT / 5:30am UTC

Investigating

AWS is investigating instance impairments in a single Availability Zone (use1-az4) in the US-EAST-1 Region. Other Availability Zones are not affected by the event and AWS are working to resolve the issue.

Began at:

Affected components
  • VMware Cloud Services
    • VMware Cloud on AWS / AWS SDDC
      • VMware Cloud on AWS
        • VMware Cloud on AWS SDDC
          • US East (N. Virginia)