DNSimple Outage History

DNSimple is up right now

There were 6 DNSimple outages since February 3, 2026 totaling 19h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://dnsimple.statuspage.io

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 →

Major February 10, 2026

Infrastructure Instability

Detected by Pingoru
Feb 10, 2026, 05:06 PM UTC
Resolved
Feb 10, 2026, 11:18 PM UTC
Duration
6h 12m
Affected: APISandbox APIName ServersURL RedirectorZone deployment
Timeline · 13 updates
  1. investigating Feb 10, 2026, 05:06 PM 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 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. investigating Feb 10, 2026, 05:30 PM UTC

    We are running restores to bring back services online

  3. identified Feb 10, 2026, 05:45 PM UTC

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

  4. identified Feb 10, 2026, 06:06 PM 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 Feb 10, 2026, 06:32 PM 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 Feb 10, 2026, 06:50 PM UTC

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

  7. identified Feb 10, 2026, 07:18 PM UTC

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

  8. identified Feb 10, 2026, 07:21 PM UTC

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

  9. identified Feb 10, 2026, 07:27 PM UTC

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

  10. identified Feb 10, 2026, 07:38 PM UTC

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

  11. identified Feb 10, 2026, 07:51 PM UTC

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

  12. monitoring Feb 10, 2026, 08:18 PM UTC

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

  13. resolved Feb 10, 2026, 11:18 PM UTC

    This incident has been resolved.

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 →

Looking to track DNSimple downtime and outages?

Pingoru polls DNSimple's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when DNSimple reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track DNSimple alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring DNSimple for free

5 free monitors · No credit card required