Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Dnsimple outage history

    54 recorded Dnsimple incidents since April 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Sandbox Environment – Intermittent Downtime During Hosting Provider Maintenance

    Started October 16, 2026 at 7:06 PM UTC · 11h 4m

    Pending
    Affected components
    Sandbox WebsiteSandbox API
    1. October 16, 2026 at 7:06 PM UTCinvestigating

      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 minutes of downtime, and more than one interruption may occur while the rollout continues. Production environments are not affected. No action is needed on your part. If a request fails, please retry after a few minutes. Data in the sandbox is not expected to be lost. We are tracking the provider’s progress and will post an update when maintenance is complete and the sandbox is stable.

    2. October 16, 2026 at 7:22 PM UTCmonitoring

      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. October 17, 2026 at 6:10 AM UTCresolved

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

    Edge network disruption in Warsaw EU region

    Started September 6, 2026 at 1:10 PM UTC · 2h 45m

    IssuesMinor incident
    Affected components
    Name Servers
    1. September 6, 2026 at 1:10 PM UTCinvestigating

      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. September 6, 2026 at 3:55 PM UTCresolved

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

    Degraded service in London region

    Started August 8, 2026 at 12:27 AM UTC · 5h 26m

    IssuesMinor incident
    Affected components
    Name Servers
    1. August 8, 2026 at 12:27 AM UTCinvestigating

      We are currently investigating this issue.

    2. August 8, 2026 at 12:28 AM UTCinvestigating

      We are continuing to investigate this issue.

    3. August 8, 2026 at 2:47 AM UTCidentified

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

    4. August 8, 2026 at 5:14 AM UTCmonitoring

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

    5. August 8, 2026 at 5:53 AM UTCresolved

      This incident has been resolved.

    500 errors on production website

    Started July 23, 2026 at 2:02 PM UTC · 43m

    OutageMajor incident
    Affected components
    WebsiteZone deployment
    1. July 23, 2026 at 2:02 PM UTCinvestigating

      We are currently investigating this issue.

    2. July 23, 2026 at 2:10 PM UTCmonitoring

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

    3. July 23, 2026 at 2:46 PM UTCresolved

      This incident has been resolved.

    Intermittent network failures in SYD/TKO region

    Started June 5, 2026 at 3:34 PM UTC · 4m

    IssuesMinor incident
    Affected components
    Name Servers
    1. June 5, 2026 at 3:34 PM 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. June 5, 2026 at 3:38 PM UTCresolved

      This incident has been resolved.

    Degraded service in Amsterdam region

    Started May 22, 2026 at 10:44 AM UTC · 11h 34m

    IssuesMinor incident
    Affected components
    Name Servers
    1. May 22, 2026 at 10:44 AM UTCinvestigating

      We are currently investigating this issue.

    2. May 22, 2026 at 1:35 PM UTCidentified

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

    3. May 22, 2026 at 6:46 PM UTCmonitoring

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

    4. May 22, 2026 at 10:18 PM UTCresolved

      This incident has been resolved.

    Degraded service in Amsterdam region

    Started May 18, 2026 at 9:26 PM UTC · 34m

    IssuesMinor incident
    Affected components
    Name Servers
    1. May 18, 2026 at 9:26 PM UTCinvestigating

      We are currently investigating this issue.

    2. May 18, 2026 at 9:42 PM UTCmonitoring

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

    3. May 18, 2026 at 10:00 PM UTCresolved

      This incident has been resolved.

    Intermittent network failures in Sydney region

    Started May 8, 2026 at 5:18 AM UTC · 4h 43m

    IssuesMinor incident
    Affected components
    Name Servers
    1. May 8, 2026 at 5:18 AM UTCinvestigating

      We are investigating intermittent network failures in the Sydney region.

    2. May 8, 2026 at 5:41 AM UTCinvestigating

      We are continuing to investigate this issue.

    3. May 8, 2026 at 5:42 AM UTCmonitoring

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

    4. May 8, 2026 at 8:33 AM UTCmonitoring

      We are continuing to monitor for any further issues.

    5. May 8, 2026 at 10:00 AM UTCresolved

      This incident has been resolved.

    dnsimple.com availability issues

    Started April 20, 2026 at 7:54 PM UTC · 1h 50m

    IssuesMinor incident
    Affected components
    WebhooksURL RedirectorWebsiteNotificationsAPI
    1. April 20, 2026 at 7:54 PM UTCinvestigating

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

    2. April 20, 2026 at 8:07 PM UTCinvestigating

      We are continuing to investigate this issue.

    3. April 20, 2026 at 8:21 PM UTCidentified

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

    4. April 20, 2026 at 8:43 PM UTCmonitoring

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

    5. April 20, 2026 at 9:44 PM UTCresolved

      This incident has been resolved.

    Delay in Zone Updates

    Started March 5, 2026 at 10:14 AM UTC · 2h 32m

    IssuesMinor incident
    Affected components
    Zone deploymentSecondary DNSNotifications
    1. March 5, 2026 at 10:14 AM UTCinvestigating

      We are currently investigating this issue.

    2. March 5, 2026 at 10:28 AM UTCidentified

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

    3. March 5, 2026 at 11:15 AM UTCidentified

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

    4. March 5, 2026 at 11:59 AM UTCmonitoring

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

    5. March 5, 2026 at 12:46 PM UTCresolved

      This incident has been resolved.

    Intermittent network failures in FRA region

    Started March 2, 2026 at 6:47 PM UTC · 3h 12m

    IssuesMinor incident
    Affected components
    Name Servers
    1. March 2, 2026 at 6:47 PM UTCinvestigating

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

    2. March 2, 2026 at 7:05 PM UTCidentified

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

    3. March 2, 2026 at 7:29 PM UTCmonitoring

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

    4. March 2, 2026 at 10:00 PM UTCresolved

      This incident has been resolved.

    Intermittent DNS Resolution for Certain ALIAS Records

    Started February 18, 2026 at 2:24 PM UTC · 1h 42m

    IssuesMinor incident
    Affected components
    Name Servers
    1. February 18, 2026 at 2:24 PM 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. February 18, 2026 at 4:07 PM 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.

    Infrastructure Instability

    Started February 10, 2026 at 5:06 PM UTC · 6h 12m

    OutageMajor incident
    Affected components
    Sandbox APIURL RedirectorZone deploymentAPIName Servers
    1. February 10, 2026 at 5:06 PM 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. February 10, 2026 at 5:30 PM UTCinvestigating

      We are running restores to bring back services online

    3. February 10, 2026 at 5:45 PM UTCidentified

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

    4. February 10, 2026 at 6:06 PM 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. February 10, 2026 at 6:32 PM 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. February 10, 2026 at 6:50 PM UTCidentified

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

    7. February 10, 2026 at 7:18 PM UTCidentified

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

    8. February 10, 2026 at 7:21 PM UTCidentified

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

    9. February 10, 2026 at 7:27 PM UTCidentified

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

    10. February 10, 2026 at 7:38 PM UTCidentified

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

    11. February 10, 2026 at 7:51 PM UTCidentified

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

    12. February 10, 2026 at 8:18 PM UTCmonitoring

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

    13. February 10, 2026 at 11:18 PM UTCresolved

      This incident has been resolved.

    Delay in Zone Updates

    Started February 3, 2026 at 11:15 PM UTC · 1h 14m

    OutageMajor incident
    Affected components
    Zone deployment
    1. February 3, 2026 at 11:15 PM UTCinvestigating

      We are currently investigating this issue.

    2. February 4, 2026 at 12:28 AM UTCinvestigating

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

    3. February 4, 2026 at 12:29 AM UTCresolved

      This incident has been resolved.

    Intermittent network failures in AMS region

    Started February 3, 2026 at 7:55 PM UTC · 3h 46m

    IssuesMinor incident
    Affected components
    Name Servers
    1. February 3, 2026 at 7:55 PM UTCinvestigating

      We are investigating intermittent network failures in AMS region.

    2. February 3, 2026 at 8:44 PM UTCmonitoring

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

    3. February 3, 2026 at 11:41 PM UTCresolved

      This incident has been resolved.

    Cache edge degraded performance

    Started January 29, 2026 at 4:52 PM UTC · 1h 6m

    IssuesMinor incident
    Affected components
    Name Servers
    1. January 29, 2026 at 4:52 PM 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. January 29, 2026 at 5:20 PM UTCmonitoring

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

    3. January 29, 2026 at 5:58 PM UTCresolved

      This incident has been resolved.

    Elevated error rates in zone.vision

    Started January 22, 2026 at 7:29 AM UTC · 1h 12m

    IssuesMinor incident
    Affected components
    WebsiteAPI
    1. January 22, 2026 at 7:29 AM 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. January 22, 2026 at 8:41 AM UTCresolved

      This incident has been resolved.

    Cache edge degraded performance

    Started December 30, 2025 at 7:03 PM UTC · 1h 52m

    IssuesMinor incident
    Affected components
    Name Servers
    1. December 30, 2025 at 7:03 PM 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. December 30, 2025 at 7:44 PM 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. December 30, 2025 at 8:55 PM UTCresolved

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

    Network Performance Issues

    Started December 16, 2025 at 1:06 AM UTC · 1h 0m

    IssuesMinor incident
    Affected components
    Name Servers
    1. December 16, 2025 at 1:06 AM 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. December 16, 2025 at 1:23 AM 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. December 16, 2025 at 1:49 AM UTCmonitoring

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

    4. December 16, 2025 at 2:06 AM UTCresolved

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

    Intermittent DNS resolution failures

    Started December 11, 2025 at 9:53 PM UTC · 1h 18m

    IssuesMinor incident
    Affected components
    Name Servers
    1. December 11, 2025 at 9:53 PM UTCinvestigating

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

    2. December 11, 2025 at 10:14 PM UTCmonitoring

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

    3. December 11, 2025 at 10:14 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    4. December 11, 2025 at 11:11 PM UTCresolved

      This incident has been resolved.