3 ms·
Official Twitter blog confirming it was a DNS hack: http://status.twitter.com/post/288586541/working-on-site-outage http://status.twitter.com/post/288586541/wor
by tlrobinson 17y ago
Official Twitter blog confirming it was a DNS hack: http://status.twitter.com/post/288586541/working-on-site-outage http://status.twitter.com/post/288586541/working-on-site-out...
Of course, if their DNS was compromised, status.twitter.com could be compromised too...