Route 53 Issues

Final update

AWS has reported that the Route 53 issue is fully resolved. All back logged events have been processed and everything should be running as intended. For more information please see https://status.aws.amazon.com/

1. Resolved · May 11, 19:34 UTC
   AWS has reported that the Route 53 issue is fully resolved. All back logged events have been processed and everything should be running as intended. For more information please see https://status.aws.amazon.com/
2. Identified · May 11, 04:15 UTC
   AWS has processed the majority of the backlog of queued changes for Route 53 Public DNS. Private DNS changes are still experiencing propagation delays. Until AWS has fully recovered, some customers may still receive errors. For more information please see https://status.aws.amazon.com/
3. Identified · May 11, 00:28 UTC
   AWS is observing steady recovery, with the oldest changes propagating first. They are continuing to work through the backlog of queued changes. For more information please see https://status.aws.amazon.com/
4. Identified · May 10, 23:32 UTC
   AWS is reporting that some DNS changes are now propagating to the live DNS servers. They continue to work towards full recovery. For more information please see https://status.aws.amazon.com/
5. Identified · May 10, 22:58 UTC
   AWS is still experiencing Route 53 Issues which is impacting multiple AWS services. As of 2 pm PST, DNS updates are being accepted by the Route 53 API and Console, however an error is preventing the updates from being propagated from the Route53 API system to the live DNS servers. AWS has identified the root cause of this propagation error and are actively working towards a resolution. For more information on this issue please see https://status.aws.amazon.com/
6. Identified · May 10, 20:38 UTC
   Amazon Route 53 is currently experiencing increased propagation times in their DNS records. This can cause the Frame Platform to be delayed in processing requests. Amazon has identified the issue and they are working to resolve it. For more information please see https://status.aws.amazon.com/