twitter

Right now, Twitter is suffering slowdowns. Earlier today it was down again. :(

There are an excessive number of single points of failure in the current system, and through developer error* and external circumstance we have managed to hit quite a few of them in the last week. I am sorry and embarrassed.

In particular, we mis-estimated the impact of some cache policy changes. If your site runs so hot that it can’t function without memcached, you’d better understand exactly how much buffer capacity you actually have.

We’re working on fixing it all, but it takes a long time…

* I ain’t sayin’ it was me, but I ain’t sayin’ it wasn’t.

This entry was written by evan, posted on May 21, 2008 at 12:00 AM, filed under Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post. Both comments and trackbacks are currently closed.

5 Comments

  1. Rob Sanheim
    Posted May 22, 2008 at 6:06 AM | Permalink

    Thanks for the note. Twitter definitely could use more transparency as you guys work through issues, so its good to see posts like this.

  2. evan
    Posted May 22, 2008 at 8:38 AM | Permalink

    Yeah, I agree re. transparency.

    There have been some awesome solutions proposed on the official blog about how to fix it:

  3. Chris
    Posted May 22, 2008 at 9:33 AM | Permalink

    I want to leave a blogger comment here, too.

  4. evan
    Posted May 22, 2008 at 12:01 PM | Permalink

    Chris: You can, but it has to be HUGE and UNUSUAL.

  5. Alex Leverington
    Posted May 22, 2008 at 4:03 PM | Permalink

    @evan

    Your humor is encouraging :)

    Feel free to email me about the post I made to the mailing list. I know it was ambiguous (on purpose).

Follow

Get every new post delivered to your Inbox.

Join 66 other followers