DNSimple had 30 outages in the last 2 years totaling 57h 19m of downtime — averaging 1.2 incidents per month.
There were 30 DNSimple outages since July 3, 2025 totaling 57h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating intermittent network failures in the Sydney region.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating an issue reaching dnsimple.com We will provide an update shortly Thank you for your patience and understanding.
We are continuing to investigate this issue.
We've identified the issue and are continuing to mitigate the impact
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
Zones updates already normalised. We are currently showing delays in notifications and Secondary DNS updates
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating intermittent network failures in FRA (Frankfurt) region.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
We are investigating intermittent network failures in AMS region.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
Cache edge performance has been stable for some time, and we have seen no further issues. We keep monitoring the situation
This incident has been resolved.
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.
This incident has been resolved.
We're receiving reports of DNS resolution issues and we are investigating. If you're experiencing these issues yourself, please email [email protected].
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.
A fix has been implemented and we are monitoring the results.
This network issue has been resolved fully. If you have any further issues please let us know by emailing [email protected]
We are currently investigating an intermittent resolution issue in some DC.
We applied a fix and the servers are recovering. We will be monitoring closely and report if the issue persists.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
This incident has been resolved.
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.
We have identified the issue and implemented fixes. Systems are recovering and performance is returning to normal.
The issue has been fully resolved. Services are back to normal.
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.
The update has finished and all assets are now being served correctly.
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 [email protected]
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're receiving reports of DNS resolution issues and we are investigating. If you're experiencing these issues yourself, please email [email protected] with traceroutes and dig trace queries if you can.
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 [email protected] with traceroutes and dig trace queries if you can.
A fix has been implemented and we are monitoring the results.
This network issue has been resolved fully. If you have any further issues please let us know by emailing [email protected]
We are seeing issues with the San Jose DC and are routing traffic to other datacenters while looking into this
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are having reports of intermittent resolution failures and issues with some name servers.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been fully resolved and we have not seen any further errors. If you see any problems please reach out at [email protected]
We're currently investigating an issue with our website and API. DNS resolution is not affected.
We are continuing to investigate this issue.
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.
This incident has been resolved.
We are investigating intermittent network failures in SV1 region.
An issue preventing DNS records updates in our nameservers in SV1 region has been spotted. We're working towards a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating networking issues to and from the Tokyo data center. Traffic is will be re-route to other data centers.
Traffic seems to have stabilized and all replication has caught back up. We are monitoring to ensure there is no further routing issues.
This incident has been resolved, and we are not seeing further routing issues. If you have any issues reach out at [email protected]
We are investigating intermittent network failures in San Jose region.
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
The underlying issue has been fixed, and traffic in the region is recovering to normal levels.
This incident has been resolved.