New
#10
I was a little more drastic, changed my Primary and Secondary DNS to Google servers, (8.8.8.8 & 8.8.4.4), which obviously did the flush too
I suspected a DNS issue as most of the net address space was working, (just Twitter was a visible issue from me and no news of problems at twitter)
I think the targeting of DYN was due to the fact that they hold the primary DNS record for Twitter and a few other major web giants so a relatively minor attack would gain major results
The Net is of course designed to With multi-redundancy so will heal most of these attacks quickly but reliance on a single Main DNS record may need to be looked at by DYN, Twitter or both