We are currently experiencing a temporary site outage. While the easyDNS interface cannot be reached, this should not in any way affect our DNS or Mail services. For approximately 15 minutes this afternoon, our website was inaccessible. This was in no way related to any of our core services, and we do not expect that […]
Resolved
[RESOLVED] Sporadic web control panel access
Between 4am-7am EST, some users may have experienced sporadic access to the easyDNS web control panel. We identified the issue and brought up the warm-spare for the easyDNS web control panel while we implemented corrective action upon the master instance. Normal services have since been restored, and we have rotated our warm-spare with the latest snapshot. […]
[RESOLVED] Web control panel unreachable
At about 10:35am the web interface for the new platform became unreachable due to the problem with the Xen server holding the VM instance. Remote hands are looking into it while the rest of the systems group are working on why the warm-spares are currently pretty frigid. DNS services, URL and email forwarding, easyMail are […]
Post-Mortem of the Jan-07 DDoS Attack
On Saturday, Jan 07 commencing at approximately 3:30pm EST (almost the exact moment I hit “publish” on a post about Save The Elephants, which we’ll repost later) we were hit with a multi-faceted DDoS Attack across three anycast constellations: dns1, dns2 and dns3. The attack was a combination SYN, ICMP and DNS Flood, in excess […]
Minor issue with easyMail webmail [resolved]
Some customers may have recently experienced errors while attempting to relay email via the easyMail webmail interface. These issues were unfortunately due to an internal routing error which we have since identified and resolved. We have also taken corrective action to ensure that this will not happen again. This was a specific issue related to […]
Intermittent resolution issues with NS2/DNS2 [resolved]
Some customers may have experienced intermittent resolution issues with our “ns2.easydns.com” / “dns2.easydns.com” Anycast nameserver cluster. We have identified a specific node within that Anycast cluster as the cause, and are working with our upstream provider to have it removed. We apologize for the inconvenience. [ UPDATE – 2011-12-15 @ 5:58pm ] We have received […]
