Historia awarii Dnsimple

1. 16 października 2026 19:06 UTCinvestigating

   Nasz dostawca usług hostingowych prowadzi awaryjną obsługę platformową wymagającą ponownego uruchomienia serwerów we wszystkich regionach. W rezultacie aplikacja WWW z piaskownicą może być okresowo niedostępna lub wolno reagować. Oczekuje się, że każdy restart spowoduje około 15- 20 minut przestoju i może wystąpić więcej niż jedna przerwa w czasie trwania procesu. Nie ma to wpływu na środowisko produkcyjne. Nie musisz podejmować żadnych działań. Jeśli prośba się nie powiedzie, proszę spróbować ponownie po kilku minutach. Dane w piaskownicy nie powinny zostać utracone. Śledzimy postęp dostawcy i opublikujemy aktualizację po zakończeniu konserwacji i piaskownicy jest stabilny.

2. 16 października 2026 19:22 UTCmonitoring

   Konserwacja dostawcy hostingu jest kompletna i dostępna jest aplikacja WWW piaskownicy. Monitorujemy dalsze kwestie. Jeśli nadal widzisz błędy, skontaktuj się ze wsparciem.

3. 17 października 2026 06:10 UTCresolved

   Ten incydent został rozwiązany teraz, żaden system nie powinien być naruszony.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 6 września 2026 13:10 UTCinvestigating

   Nasz warszawski region UE przeżywa problemy z siecią lokalną. Badamy tę sprawę. Jedynym wpływem na nasze usługi jest nieco wyższe opóźnienie w regionie, ponieważ ruch jest kierowany do naszych pobliskich regionów w Europie.

2. 6 września 2026 15:55 UTCresolved

   Problem został rozwiązany w górę rzeki, a region Warszawy jest stabilny.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 8 sierpnia 2026 00:27 UTCinvestigating

   Obecnie badamy tę kwestię.

2. 8 sierpnia 2026 00:28 UTCinvestigating

   Nadal badamy tę kwestię.

3. 8 sierpnia 2026 02:47 UTCidentified

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

4. 8 sierpnia 2026 05:14 UTCmonitoring

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

5. 8 sierpnia 2026 05:53 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 23 lipca 2026 14:02 UTCinvestigating

   Obecnie badamy tę kwestię.

2. 23 lipca 2026 14:10 UTCmonitoring

   Wszystkie systemy działają normalnie, a my badamy przyczynę.

3. 23 lipca 2026 14:46 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 5 czerwca 2026 15:34 UTCinvestigating

   We are investigating intermittent network failures in SYD/TKO region. Record updates are affected in TKO and SYD and affected regional records may not respond and all other traffic will be rerouted to other regions.

2. 5 czerwca 2026 15:38 UTCresolved

   This incident has been resolved.

1. 22 maja 2026 10:44 UTCinvestigating

   We are currently investigating this issue.

2. 22 maja 2026 13:35 UTCidentified

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

3. 22 maja 2026 18:46 UTCmonitoring

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

4. 22 maja 2026 22:18 UTCresolved

   This incident has been resolved.

1. 18 maja 2026 21:26 UTCinvestigating

   We are currently investigating this issue.

2. 18 maja 2026 21:42 UTCmonitoring

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

3. 18 maja 2026 22:00 UTCresolved

   This incident has been resolved.

1. 8 maja 2026 05:18 UTCinvestigating

   We are investigating intermittent network failures in the Sydney region.

2. 8 maja 2026 05:41 UTCinvestigating

   We are continuing to investigate this issue.

3. 8 maja 2026 05:42 UTCmonitoring

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

4. 8 maja 2026 08:33 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8 maja 2026 10:00 UTCresolved

   This incident has been resolved.

1. 20 kwietnia 2026 19:54 UTCinvestigating

   We are investigating an issue reaching dnsimple.com We will provide an update shortly Thank you for your patience and understanding.

2. 20 kwietnia 2026 20:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 kwietnia 2026 20:21 UTCidentified

   We've identified the issue and are continuing to mitigate the impact

4. 20 kwietnia 2026 20:43 UTCmonitoring

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

5. 20 kwietnia 2026 21:44 UTCresolved

   This incident has been resolved.

1. 5 marca 2026 10:14 UTCinvestigating

   We are currently investigating this issue.

2. 5 marca 2026 10:28 UTCidentified

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

3. 5 marca 2026 11:15 UTCidentified

   Zones updates already normalised. We are currently showing delays in notifications and Secondary DNS updates

4. 5 marca 2026 11:59 UTCmonitoring

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

5. 5 marca 2026 12:46 UTCresolved

   This incident has been resolved.

1. 2 marca 2026 18:47 UTCinvestigating

   We are investigating intermittent network failures in FRA (Frankfurt) region.

2. 2 marca 2026 19:05 UTCidentified

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

3. 2 marca 2026 19:29 UTCmonitoring

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

4. 2 marca 2026 22:00 UTCresolved

   This incident has been resolved.

1. 18 lutego 2026 14:24 UTCmonitoring

   Starting at 08:35 UTC, we are experiencing intermittent DNS resolution issues affecting a subset of ALIAS records that point to hostnames within the same zone. Earlier today, we began rolling out improvements to our alias resolution handling. During the deployment, a bug was introduced that manifests when an ALIAS record targets a name inside its own zone. Because the updated logic is not yet fully deployed across all authoritative nameservers, affected records may resolve inconsistently depending on which nameserver handles the query. This is resulting in sporadic resolution degradation for impacted ALIAS records. We have identified the issue and are currently rolling back the changes across the affected authoritative nameservers. We are actively monitoring resolution behavior as the rollback progresses. We will provide further updates once the rollback is fully complete and resolution behavior has stabilized. We apologize for the disruption and appreciate your patience.

2. 18 lutego 2026 16:07 UTCresolved

   The rollback has completed, and DNS resolution has returned to normal behavior. We will be making follow-up improvements to alias-resolution handling, including additional safeguards and testing to prevent recurrence.

1. 10 lutego 2026 17:06 UTCinvestigating

   We are currently investigating an issue affecting our infrastructure that is causing some applications to restart unexpectedly. As a result, customers may experience intermittent disruptions or degraded performance across our systems. Our team is actively working to stabilize the situation and restore normal operation as quickly as possible. We’ll continue to share updates here as we learn more. Thank you for your patience.

2. 10 lutego 2026 17:30 UTCinvestigating

   We are running restores to bring back services online

3. 10 lutego 2026 17:45 UTCidentified

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

4. 10 lutego 2026 18:06 UTCidentified

   Our initial attempts to restore our cluster has failed. We are working on bringing the services up in a fresh cluster. Thank you for your patience

5. 10 lutego 2026 18:32 UTCidentified

   We are still working diligently to restore service in our new production orchestration cluster. We will continue to provide updates as the status changes.

6. 10 lutego 2026 18:50 UTCidentified

   We've started restoring backend services. We expect to have services restored shortly!!

7. 10 lutego 2026 19:18 UTCidentified

   Restores are completing and we will be bringing DNS services back online soon.

8. 10 lutego 2026 19:21 UTCidentified

   Nameservers are currently recovering, and we are bringing other services online.

9. 10 lutego 2026 19:27 UTCidentified

   We've restored half of our infrastructure, and are presently restoring services for the other half.

10. 10 lutego 2026 19:38 UTCidentified

    We've restored most customer facing services. We are still actively restoring the Sandbox API and other internal services. Thanks.

11. 10 lutego 2026 19:51 UTCidentified

    Production services are back online. We are monitoring their state and continuing to work on the Sandbox API and other services.

12. 10 lutego 2026 20:18 UTCmonitoring

    All systems are currently operational and the team is continuing to monitor while we investigate.

13. 10 lutego 2026 23:18 UTCresolved

    This incident has been resolved.

1. 3 lutego 2026 23:15 UTCinvestigating

   We are currently investigating this issue.

2. 4 lutego 2026 00:28 UTCinvestigating

   We have identified the cause of the issue and zone deployments are working normally.

3. 4 lutego 2026 00:29 UTCresolved

   This incident has been resolved.

1. 3 lutego 2026 19:55 UTCinvestigating

   We are investigating intermittent network failures in AMS region.

2. 3 lutego 2026 20:44 UTCmonitoring

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

3. 3 lutego 2026 23:41 UTCresolved

   This incident has been resolved.

1. 29 stycznia 2026 16:52 UTCmonitoring

   We are observing degraded performance at our cache edge nodes, which may impact request latency for some users. Our team is actively investigating the cause and working to mitigate the issue.

2. 29 stycznia 2026 17:20 UTCmonitoring

   Cache edge performance has been stable for some time, and we have seen no further issues. We keep monitoring the situation

3. 29 stycznia 2026 17:58 UTCresolved

   This incident has been resolved.

1. 22 stycznia 2026 07:29 UTCinvestigating

   We are currently seeing elevated error rates for our zone inspection service, this affected the following services: - Let's Encrypt SSL Certificate issuance is affected. We cannot issue or auto-renew Let's Encrypt SSL certificate at this moment. - Display domain resolution is affected. Our UI will not be able to display the current name servers. Domain registration and DNS resolution is not affected.

2. 22 stycznia 2026 08:41 UTCresolved

   This incident has been resolved.

1. 30 grudnia 2025 19:03 UTCinvestigating

   We are observing degraded performance at our cache edge nodes, which may impact request latency for some users. Our team is actively investigating the cause and working to mitigate the issue.

2. 30 grudnia 2025 19:44 UTCmonitoring

   We have identified the cause as an issue with a downstream infrastructure provider. Mitigation steps have been applied to stabilize our cache edge nodes, and we are closely monitoring the system while awaiting confirmation that the provider has fully recovered.

3. 30 grudnia 2025 20:55 UTCresolved

   Cache edge performance has been stable for some time, and we have seen no further issues. The incident is now closed.

1. 16 grudnia 2025 01:06 UTCinvestigating

   We're receiving reports of DNS resolution issues and we are investigating. If you're experiencing these issues yourself, please email [email protected].

2. 16 grudnia 2025 01:23 UTCidentified

   We have identified the source of the issue, and we have implemented performance optimization measures to ensure stability and service continuity. We will continue to monitor the network and update this page with the latest information as we continue to monitor for network conditions to return to normal. Thank you for your patience and understanding.

3. 16 grudnia 2025 01:49 UTCmonitoring

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

4. 16 grudnia 2025 02:06 UTCresolved

   This network issue has been resolved fully. If you have any further issues please let us know by emailing [email protected]

1. 11 grudnia 2025 21:53 UTCinvestigating

   We are currently investigating an intermittent resolution issue in some DC.

2. 11 grudnia 2025 22:14 UTCmonitoring

   We applied a fix and the servers are recovering. We will be monitoring closely and report if the issue persists.

3. 11 grudnia 2025 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 11 grudnia 2025 23:11 UTCresolved

   This incident has been resolved.