You might have noticed that since the last 6 (or 8?) hours “Tweet Activity” have been giving that error. I got some time on my hands to waste and i googled for it, came up that its a pretty common error observed by a lot of users yet there were no official statements regarding what could it be. To verify that i can still resolve twitter from our server and that i haven’t gone over ther API Hits limit i created a check-twitter.php with the following code: <?php echo gethostbyname('twitter.com'); ?> Accessed it via Chrome and came out just fine. More >