System Status
All Systems Operational
Website Operational
API Operational
Sandbox API ? Operational
Name Servers Operational
Redirector Operational
Support Site Operational
Zone deployment Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Past Incidents
May 30, 2016
Completed - We have been able to complete maintenace works in our sandbox environment. If you have any questions please write us to our support address.
May 30, 10:16 UTC
Update - We are going to extend the maintenance time for another hour as we debug an ongoing issue with one of the components of the database.
May 30, 09:42 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 30, 08:00 UTC
Scheduled - We are going to deploy several components in our database system that introduces better performance and higher availability in the Sandbox environment. Website and API access will be disabled and return HTTP 503 status codes until service is restored. Please contact support if you have any questions.
May 26, 15:06 UTC
May 29, 2016

No incidents reported.

May 28, 2016

No incidents reported.

May 27, 2016

No incidents reported.

May 26, 2016

No incidents reported.

May 25, 2016

No incidents reported.

May 24, 2016
Resolved - DNS service in the Asia/Pacific Region should be restored, if you notice any issues please email support@dnsimple.com so we can investigate.
May 24, 03:02 UTC
Identified - Our upstream provider is currently working on a networking issue in the Asia/Pacific region and working to resolve the issue as quickly as possible. DNS resolution will be intermittent or unreachable until this issue is resolved.
May 24, 02:34 UTC
Resolved - Chicago is fully synchronized and operational. As always, please report any issues at support@dnsimple.com so we can investigate them quickly. Thank you again for your patience.
May 24, 02:29 UTC
Monitoring - The server is back online and processing DNS updates quickly. As a precaution mentioned earlier, we're going to synchronize the Chicago nameservers to make sure they're up to date with the latest DNS changes.
May 24, 02:24 UTC
Identified - We are re-installing the zone distribution services in Chicago which should be completed within the hour. DNS changes will be delayed until the system comes back online and begins to process the changes. We'll synchronize our DNS servers in the region once the system comes back online as well. Thank you for your patience.
May 24, 01:11 UTC
May 23, 2016

No incidents reported.

May 22, 2016

No incidents reported.

May 21, 2016
Resolved - Everything seems to have returned to normal operation and as a precaution we are re-synchronizing the name servers across the globe. As always, if you notice any issues please email support@dnsimple.com
May 21, 05:09 UTC
Monitoring - The affected server is now back online and zone updates are going out to Chicago. We're going to keep an eye on things and sound the all clear soon. If you are experiencing issues sending DNS updates to Chicago, please email support@dnsimple.com so we can investigate.
May 21, 04:13 UTC
Identified - We've experienced a hardware issue in one of our systems in Chicago that distributes DNS updates and are working to restore it as quickly as possible. Zone updates will be queued and delayed until the system comes back online.
May 21, 03:13 UTC
May 20, 2016

No incidents reported.

May 19, 2016

No incidents reported.

May 18, 2016

No incidents reported.

May 17, 2016
Resolved - Our upstream provider has resolved the routing issues in Buenos Aires. If you are still experiencing DNS resolution issues in the South America region, please email support@dnsimple.com so we can investigate. Thank you again for your patience.
May 17, 22:40 UTC
Identified - Our upstream provider has confirmed there is a routing issue happening in the Buenos Aires region and are actively trying to resolve the issue. If you are still experiencing DNS resolution issues in the South America region please email support@dnsimple.com with dig and traceroute information indicated in earlier updates.
May 17, 21:48 UTC
Update - We have received word from our upstream provider that they are continuing to investigate the issue. Please keep us updated with any of the information we've mentioned previously as it could help resolve things more swiftly.
May 17, 20:52 UTC
Update - We are still investigating reported DNS resolution errors in some South American locations. We are awaiting confirmation from our upstream network provider to determine if this is a routing issue, which is what we suspect. If you are unable to resolve a name from your location in South America, please email the result of `dig @162.159.24.4 yourdomain` and `traceroute 162.159.24.4` to support@dnsimple.com. Thank you for your patience.
May 17, 19:52 UTC
Investigating - We're getting reports from customers being unable to reach dnsimple.com and our name servers in the South America region. We are talking with our upstream provider to investigate further and will update you as soon as we know any information. If you are experiencing an outage in this region, please email support@dnsimple.com with a trace route to ns1.dnsimple.com and dnsimple.com so we can pass it on to our provider.
May 17, 19:18 UTC
Resolved - All the DNS changes have synchronized and everything has returned to normal. If you are experiencing any issues sending updates to this region specifically, please email support@dnsimple.com to get help.
May 17, 20:03 UTC
Monitoring - The system that was affected has been fixed and has rebooted. DNS changes queued for this region are catching up as quickly as possible and we will keep a close eye on the name servers in this region.
May 17, 19:47 UTC
Identified - We're experiencing issues with sending out DNS changes to our Ashburn, VA data center due to a down server with a hardware issue. We are waiting on work from our hosting provider to help get the system back online. Changes sent to this region will continue to queue and will process as soon as the system comes back online and the region synchronizes with the rest of the data centers.
May 17, 19:10 UTC
May 16, 2016

No incidents reported.