DNSimple Outage History

DNSimple is up right now

DNSimple had 37 outages in the last 2 years totaling 61h 48m of downtime — averaging 1.5 incidents per month.

There were 37 DNSimple outages since May 2, 2025 totaling 61h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://dnsimple.statuspage.io

Minor August 8, 2026

Degraded service in London region

Detected by Pingoru
Aug 08, 2026, 12:27 AM UTC
Resolved
Aug 08, 2026, 05:53 AM UTC
Duration
5h 25m
Affected: Name Servers
Timeline · 5 updates
  1. investigating Aug 08, 2026, 12:27 AM UTC

    We are currently investigating this issue.

  2. investigating Aug 08, 2026, 12:28 AM UTC

    We are continuing to investigate this issue.

  3. identified Aug 08, 2026, 02:47 AM UTC

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

  4. monitoring Aug 08, 2026, 05:14 AM UTC

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

  5. resolved Aug 08, 2026, 05:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2026

500 errors on production website

Detected by Pingoru
Jul 23, 2026, 02:02 PM UTC
Resolved
Jul 23, 2026, 02:46 PM UTC
Duration
43m
Affected: WebsiteZone deployment
Timeline · 3 updates
  1. investigating Jul 23, 2026, 02:02 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 23, 2026, 02:10 PM UTC

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

  3. resolved Jul 23, 2026, 02:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 5, 2026

Intermittent network failures in SYD/TKO region

Detected by Pingoru
Jun 05, 2026, 03:34 PM UTC
Resolved
Jun 05, 2026, 03:38 PM UTC
Duration
4m
Affected: Name Servers
Timeline · 2 updates
  1. investigating Jun 05, 2026, 03:34 PM 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 Jun 05, 2026, 03:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 22, 2026

Degraded service in Amsterdam region

Detected by Pingoru
May 22, 2026, 10:44 AM UTC
Resolved
May 22, 2026, 10:18 PM UTC
Duration
11h 33m
Affected: Name Servers
Timeline · 5 updates
  1. investigating May 22, 2026, 10:44 AM UTC

    We are currently investigating this issue.

  2. monitoring May 22, 2026, 01:23 PM UTC

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

  3. identified May 22, 2026, 01:35 PM UTC

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

  4. monitoring May 22, 2026, 06:46 PM UTC

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

  5. resolved May 22, 2026, 10:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Intermittent network failures in Sydney region

Detected by Pingoru
May 08, 2026, 05:18 AM UTC
Resolved
May 08, 2026, 10:00 AM UTC
Duration
4h 42m
Affected: Name Servers
Timeline · 5 updates
  1. investigating May 08, 2026, 05:18 AM UTC

    We are investigating intermittent network failures in the Sydney region.

  2. investigating May 08, 2026, 05:41 AM UTC

    We are continuing to investigate this issue.

  3. monitoring May 08, 2026, 05:42 AM UTC

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

  4. monitoring May 08, 2026, 08:33 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved May 08, 2026, 10:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 20, 2026

dnsimple.com availability issues

Detected by Pingoru
Apr 20, 2026, 07:54 PM UTC
Resolved
Apr 20, 2026, 09:44 PM UTC
Duration
1h 50m
Affected: WebsiteAPIURL RedirectorWebhooksNotifications
Timeline · 5 updates
  1. investigating Apr 20, 2026, 07:54 PM UTC

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

  2. investigating Apr 20, 2026, 08:07 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 20, 2026, 08:21 PM UTC

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

  4. monitoring Apr 20, 2026, 08:43 PM UTC

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

  5. resolved Apr 20, 2026, 09:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 5, 2026

Delay in Zone Updates

Detected by Pingoru
Mar 05, 2026, 10:14 AM UTC
Resolved
Mar 05, 2026, 12:46 PM UTC
Duration
2h 32m
Affected: Zone deploymentSecondary DNSNotifications
Timeline · 5 updates
  1. investigating Mar 05, 2026, 10:14 AM UTC

    We are currently investigating this issue.

  2. identified Mar 05, 2026, 10:28 AM UTC

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

  3. identified Mar 05, 2026, 11:15 AM UTC

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

  4. monitoring Mar 05, 2026, 11:59 AM UTC

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

  5. resolved Mar 05, 2026, 12:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Intermittent network failures in FRA region

Detected by Pingoru
Mar 02, 2026, 06:47 PM UTC
Resolved
Mar 02, 2026, 10:00 PM UTC
Duration
3h 12m
Affected: Name Servers
Timeline · 4 updates
  1. investigating Mar 02, 2026, 06:47 PM UTC

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

  2. identified Mar 02, 2026, 07:05 PM UTC

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

  3. monitoring Mar 02, 2026, 07:29 PM UTC

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

  4. resolved Mar 02, 2026, 10:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 18, 2026

Intermittent DNS Resolution for Certain ALIAS Records

Detected by Pingoru
Feb 18, 2026, 02:24 PM UTC
Resolved
Feb 18, 2026, 04:07 PM UTC
Duration
1h 42m
Affected: Name Servers
Timeline · 2 updates
  1. monitoring Feb 18, 2026, 02:24 PM 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 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. resolved Feb 18, 2026, 04:07 PM 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.

Read the full incident report →

Minor February 3, 2026

Intermittent network failures in AMS region

Detected by Pingoru
Feb 03, 2026, 07:55 PM UTC
Resolved
Feb 03, 2026, 11:41 PM UTC
Duration
3h 46m
Affected: Name Servers
Timeline · 3 updates
  1. investigating Feb 03, 2026, 07:55 PM UTC

    We are investigating intermittent network failures in AMS region.

  2. monitoring Feb 03, 2026, 08:44 PM UTC

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

  3. resolved Feb 03, 2026, 11:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026

Cache edge degraded performance

Detected by Pingoru
Jan 29, 2026, 04:52 PM UTC
Resolved
Jan 29, 2026, 05:58 PM UTC
Duration
1h 5m
Affected: Name Servers
Timeline · 3 updates
  1. monitoring Jan 29, 2026, 04:52 PM 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 Jan 29, 2026, 05:20 PM UTC

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

  3. resolved Jan 29, 2026, 05:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 22, 2026

Elevated error rates in zone.vision

Detected by Pingoru
Jan 22, 2026, 07:29 AM UTC
Resolved
Jan 22, 2026, 08:41 AM UTC
Duration
1h 12m
Affected: WebsiteAPI
Timeline · 2 updates
  1. investigating Jan 22, 2026, 07:29 AM 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 affected. Our UI will not be able to display the current name servers. Domain registration and DNS resolution is not affected.

  2. resolved Jan 22, 2026, 08:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 16, 2025

Network Performance Issues

Detected by Pingoru
Dec 16, 2025, 01:06 AM UTC
Resolved
Dec 16, 2025, 02:06 AM UTC
Duration
59m
Affected: Name Servers
Timeline · 4 updates
  1. investigating Dec 16, 2025, 01:06 AM UTC

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

  2. identified Dec 16, 2025, 01:23 AM 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 conditions to return to normal. Thank you for your patience and understanding.

  3. monitoring Dec 16, 2025, 01:49 AM UTC

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

  4. resolved Dec 16, 2025, 02:06 AM UTC

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

Read the full incident report →

Minor December 11, 2025

Intermittent DNS resolution failures

Detected by Pingoru
Dec 11, 2025, 09:53 PM UTC
Resolved
Dec 11, 2025, 11:11 PM UTC
Duration
1h 18m
Affected: Name Servers
Timeline · 4 updates
  1. investigating Dec 11, 2025, 09:53 PM UTC

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

  2. monitoring Dec 11, 2025, 10:14 PM UTC

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

  3. monitoring Dec 11, 2025, 10:14 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 11, 2025, 11:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 4, 2025

CSS styles not loading for dnsimple.com

Detected by Pingoru
Dec 04, 2025, 09:24 AM UTC
Resolved
Dec 04, 2025, 09:27 AM UTC
Duration
2m
Affected: Website
Timeline · 2 updates
  1. identified Dec 04, 2025, 09:24 AM 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 Dec 04, 2025, 09:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 1, 2025

Elevated latencies for DNS queries

Detected by Pingoru
Dec 01, 2025, 12:54 PM UTC
Resolved
Dec 01, 2025, 03:36 PM UTC
Duration
2h 42m
Affected: Name Servers
Timeline · 3 updates
  1. investigating Dec 01, 2025, 12:54 PM 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 Dec 01, 2025, 01:10 PM UTC

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

  3. resolved Dec 01, 2025, 03:36 PM UTC

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

Read the full incident report →

Minor November 28, 2025

CDN Assets Refresh in Progress

Detected by Pingoru
Nov 28, 2025, 04:28 PM UTC
Resolved
Nov 28, 2025, 04:42 PM UTC
Duration
14m
Affected: WebsiteSandbox Website
Timeline · 2 updates
  1. monitoring Nov 28, 2025, 04:28 PM 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 Nov 28, 2025, 04:42 PM UTC

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

Read the full incident report →

Notice November 27, 2025

Traffic re-routed from LHR (London, UK) edge datacenter

Detected by Pingoru
Nov 27, 2025, 03:00 PM UTC
Resolved
Nov 27, 2025, 06:24 PM UTC
Duration
3h 24m
Affected: Name Servers
Timeline · 3 updates
  1. identified Nov 27, 2025, 03:00 PM 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 [email protected]

  2. monitoring Nov 27, 2025, 04:27 PM UTC

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

  3. resolved Nov 27, 2025, 06:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 10, 2025

DNS resolution issues

Detected by Pingoru
Nov 10, 2025, 05:52 PM UTC
Resolved
Nov 10, 2025, 07:48 PM UTC
Duration
1h 55m
Affected: Name Servers
Timeline · 4 updates
  1. investigating Nov 10, 2025, 05:52 PM UTC

    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.

  2. identified Nov 10, 2025, 06:08 PM 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 [email protected] with traceroutes and dig trace queries if you can.

  3. monitoring Nov 10, 2025, 06:12 PM UTC

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

  4. resolved Nov 10, 2025, 07:48 PM UTC

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

Read the full incident report →

Minor November 5, 2025

Regional DNS (San Jose)

Detected by Pingoru
Nov 05, 2025, 11:56 PM UTC
Resolved
Nov 06, 2025, 01:31 AM UTC
Duration
1h 34m
Affected: Name Servers
Timeline · 5 updates
  1. investigating Nov 05, 2025, 11:56 PM UTC

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

  2. identified Nov 06, 2025, 12:32 AM UTC

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

  3. identified Nov 06, 2025, 12:43 AM UTC

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

  4. monitoring Nov 06, 2025, 12:43 AM UTC

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

  5. resolved Nov 06, 2025, 01:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Intermittent resolution failures.

Detected by Pingoru
Oct 29, 2025, 10:05 PM UTC
Resolved
Oct 29, 2025, 11:52 PM UTC
Duration
1h 47m
Affected: Name Servers
Timeline · 4 updates
  1. investigating Oct 29, 2025, 10:05 PM UTC

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

  2. identified Oct 29, 2025, 10:07 PM UTC

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

  3. monitoring Oct 29, 2025, 10:50 PM UTC

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

  4. resolved Oct 29, 2025, 11:52 PM UTC

    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]

Read the full incident report →

Critical October 24, 2025

DNSimple is unreachable

Detected by Pingoru
Oct 24, 2025, 12:21 AM UTC
Resolved
Oct 24, 2025, 02:00 AM UTC
Duration
1h 38m
Affected: WebsiteAPI
Timeline · 4 updates
  1. investigating Oct 24, 2025, 12:21 AM UTC

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

  2. investigating Oct 24, 2025, 12:37 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Oct 24, 2025, 12:37 AM 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 Oct 24, 2025, 02:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 14, 2025

Intermittent network failures in SV1 region

Detected by Pingoru
Oct 14, 2025, 08:26 PM UTC
Resolved
Oct 14, 2025, 09:14 PM UTC
Duration
48m
Affected: Name Servers
Timeline · 4 updates
  1. investigating Oct 14, 2025, 08:26 PM UTC

    We are investigating intermittent network failures in SV1 region.

  2. identified Oct 14, 2025, 08:44 PM UTC

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

  3. monitoring Oct 14, 2025, 08:50 PM UTC

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

  4. resolved Oct 14, 2025, 09:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 10, 2025

URL redirects have degraded performance

Detected by Pingoru
Oct 10, 2025, 12:53 PM UTC
Resolved
Oct 10, 2025, 02:11 PM UTC
Duration
1h 18m
Affected: URL Redirector
Timeline · 3 updates
  1. identified Oct 10, 2025, 12:53 PM 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 Oct 10, 2025, 01:25 PM UTC

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

  3. resolved Oct 10, 2025, 02:11 PM UTC

    This incident has been resolved.

Read the full incident report →