<< Back to the main Twitter Blog page

Wednesday, May 14, 2008

What Happened Today?

It is not entirely to do with the Democrats, Space Aliens, Mysterious Men in Black, or Arugula. In fact, this afternoon's service interruption does not have a very exciting explanation.

Part of our caching service required an unscheduled restart. That means a slow rebuilding of data. You may notice some of the normal browsing related features (such as pagination) are missing while we repopulate the caching service. This is so we can get it done quicker.

Update: It's not Groundhog Day but it sure feels like it. We are recovering today from the same problem as yesterday. This service interruption is our own fault. If you have questions that are only satisfied by technical answers please join our technical discussion forum on Google groups.

25 Comments:

Anonymous jared said...

awww shucks , get well soon we need you... sending you love xxx we all need a rest sometimes...

5/14/08 6:05 PM  
Blogger KathyJ said...

Is this why the Replies tab also isn't working right now?

5/14/08 6:06 PM  
Blogger Carlene said...

hurry! i need to twitter!!! im addicted!!! hahaha jk...kinda. :P heh

5/14/08 6:20 PM  
Anonymous kaourika said...

Caching? Pah. A likely excuse. THIS IS OBVIOUSLY A VAST CONSPIRACY TO FACILITATE THE NINJA TAKEOVER >:O

Thanks for working on it, guys :D

5/14/08 6:29 PM  
Blogger Luke said...

Outrage! I couldn't tweet for like hours earlier. :P

5/14/08 6:30 PM  
Anonymous Stilgherrian said...

"Part of our caching service required an unscheduled restart"? Bah! Please don't retreat into vague corporate non-explanations! Your user base includes some of the planet's leading alpha geeks, and you'd build more trust if you were clearer — and communicated more frequently during outages.

Tell us WHY it required a restart. Was it overload from the China earthquake, as some have speculated? General overload that you'll fix by date X? Software failure? Human dumbness? Marauding cabbages?

5/14/08 6:35 PM  
Blogger Nedra Weinreich said...

Phew - I was starting to get shaky. :-)

You might like this:

You know you spend too much time on Twitter when...

@Nedra

5/14/08 6:36 PM  
Blogger ...e... said...

geez, i thought i broke it! whew!

5/14/08 6:48 PM  
Blogger Robert said...

I never realized how big Twitter was until things like this happen: http://www.flickr.com/photos/sandieman/2493787902/in/photostream/

5/14/08 6:52 PM  
Anonymous Katie Fellows said...

Ah. Makes perfect sense. But, then again, so do the space aliens...

5/14/08 7:10 PM  
Blogger SEMcents.com said...

What about faries

5/14/08 7:13 PM  
Anonymous Levi Figueira said...

I understand these things happen, but you guys have either been really unlucky with your availability or there are some fundamental mistakes in the framework you're basing your app on...

I won't enter the whole RoR discussion because I'm no guru, but I certainly know that some other high traffic services are handling caching and other things a lot better! Heck, even on PHP (Facebook)...

I really wish you the best of luck! I love the service and I'm certainly not one to go ranting about it negatively, but: please make the changes you need to make now to make it more available. And in the process, make your API available through XMPP/Jabber so that apps like Twitterific and others can get stuff "live" :P (of course this implies that the availability/speed issues get resolved... ;))

5/14/08 8:17 PM  
Anonymous Justin said...

twitter doesn't work at all for me anymore, the site won't even load... :(

5/15/08 1:52 PM  
Blogger warza said...

Yet again twitter demonstrates just how badly it's run. If only the community wasn't big enough for us to have to put up with this rubbish service. Remember there's the boycott to demonstrate our dis-satisfaction.

http://jerseysuburbia.com/?p=30

I've twittered over 26,000 times, I'm patient. Fix the service.

I want an alternative.

5/15/08 2:09 PM  
Anonymous openAllNight said...

5/15/08, 5:10pm ET, Web site will not load again today. Feed the katz.

5/15/08 2:18 PM  
Anonymous Anonymous said...

Yet again, the twit is down.

5/15/08 2:53 PM  
Blogger Remco Kouwenhoven said...

5/15/2008, 23:55 (Central European Time) no connection... :-(

Friendfeed is becoming more and more an attractive alternative....

5/15/08 2:54 PM  
Blogger John said...

May the force be with you!

5/15/08 2:54 PM  
Blogger garth said...

When the service goes down—again—without any mention on the official blog, I begin to doubt Twitter has any commitment to me or the community.

I'm more outraged by the lack of candor than by the lack of uptime.

I'm sure you know about the problem. Could you also spend a minute telling us you know about it? We don't need much detail. 140 characters will do.

5/15/08 3:17 PM  
Blogger Jason Goldman said...

@garth we've just updated this post to include a pointer to our technical forum where additional information about the problem is available.

5/15/08 3:23 PM  
Anonymous Stilgherrian said...

@jason goldman: Even that technical forum is scant on usable detail. I don't need network engineering specifics -- that's your problem -- but I do need information which will allow me to give informed advice to clients, colleagues and friends.

Those folks rely on me and other geeks to translate all this geekery into something they can use to make important decisions -- such as whether they can rely on Twitter to use it as the basis for some business process, or whether it's to flaky.

Right now, my advice is that Twitter has the potential to be a huge part of the Internet, but they're having real problem coping with their own growth. There have been growing pains, which they need to sort out.

However for two days in a row now they've been completely unusable just as we in Sydney are starting our working day -- supposed for the same reason each day. I don't know what the problem is (they haven't given enough information to tell whether they're spinning BS or not), and they haven't given any real explanation of when it'll be fixed permanently.

Right now, Twitter is ripe for replacement by someone with a similar product (clone the API) but with better engineering.

5/15/08 4:31 PM  
Anonymous Anonymous said...

@Stilgherrian: Think you're find people aren't in a hurry to clone twitter because it's another web2.0 very-popular-but-no-revenue-model thing.

If you're even considering basing anything you'd offer to clients on a 3rd party website you have no control over, I seriously pity your clients. You remind me of all those people crying when Skype went down for 2 days, at least they have a leg to stand on because they were paying customers.

5/16/08 3:24 PM  
Blogger war59312 said...

Twitter is down again. :(

5/20/08 1:20 AM  
Anonymous Example Name said...

interesante

5/20/08 11:29 AM  
Anonymous sha said...

hrwV @ India are really frustrated.What happened to India short code 5566511?

5/22/08 10:14 AM  

Post a Comment

Links to this post:

Create a Link

<< Home