Those of us that use Twitter like a religion and visit the church of tweeting constantly will have noticed that over the last couple of days there has been some major problems with access, account editing and slowness of the twitter service.
It all started yesterday when the site went down, upon checking the Twitter Status it turns out that Twitter was going through a deniel-of-service attack!
We are defending against a denial-of-service attack, and will update status again shortly.
Update: the site is back up, but we are continuing to defend against and recover from this attack.
Update (9:46a): As we recover, users will experience some longer load times and slowness. This includes timeouts to API clients. We’re working to get back to 100% as quickly as we can.
Update (4:14p): Site latency has continued to improve, however some web requests continue to fail. This means that some people may be unable to post or follow from the website.
Even Tweetdeck was having problems due to the outrage, though TweetDeck is now running again, editing accounts and using Ouath is still sluggish to say the least.
Even TweetLater has an announcement of there website with regards to problems:
IMPORTANT SERVICE ANNOUNCEMENT — PLEASE READ
- To help Twitter in recovering from the Denial-of-Service attack, we have paused all Twitter account automation. In other words, at present no new follower checking is being done, no scheduled tweets are being posted, keyword alerts are paused, etc.
- If you do not want a small avalanche of tweets posted on your Twitter account when service resumes, then please reschedule your tweets now for publishing on Monday or Tuesday (we have no idea how long the Twitter recovery will take).
- Also, you will probably not be able to add a Twitter account or edit your Twitter account at present. It is because the Twitter API is not responding at the moment. The system will tell you your credentials are invalid, but it’s because it couldn’t check them against the API.
- Features such as TweetCockpit, @Mentions & Retweets, DM Manager, Vet Friends/ Followers, etc., are also crippled by the API’s unresponsiveness.
- We will remove this notice message as soon as we get the thumbs up from Twitter that they have fully recovered from the attack and we have resumed normal service.
- Update: We have received word from Twitter that this outage could last well into Saturday.
So for the time been, it’s just a case waiting for the attack to be thwarted by the Twitter techies!
If you enjoyed reading this post, then please remember to post a comment, Subscribe to my RSS feed.
Pingback: Vote on this article at blogengage.com
Thank God I’m still not that twitterholic. I noticed it when I was doing my retweeting rounds and every time the website timed out.
.-= Asswass´s last blog ..Asswass and Hiburrito’s Special Blog Directory =-.
I’m having issues off and on today. Wondering how much longer it can go on, I don’t want anything interfering with my twitter fix
.-= Daily Shot Mike´s last blog ..What I’m Drinking – Colombia – Guiterrez from Paradise Roasters =-.
I was just reading on Twitter Status that they are now also having problems with FireFox 3.5!
This entire Twitter thing just killed some of the things I had planned going into the later part of the week. Im so happy it’s back now.
.-= Extreme John´s last blog ..UFC 101 Review =-.
You’re not kidding, I’ve only just been able to get back on SNODS and been able to use sites with the Twitter Oauth…
Twitter was a victim of a DDOS attack. I can’t understand why it happened to such a big name?
If you check out the Wiki for DoS you can get a good idea of how it was done, it is such a shame though that people do things like this, I mean, come on haven’t they got anything better to do!
Wow….when the twitter thing happened…..and everyone totally freaked….I realized how important this little site has become to business around the country. Wild isn’t it!
.-= Thomas@Atlanta New Cars´s last blog ..The Cadillac CTS-V has Firepower! =-.