История сбоев Ultradns

April 15, 2026 8:04AM UTC Investigating - We are experiencing a DDoS against nameservers in parts of Asia and Australia. Customers may see timeouts in these regions. Our teams are actively engaged in mitigating efforts. Further updates will be provided as progress continues. April 15, 2026 8:28AM UTC Identified - Our teams are working on mitigating the attack on our nameservers in parts of Asia and Australia. Customers may see timeouts in these regions. Will provide further updates as progress continues. April 15, 2026 9:08AM UTC Identified - Our teams have been able to mitigate a large portion of the attack and our nameservers have started to recover. Customers may still see timeouts in these regions as we work on fine tuning the mitigation and will provide further updates as progress continues. April 15, 2026 9:33AM UTC Identified - Our teams are continuing to fine tune countermeasures in order to mitigate impact on our nameservers. Will provide further updates as progress continues. April 15, 2026 9:59AM UTC Identified - Our teams are continuing to fine tune countermeasures in order to mitigate impact on our nameservers. Will provide further updates as progress continues. April 15, 2026 10:44AM UTC Identified - Our teams are continuing to fine tune countermeasures in order to mitigate impact on our nameservers and we are seeing improvement. Will provide further updates as progress continues. April 15, 2026 11:16AM UTC Resolved - Our teams have updated countermeasures to mitigate the attack and this should be resolved at this time.

April 4, 2026 1:15PM UTC Investigating - We are experiencing a DDoS against nameservers in parts of Asia and parts of Europe. Customers may see timeouts in these regions. Our teams are actively engaged in mitigating efforts. Further updates will be provided as progress continues. April 4, 2026 1:50PM UTC Identified - Our teams have been able to mitigate the attack and our nameservers have recovered in Europe and parts of Asia. The only remaining region still impacted is Singapore. We are still working on fine tuning the mitigation and will provide further updates as progress continues. April 4, 2026 2:30PM UTC Identified - Our teams are continuing to fine tune countermeasures in order to mitigate impact on last remaining region in Singapore. Will provide further updates as progress continues April 4, 2026 2:49PM UTC Monitoring - Countermeasures have been updated for the Singapore area and services should be returning to normal at this time. We are continuing to monitor. April 4, 2026 3:12PM UTC Resolved - Our engineers have updated countermeasures and this should be resolved at this time.

February 2, 2026 10:49AM UTC Investigating - Start Time: 6:06 GMT We are seeing increased latency and error rates regionally and working to resolve issues. February 2, 2026 11:25AM UTC Investigating - We are still working to resolve the issue. Some customers may continue to experience intermittent latency and error rates in select regions. Our teams remain actively engaged and are continuing mitigation efforts. Further updates will be provided as progress continues. February 2, 2026 12:06PM UTC Identified - We have identified the issue and are working on remediation. Some customers may continue to experience intermittent latency and error rates in select regions while this work is ongoing. Our teams remain actively engaged and will continue to provide updates as progress continues. February 2, 2026 12:42PM UTC Identified - Our teams are continuing the work on resolving the identified issue with urgency. Some customers may continue to experience intermittent latency and error rates in select regions while this work is ongoing. Our teams remain actively engaged and will continue to provide updates as progress continues. February 2, 2026 1:17PM UTC Identified - Our teams are actively working to resolve the identified issue as quickly as possible. During this time, some customers might still experience occasional latency and error rates in certain regions. We will keep you informed with updates as we make progress. February 2, 2026 1:55PM UTC Identified - Our teams are actively working to resolve the identified issue as quickly as possible. During this time, some customers might still experience occasional latency and error rates in certain regions. We will keep you informed with updates as we make progress. February 2, 2026 2:47PM UTC Identified - Our teams are actively working to resolve the identified issue as quickly as possible. During this time, some customers might still experience occasional latency and error rates in certain regions. We will keep you informed with updates as we make progress. February 2, 2026 3:05PM UTC Identified - We are now rolling out a fix for the identified issue. Some customers may continue to experience intermittent latency and error rates in select regions while deployment is in progress. We will continue to provide updates as rollout progresses. February 2, 2026 3:52PM UTC Identified - Our teams are continuing to rolling out a fix for the identified issue. Some customers may continue to experience intermittent latency and error rates in select regions while deployment is in progress. We will continue to provide updates as rollout progresses. February 2, 2026 4:35PM UTC Identified - Our teams are continuing to rolling out a fix for the identified issue. Some customers may continue to experience intermittent latency and error rates in select regions while deployment is in progress. We will continue to provide updates as rollout progresses. February 2, 2026 5:07PM UTC Identified - Our teams are continuing to roll out a fix for the identified issue, with deployment progressing across the environment and impact becoming more limited. Some customers may continue to experience intermittent latency and error rates in select regions while this work is ongoing. We will continue to provide updates as rollout progresses. February 2, 2026 5:42PM UTC Identified - Our teams are continuing to roll out a fix for the identified issue, with deployment progressing across the environment and impact becoming more limited. Some customers may continue to experience intermittent latency and error rates in select regions while this work is ongoing. We will continue to provide updates as rollout progresses. February 2, 2026 6:54PM UTC Monitoring - We are no longer observing service degradation and are continuing to monitor closely for any recurrence. Update deployment is still in progress across all locations, and we will provide additional updates as rollout continues. February 2, 2026 7:00PM UTC Monitoring - We are no longer observing service degradation and are continuing to monitor closely for any recurrence. Update deployment is still in progress across all locations, and we will provide additional updates as rollout continues. February 2, 2026 8:01PM UTC Monitoring - We are no longer observing service degradation and are continuing to monitor closely for any recurrence. Update deployment is still in progress across all locations, and we will provide additional updates as rollout continues. February 2, 2026 9:34PM UTC Resolved - The identified impact has been mitigated, and remediation actions have been applied. Our teams are continuing to monitor the environment closely to ensure stability.

January 16, 2026 10:42AM UTC Investigating - UltraDNS is currently seeing intermittent SAML login failures. We are currently investigating this issue and will provide further updates as soon as we have them January 16, 2026 11:08AM UTC Resolved - The SAML login issue has now been resolved.