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.
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.
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.
We’ll find your subscription and send you a link to login to manage your preferences.
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
We’ll use your email to save your preferences so you can update them later.
Subscribe to other services using the bell icon on the subscribe button on the status page.
You’ll no long receive any status updates from Synadia NGS, are you sure?
{{ error }}
We’ll no longer send you any status updates about Synadia NGS.