Historique des pannes de Dnsimple

1. 16 octobre 2026 à 19:06 UTCinvestigating

   Notre fournisseur d'hébergement effectue une maintenance d'urgence à l'échelle de la plate-forme qui nécessite des redémarrages roulants de ses serveurs dans toutes les régions. Par conséquent, l'application web sandbox peut être indisponible par intermittence ou lente à répondre. Chaque redémarrage devrait causer environ 15 à 20 minutes de temps d'arrêt, et plus d'une interruption peut survenir pendant que le déploiement se poursuit. Les environnements de production ne sont pas affectés. Aucune action n'est nécessaire de votre part. Si une demande échoue, veuillez réessayer après quelques minutes. Les données dans le bac à sable ne devraient pas être perdues. Nous suivons les progrès du fournisseur et afficherons une mise à jour lorsque la maintenance est terminée et le bac à sable est stable.

2. 16 octobre 2026 à 19:22 UTCmonitoring

   La maintenance du fournisseur d'hébergement est terminée et l'application web sandbox est disponible. Nous surveillons d'autres questions. Si vous voyez toujours des erreurs, veuillez contacter le support.

3. 17 octobre 2026 à 06:10 UTCresolved

   Cet incident est résolu maintenant, aucun système ne devrait être affecté.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 6 septembre 2026 à 13:10 UTCinvestigating

   Notre région de l'UE à Varsovie connaît des problèmes de réseau local. Nous enquêtons sur la question. Le seul impact sur notre service est une latence légèrement plus élevée dans la région, car le trafic est acheminé vers nos régions voisines en Europe.

2. 6 septembre 2026 à 15:55 UTCresolved

   La question a été réglée en amont et la région de Varsovie a été stable.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 8 août 2026 à 00:27 UTCinvestigating

   Nous enquêtons actuellement sur cette question.

2. 8 août 2026 à 00:28 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 8 août 2026 à 02:47 UTCidentified

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

4. 8 août 2026 à 05:14 UTCmonitoring

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

5. 8 août 2026 à 05:53 UTCresolved

   This incident has been resolved.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 23 juillet 2026 à 14:02 UTCinvestigating

   Nous enquêtons actuellement sur cette question.

2. 23 juillet 2026 à 14:10 UTCmonitoring

   Tous les systèmes fonctionnent normalement, et nous étudions la cause profonde.

3. 23 juillet 2026 à 14:46 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 5 juin 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 juin 2026 à 15:38 UTCresolved

   This incident has been resolved.

1. 22 mai 2026 à 10:44 UTCinvestigating

   We are currently investigating this issue.

2. 22 mai 2026 à 13:35 UTCidentified

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

3. 22 mai 2026 à 18:46 UTCmonitoring

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

4. 22 mai 2026 à 22:18 UTCresolved

   This incident has been resolved.

1. 18 mai 2026 à 21:26 UTCinvestigating

   We are currently investigating this issue.

2. 18 mai 2026 à 21:42 UTCmonitoring

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

3. 18 mai 2026 à 22:00 UTCresolved

   This incident has been resolved.

1. 8 mai 2026 à 05:18 UTCinvestigating

   We are investigating intermittent network failures in the Sydney region.

2. 8 mai 2026 à 05:41 UTCinvestigating

   We are continuing to investigate this issue.

3. 8 mai 2026 à 05:42 UTCmonitoring

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

4. 8 mai 2026 à 08:33 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8 mai 2026 à 10:00 UTCresolved

   This incident has been resolved.

1. 20 avril 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 avril 2026 à 20:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 avril 2026 à 20:21 UTCidentified

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

4. 20 avril 2026 à 20:43 UTCmonitoring

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

5. 20 avril 2026 à 21:44 UTCresolved

   This incident has been resolved.

1. 5 mars 2026 à 10:14 UTCinvestigating

   We are currently investigating this issue.

2. 5 mars 2026 à 10:28 UTCidentified

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

3. 5 mars 2026 à 11:15 UTCidentified

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

4. 5 mars 2026 à 11:59 UTCmonitoring

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

5. 5 mars 2026 à 12:46 UTCresolved

   This incident has been resolved.

1. 2 mars 2026 à 18:47 UTCinvestigating

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

2. 2 mars 2026 à 19:05 UTCidentified

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

3. 2 mars 2026 à 19:29 UTCmonitoring

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

4. 2 mars 2026 à 22:00 UTCresolved

   This incident has been resolved.

1. 18 février 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 février 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 février 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 février 2026 à 17:30 UTCinvestigating

   We are running restores to bring back services online

3. 10 février 2026 à 17:45 UTCidentified

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

4. 10 février 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 février 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 février 2026 à 18:50 UTCidentified

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

7. 10 février 2026 à 19:18 UTCidentified

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

8. 10 février 2026 à 19:21 UTCidentified

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

9. 10 février 2026 à 19:27 UTCidentified

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

10. 10 février 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 février 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 février 2026 à 20:18 UTCmonitoring

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

13. 10 février 2026 à 23:18 UTCresolved

    This incident has been resolved.

1. 3 février 2026 à 23:15 UTCinvestigating

   We are currently investigating this issue.

2. 4 février 2026 à 00:28 UTCinvestigating

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

3. 4 février 2026 à 00:29 UTCresolved

   This incident has been resolved.

1. 3 février 2026 à 19:55 UTCinvestigating

   We are investigating intermittent network failures in AMS region.

2. 3 février 2026 à 20:44 UTCmonitoring

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

3. 3 février 2026 à 23:41 UTCresolved

   This incident has been resolved.

1. 29 janvier 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 janvier 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 janvier 2026 à 17:58 UTCresolved

   This incident has been resolved.

1. 22 janvier 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 janvier 2026 à 08:41 UTCresolved

   This incident has been resolved.

1. 30 décembre 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 décembre 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 décembre 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 décembre 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 décembre 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 décembre 2025 à 01:49 UTCmonitoring

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

4. 16 décembre 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 décembre 2025 à 21:53 UTCinvestigating

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

2. 11 décembre 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 décembre 2025 à 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 11 décembre 2025 à 23:11 UTCresolved

   This incident has been resolved.