DNSimple

Affected: Sandbox Website, Sandbox API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-16 19:06 UTC

   Our hosting provider is performing emergency platform-wide maintenance that requires rolling restarts of its servers in all regions. As a result, the sandbox web application may be intermittently unavailable or slow to respond. Each restart is expected to cause roughly 15–20...

2. monitoring 2026-10-16 19:22 UTC

   The hosting provider’s maintenance is complete and the sandbox web application is available. We are monitoring for further issues. If you still see errors, please contact support.

3. resolved 2026-10-17 06:10 UTC

   This incident is resolved now, no system should be affected.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-06 13:10 UTC

   Our Warsaw EU region is experiencing local network issues. We are investigating the issue. The only impact on our service is slightly higher latency in the region, as traffic is routed to our nearby regions in Europe.

2. resolved 2026-09-06 15:55 UTC

   The issue was resolved upstream, and the Warsaw region has been stable.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-08 00:27 UTC

   We are currently investigating this issue.

2. investigating 2026-08-08 00:28 UTC

   We are continuing to investigate this issue.

3. identified 2026-08-08 02:47 UTC

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

4. monitoring 2026-08-08 05:14 UTC

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

5. resolved 2026-08-08 05:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website, Zone deployment

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 14:02 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-23 14:10 UTC

   All systems are operating normally, and we are investigating root cause.

3. resolved 2026-07-23 14:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Sandbox Website, Sandbox API

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-22 05:09 UTC

   The recent maintenance on the Sandbox environment introduced instability in the system. We have identified the cause and are actively taking steps to tune the system and bring it back fully operational. No production systems are affected.

2. identified 2026-07-22 07:58 UTC

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

3. resolved 2026-07-22 07:59 UTC

   The system has been stable; we consider this incident to be over.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-05 15:34 UTC

   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. resolved 2026-06-05 15:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 10:44 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-22 13:23 UTC

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

3. identified 2026-05-22 13:35 UTC

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

4. monitoring 2026-05-22 18:46 UTC

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

5. resolved 2026-05-22 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-18 21:26 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-18 21:42 UTC

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

3. resolved 2026-05-18 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-08 05:18 UTC

   We are investigating intermittent network failures in the Sydney region.

2. investigating 2026-05-08 05:41 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-05-08 05:42 UTC

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

4. monitoring 2026-05-08 08:33 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-05-08 10:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website, API, URL Redirector, Webhooks, Notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-20 19:54 UTC

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

2. investigating 2026-04-20 20:07 UTC

   We are continuing to investigate this issue.

3. identified 2026-04-20 20:21 UTC

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

4. monitoring 2026-04-20 20:43 UTC

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

5. resolved 2026-04-20 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Zone deployment, Secondary DNS, Notifications

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-05 10:14 UTC

   We are currently investigating this issue.

2. identified 2026-03-05 10:28 UTC

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

3. identified 2026-03-05 11:15 UTC

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

4. monitoring 2026-03-05 11:59 UTC

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

5. resolved 2026-03-05 12:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-02 18:47 UTC

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

2. identified 2026-03-02 19:05 UTC

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

3. monitoring 2026-03-02 19:29 UTC

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

4. resolved 2026-03-02 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-02-18 14:24 UTC

   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...

2. resolved 2026-02-18 16:07 UTC

   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.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: API, Sandbox API, Name Servers, URL Redirector, Zone deployment

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-10 17:06 UTC

   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...

2. investigating 2026-02-10 17:30 UTC

   We are running restores to bring back services online

3. identified 2026-02-10 17:45 UTC

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

4. identified 2026-02-10 18:06 UTC

   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. identified 2026-02-10 18:32 UTC

   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. identified 2026-02-10 18:50 UTC

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

7. identified 2026-02-10 19:18 UTC

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

8. identified 2026-02-10 19:21 UTC

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

9. identified 2026-02-10 19:27 UTC

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

10. identified 2026-02-10 19:38 UTC

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

11. identified 2026-02-10 19:51 UTC

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

12. monitoring 2026-02-10 20:18 UTC

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

13. resolved 2026-02-10 23:18 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Zone deployment

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 23:15 UTC

   We are currently investigating this issue.

2. investigating 2026-02-04 00:28 UTC

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

3. resolved 2026-02-04 00:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 19:55 UTC

   We are investigating intermittent network failures in AMS region.

2. monitoring 2026-02-03 20:44 UTC

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

3. resolved 2026-02-03 23:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-01-29 16:52 UTC

   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. monitoring 2026-01-29 17:20 UTC

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

3. resolved 2026-01-29 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-22 07:29 UTC

   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...

2. resolved 2026-01-22 08:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-30 19:03 UTC

   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. monitoring 2025-12-30 19:44 UTC

   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. resolved 2025-12-30 20:55 UTC

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

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-16 01:06 UTC

   We're receiving reports of DNS resolution issues and we are investigating. If you're experiencing these issues yourself, please email support@dnsimple.com.

2. identified 2025-12-16 01:23 UTC

   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...

3. monitoring 2025-12-16 01:49 UTC

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

4. resolved 2025-12-16 02:06 UTC

   This network issue has been resolved fully. If you have any further issues please let us know by emailing support@dnsimple.com

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-11 21:53 UTC

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

2. monitoring 2025-12-11 22:14 UTC

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

3. monitoring 2025-12-11 22:14 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-12-11 23:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-07 13:05 UTC

   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...

2. monitoring 2025-12-07 13:12 UTC

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

3. resolved 2025-12-07 13:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-07 07:03 UTC

   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...

2. monitoring 2025-12-07 07:13 UTC

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

3. resolved 2025-12-07 07:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-04 09:24 UTC

   We have identified an issue affecting some CSS styles in the web application. This issue impacts the display of UI elements but does not affect DNS resolution or the API. The issue has been identified and a fix is being implemented.

2. resolved 2025-12-04 09:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-01 12:54 UTC

   We are currently experiencing issues with our cache edge, which may cause increased latency for some queries. Our team is actively investigating and implementing mitigations.

2. monitoring 2025-12-01 13:10 UTC

   We have identified the issue and implemented fixes. Systems are recovering and performance is returning to normal.

3. resolved 2025-12-01 15:36 UTC

   The issue has been fully resolved. Services are back to normal.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website, Sandbox Website

Failure mode: CDN or edge layer failed or served bad content. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-11-28 16:28 UTC

   We are currently forcing a refresh of our CDN assets. During this process, some assets may be temporarily unavailable for the next few minutes. We will provide an update once the assets have been fully refreshed and service is restored.

2. resolved 2025-11-28 16:42 UTC

   The update has finished and all assets are now being served correctly.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-27 15:00 UTC

   We are monitoring a downtime in our edge datacenter in LHR (London, UK) region. Other close edge datacenters are picking up the traffic normally. If you're experiencing these issues yourself, please email support@dnsimple.com

2. monitoring 2025-11-27 16:27 UTC

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

3. resolved 2025-11-27 18:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-10 17:52 UTC

   We're receiving reports of DNS resolution issues and we are investigating. If you're experiencing these issues yourself, please email support@dnsimple.com with traceroutes and dig trace queries if you can.

2. identified 2025-11-10 18:08 UTC

   We have isolated the DNS resolution issues only with IPv6 on ns1.dnsimple.com & ns3.dnsimple.com. We're continue to look deeper into this situation. If you're experiencing these issues yourself, please email support@dnsimple.com with traceroutes and dig trace queries if you can.

3. monitoring 2025-11-10 18:12 UTC

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

4. resolved 2025-11-10 19:48 UTC

   This network issue has been resolved fully. If you have any further issues please let us know by emailing support@dnsimple.com

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-05 23:56 UTC

   We are seeing issues with the San Jose DC and are routing traffic to other datacenters while looking into this

2. identified 2025-11-06 00:32 UTC

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

3. identified 2025-11-06 00:43 UTC

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

4. monitoring 2025-11-06 00:43 UTC

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

5. resolved 2025-11-06 01:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A zone, region or data center became unavailable. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-05 21:45 UTC

   We are seeing issues with the San Jose DC and are routing traffic to other datacenters while looking into this

2. monitoring 2025-11-05 22:17 UTC

   The network is stabilized and we are verifying things are back to normal and not flapping.

3. resolved 2025-11-05 22:58 UTC

   We are not seeing any more latency or issues in San Jose. if you are seeing any more issues please let us know at support@dnsimple.com

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-29 22:05 UTC

   We are having reports of intermittent resolution failures and issues with some name servers.

2. identified 2025-10-29 22:07 UTC

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

3. monitoring 2025-10-29 22:50 UTC

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

4. resolved 2025-10-29 23:52 UTC

   This incident has been fully resolved and we have not seen any further errors. If you see any problems please reach out at support@dnsimple.com

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website, API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-24 00:21 UTC

   We're currently investigating an issue with our website and API. DNS resolution is not affected.

2. investigating 2025-10-24 00:37 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-10-24 00:37 UTC

   Connectivity to dnsimple.com has been fully restored. API access is once again operational. We're monitoring the traffic. DNS resolution was not affected during this incident.

4. resolved 2025-10-24 02:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-14 20:26 UTC

   We are investigating intermittent network failures in SV1 region.

2. identified 2025-10-14 20:44 UTC

   An issue preventing DNS records updates in our nameservers in SV1 region has been spotted. We're working towards a fix.

3. monitoring 2025-10-14 20:50 UTC

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

4. resolved 2025-10-14 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: URL Redirector

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-10 12:53 UTC

   We are seeing an issue an elevated error rate in fetching certificates to handle HTTPS requests for the URL redirector. Our team is actively working on fixing the issue.

2. monitoring 2025-10-10 13:25 UTC

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

3. resolved 2025-10-10 14:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-02 07:49 UTC

   We're currently investigating an issue with our website and API. DNS resolution is not affected.

2. monitoring 2025-10-02 07:58 UTC

   Connectivity to dnsimple.com has been fully restored. API access and the HTTPS redirector are once again operational. We're monitoring the traffic. DNS resolution was not affected during this incident.

3. resolved 2025-10-02 08:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-19 18:10 UTC

   We are investigating networking issues to and from the Tokyo data center. Traffic is will be re-route to other data centers.

2. monitoring 2025-09-19 18:18 UTC

   Traffic seems to have stabilized and all replication has caught back up. We are monitoring to ensure there is no further routing issues.

3. resolved 2025-09-19 18:34 UTC

   This incident has been resolved, and we are not seeing further routing issues. If you have any issues reach out at support@dnsimple.com

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-16 06:49 UTC

   We are investigating intermittent network failures in San Jose region.

2. identified 2025-09-16 07:13 UTC

   We have identified the cause of the network failures, and our upstream partners are working to apply a fix. Regional records for the San Jose region won't resolve in the meantime

3. monitoring 2025-09-16 07:28 UTC

   The underlying issue has been fixed, and traffic in the region is recovering to normal levels.

4. resolved 2025-09-16 08:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-11 22:53 UTC

   We're receiving reports of DNS resolution issues and we are investigating. If you're experiencing these issues yourself, please email support@dnsimple.com with traceroutes and dig trace queries if you can.

2. monitoring 2025-09-11 23:16 UTC

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

3. resolved 2025-09-11 23:44 UTC

   We have identified the source of the intermittent resolution issues and resolved it. If you're still experiencing this kind of issues, please email support@dnsimple.com with traceroutes and dig trace queries if you can.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Website

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-01 14:32 UTC

   We are currently investigating this issue.

2. identified 2025-09-01 14:43 UTC

   Networking routes from Europe to our application DC show intermittent. We are investigating further and will place further updates.

3. monitoring 2025-09-01 14:50 UTC

   We are no longer showing routing issues from Europe to our application DC. We will keep monitoring the situation.

4. resolved 2025-09-01 15:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: URL Redirector

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-21 11:25 UTC

   We have identified an issue with the SSL chain that our Redirector service uses for the most recent Let's Encrypt SSL certificates. This issue only impacts domains with URL redirects with HTTPS sources and SSL certificates issued from August 20th onwards. This issue doesn't...

2. monitoring 2025-08-21 11:57 UTC

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

3. resolved 2025-08-21 12:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Zone deployment

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-08-11 10:32 UTC

   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...

2. resolved 2025-08-11 10:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-22 09:01 UTC

   We are getting reports of high-volume traffic in some of our PoPs. Our team is investigating the issue

2. identified 2025-07-22 09:04 UTC

   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...

3. monitoring 2025-07-22 09:05 UTC

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

4. resolved 2025-07-22 12:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Email Forwards

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-18 05:00 UTC

   We’re currently experiencing problems with email forwarding delivery to a subset of users. We are investigating the root cause and will post updates as soon as we have more information.

2. identified 2025-07-18 08:10 UTC

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

3. identified 2025-07-18 13:00 UTC

   We have fixed the root cause and our team is consolidating the existing email forward configurations in our upstream partner.

4. resolved 2025-07-18 15:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Registrar

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-03 19:25 UTC

   Our upstream registrar partner is experiencing a downtime. This may result in certain registrar operations being delayed or unable to complete. We are monitoring their status page, and we'll post updates here. DNS resolution is not affected.

2. identified 2025-07-03 22:32 UTC

   Our upstream registrar partner is still working on a solution We keep monitoring their status page, and we'll post updates here.

3. identified 2025-07-04 01:28 UTC

   Work toward a resolution is still underway. We keep monitoring our upstream partner status page, and we'll post updates here.

4. monitoring 2025-07-04 03:22 UTC

   System has been stabilized and we are monitoring the results.

5. resolved 2025-07-04 06:33 UTC

   The incident has now been resolved. The system is now operational.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-06-09 13:33 UTC

   We are currently investigating an issue while certain DNSSEC-enabled zones are sporadically returning SERVFAIL. Zones without DNSSEC are not affected.

2. identified 2025-06-09 13:35 UTC

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

3. identified 2025-06-09 13:38 UTC

   We are rolling back a recent deployment to a stable version of our nameservers

4. monitoring 2025-06-09 13:59 UTC

   The rollback has completed. The nameservers that were previously returning invalid data are serving now correct responses. It might take up to the TTL value of the corresponding records to clear out cached responses.

5. resolved 2025-06-09 14:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-23 04:26 UTC

   We are currently investigating increased network latency and intermittent connectivity issues affecting services in our Sydney, Australia region. Traffic is being rerouted to other locations and regional records for the region are unavailable.

2. monitoring 2025-05-23 04:56 UTC

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

3. resolved 2025-05-23 05:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-16 15:53 UTC

   We are currently investigating network problems in our CDG location.

2. monitoring 2025-05-16 16:32 UTC

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

3. resolved 2025-05-16 17:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-16 09:50 UTC

   We have identified the source of the issue and 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 wait for network conditions to return to...

2. monitoring 2025-05-16 12:12 UTC

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

3. resolved 2025-05-16 13:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Affected: Notifications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-16 08:35 UTC

   We’re currently experiencing problems sending transactional and notification emails to a subset of users. Messages to affected addresses may be delayed or fail to arrive. Our team is investigating the root cause with our email provider and will post updates as soon as we have...

2. resolved 2025-05-16 08:56 UTC

   We’ve traced the email delivery failures to hard bounces and automatic suppressions affecting specific recipient addresses. We're resolving this incident.

Excerpts are shortened. Read the full incident on DNSimple's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-08 14:49 UTC

   We are seeing elevated rates of timeouts in ALIAS record resolution in SV1. This is leading to SERVFAIL responses for some ALIAS records.

2. identified 2025-05-08 15:36 UTC

   We have identified the cause of the elevated timeouts affecting our San Jose datacenter. The issue appears to be related to upstream packet loss. We are working with our provider to resolve it.

3. monitoring 2025-05-08 18:23 UTC

   We have identified the networking issues and implemented a workaround to prevent slow replies for ALIAS records. We are monitoring network health and looking to Implement further improvements if necessary

4. resolved 2025-05-08 20:47 UTC

   All issues have been resolved and there should be no further delays in ALIAS record resolution.

Excerpts are shortened. Read the full incident on DNSimple's status page.