Comment by ben174

Doesn't look like a DNS issue this time. Something specific to Twitter specifically?