Our mail forwarding system (not to be confused with our mailout system) is experiencing delays with relaying mail to @verizon.net . We have contacted Verizon and they have advised the issue to be cleared, however they have not provided a time line as to when mail will flow without restriction. We will continue to monitor […]
status
[RESOLVED] Mailout Slowness
Our mailout system is experiencing slower than usual mail delivery times . We have isolated and corrected the issue causing the slowness and the mail queue is slowly – but surely – being processed. [ UPDATE – 2012-03-26 @ 3:39pm EST ] All mail has been dequeued at this point, and we’re back to normal […]
Small DNS flood to our nameservers
Yesterday afternoon we were alerted of a domain upon our system that was known within DNS provider circles for excessive traffic, and attempted to have this issue dealt with before it became a problem. Unfortunately, while the domain was delegated to us for only a short time, we did see some spikes in traffic during […]
[Resolved] Sporadic connectivity to dns2.easydns.net
We have had reports of sporadic DNS connectivity to “dns2.easydns.net” from various customers. We have confirmed this and alerted our upstream provider. They believe this is a routing issue, and are escalating this on their end with their networking team. We apologise for the inconvenience, and hope to have this resolved as soon as possible. […]
DDoS attack – mitigation in progress [RESOLVED]
We have detected a DDoS attack in progress. We are alerting our upstream providers and mitigation procedures are going into effect. Our apologies in advance if we take a little more time to answer emails and such than we might otherwise This blog post will be updated as we get more information. –update 15:41 EST […]
Temporary Site Outage [Resolved]
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 […]
