We’re moving our write enabled Postgres cluster to a new data center. As such we’ve scheduled a one hour maintenance window starting at 8am Pacific time (1500 UTC) on Sunday, June 30. The DNSimple app and API will be unavailable for roughly twenty minutes.
Name service will remain unaffected.
By popular demand, we added a confirmation dialog when trying to delete a record from the advanced editor.
What happened? Several days ago we detected the start of a DNS amplification attack. This attack was nothing special until the morning of June 3rd when it changed in a manner causing an outage for DNSimple name servers. In this type of attack we are one player in a larger game. The attacker wants to…
On May 20th, beginning at about 11:30am Pacific time (18:30 UTC), we experienced a partial service outage. A component failure blocked our customers from updating their DNS records. We apologize for any trouble this caused DNSimple customers. Highlights Detected time: 11:40 PDT Resolved time: 23:43 PDT Severity: All customers wanting to change DNS records. Pros: Our alerting…
We have scheduled a one hour maintenance window beginning at 6pm Pacific time on Wednesday, May 15 (Thursday, May 16, 2013 at 0100 UTC). This will be used to update network routers at each of DNSimple’s data centers to increase overall availability. We expect the DNSimple application and redirection service to each be unavailable for less…
Today we’re officially deprecating our advanced editor v1.
Today we deployed a change to how the Heroku one-click service works. Heroku recently released their European region, and with that change they deprecated the “proxy” subdomain for Heroku apps. To make DNSimple’s one-click service compatible with this change, we now require your Heroku app name, as it appears in your herokuapp.com subdomain. When you…
In order to update several low level components of our software stack we have scheduled a maintenance window beginning Sunday, April 21 at 0400 UTC (Saturday, April 20th at 9PM Pacific time). It will remain open for two hours. We expect the DNSimple application and API to be unavailable for less than twenty minutes. Name service will not…
On Saturday, April 6th, around 7:49 AM UTC NS2 (name server 2) stopped responding to queries. At 10:32 AM UTC, NS3 stopped responding to queries as well. During the outage NS1 and NS4 picked up the additional traffic. This abnormal load caused a portion of ALIAS resolutions to fail — directly affecting DNSimple customers. We…
Modern web applications benefit from fast DNS responses. DNS response times may still add anywhere from 10s to 100s of milliseconds to your applications overall latency. DNS providers are constantly working to reduce lookup times using technology such as caching and the use of BGP protocols. Even web browser makers like Google have joined in…