Resolved

AWS have resolved their networking incident, which also affected NGS. After monitoring for a while, we have returned AWS clusters to the public DNS and are resolving our incident.

Recovering

This is an AWS issue and appears to have primarily affected us-east-2 (Ohio).

AWS report that things are recovering, but for now we will leave AWS out of service.

Investigating

The NGS components running in AWS have limited visibility to those running in Azure. We have withdrawn the AWS servers from DNS for connect.ngs.global and are continuing to investigate.

Began at:

Affected components
  • NGS
    • AWS
      • JetStream AWS
      • Connectivity AWS