Update: 11:29 EST
None of our data centers have reported anything looking like attack traffic, DOS activity or anything other than normal DNS query traffic coming in.
We traced most of the DNS timeouts back to San Jose, which has servers in both the NS1 and NS2 anycast strands, we have removed San Jose from both anycast announcements, which seemed to improve things. We also stopped announcing Amsterdam.
I have noticed that the last few comments to the blog “we’re seeing it too” have all come from England and the UK. We’re now looking at that.
Thanks to all for their datapoints and their patience.
It appears that the issue is only affecting certain nameservers in a few locations. All the servers are fine, but it appears that there may be some network issues affecting not only easyDNS but general network traffic in some areas or across some routes. For the moment, we have removed those servers from the answer-groups, and we believe the problem to be resolved for the time being.
We are continuing to investigate what may be causing these issues, and as yet are not considering it a DOS attack.
Please note that reports from site monitoring services may have given far more negative results than users actually experienced in accessing affected sites.
We apologize for the inconvenience, and will update the blog when we have more information.