Resolved -
We have received confirmation that this issue has been resolved by taking a host offline in the AWS network that was causing the DNS resolution issues. We also continue to confirm with customers that they are not seeing any residual impacts of this issue.
This issue is now resolved.
Apr 3, 16:40 UTC
Update -
We are getting confirmation from customers that they have now seen the issue resolve after a host causing DNS resolution issues was taken offline. We continue to work to ensure the issue is fully resolved and monitor the situation.
Apr 3, 12:07 UTC
Monitoring -
A host has been taken offline that was suspected to be causing the DNS resolution issues. The issue continues to be looked into to ensure it is fully mitigated.
A reproduction of the issue is no longer exhibiting DNS resolution issues. We will be checking in with customers to ensure their intermittent connection issues are fully resolved.
Apr 3, 03:25 UTC
Update -
A fix to the issue with the resolver host within the AWS network continues to be worked on. We will provide the next update before 2025/04/02 14UTC.
Apr 3, 02:45 UTC
Update -
A resolver host within the AWS network has been identified as the root cause of the failed DNS resolutions. A fix to the issue is being worked on.
Apr 2, 22:47 UTC
Update -
DNS Resolution issues at Cloud Provider level resulting in intermittent resolution issues of the Atlas Resources to their Hostname/IP. High Severity case has been filed and additional updates to follow.
Apr 2, 21:55 UTC
Identified -
We have successfully reproduced the failed DNS resolution from an ec2 instance in Frankfurt (eu-central-1). We are in communication with AWS on the issue.
Apr 2, 21:09 UTC
Update -
Our investigation has found an issue with resolving DNS records from certain geographies. We are continuing to investigate to identify which geographies are impacted
Apr 2, 20:30 UTC
Investigating -
We are investigating intermittent connection issues for some clusters in the AWS Frankfurt (eu-central-1) region.
Apr 2, 17:02 UTC