Jamie Reidy “totally tried” to Tweet about this.
The Twitter outage began at 11:59 a.m. ET, according to Twitter’s page on tracking site Pingdom. Service returned intermittently around 1 p.m., but less than an hour later, Twitter crashed again.
Twitter updated its status blog at 1:42 saying “the issue has been resolved and all services are currently operational” — but at 2:16, another update from Twitter backtracked and said “the issue is on-going.”
hour later, Twitter seemed to be working for most users. Shortly after 3 p.m. ET, Twitter’s PR account tweeted that the issue was caused by “a cascaded bug in one of our infrastructure components.”
Who was to blame?
A hacker group, UGNazi, claimed to several media outlets that it had taken Twitter down in a distributed denial-of-service (DDoS) attack.
GMP readers, what did you do to survive without Twitter???