Performance Issues in DNS services

Update timeline

1. investigating Apr 28, 2026, 12:19 PM UTC

   We are currently experiencing a partial disruption affecting our DNS services, which may impact domain resolution for some users. Our Engineering team has identified the issue and is actively working on mitigation efforts to restore full service stability as quickly as possible. We will continue to provide timely updates as more information becomes available.

2. identified Apr 28, 2026, 12:35 PM UTC

   We are still actively working to mitigate the ongoing DNS service disruption. Our Engineering team continues to investigate and apply corrective actions to restore full stability. We appreciate your patience and will provide further updates as progress is made.

3. identified Apr 28, 2026, 12:51 PM UTC

   Mitigation efforts are still in progress, and our Engineering team continues to work on restoring full DNS service stability. We are seeing gradual improvements, but some users may still experience intermittent issues with domain resolution. We will keep monitoring the situation closely and share further updates as new information becomes available.

4. identified Apr 28, 2026, 01:09 PM UTC

   Investigation efforts are still in progress, and our Engineering team continues to analyze the issue affecting DNS services. We are actively working to identify the root cause and determine the appropriate mitigation actions. We will continue to provide updates as more information becomes available.

5. monitoring Apr 28, 2026, 01:17 PM UTC

   Mitigation measures have been successfully applied, and the incident affecting DNS services has been mitigated. Service stability has been restored, and we are continuing to monitor the environment to ensure normal operation. We will provide a final update once the investigation is fully concluded.

6. identified Apr 28, 2026, 03:24 PM UTC

   The issue has been identified and a fix is being implemented.

7. identified Apr 28, 2026, 03:24 PM UTC

   We are continuing to work on a fix for this issue.

8. monitoring Apr 28, 2026, 03:35 PM UTC

   A fix has been implemented and we are monitoring the results.

9. identified Apr 28, 2026, 05:55 PM UTC

   The issue has been identified and a fix is being implemented.

10. monitoring Apr 28, 2026, 06:30 PM UTC

    A fix has been implemented and we are monitoring the results.

11. monitoring Apr 28, 2026, 09:27 PM UTC

    We are continuing to monitor for any further issues.

12. resolved Apr 28, 2026, 10:46 PM UTC

    This incident has been resolved.