Blog Back
‎English (US)‎ ‎English (UK)‎ ‎English (Australia)‎ ‎English (Canada)‎ ‎English (India)‎ ‎日本語‎ ‎Français‎ ‎Português‎ ‎한국어‎ ‎Bahasa Indonesia‎ ‎Español - España‎ ‎Español - América Latina‎ العربيّة ‎English (MENA)‎ ‎English (Southeast Asia)‎
‎English (US)‎ ‎English (UK)‎ ‎English (Australia)‎ ‎English (Canada)‎ ‎English (India)‎ ‎日本語‎ ‎Français‎ ‎Português‎ ‎한국어‎ ‎Bahasa Indonesia‎ ‎Español - España‎ ‎Español - América Latina‎ العربيّة ‎English (MENA)‎ ‎English (Southeast Asia)‎

We had a rough night. But now we're back.

Thursday, 31 January 2008

I just left the office, at 6am, with most of our engineering and technical operations team. That’s only a handful of people, but we were all there all night.

You may have noticed we had an outage last night/stretching into this morning. This was a planned maintenance project, not a surprise happening for us. But we did go far beyond our planned time window, which sucks. What sucks more is the series of outages (planned and not) we’ve had lately. We know this makes Twitter frustrating to use, and we want you to know, we hear (and share) your frustration and are working really, really hard to fix it.

The good news is we finished a major infrastructure project tonight, which we’ve been working on for months and that we think is going to help a lot. I’m sure there will be some glitches in the coming weeks, but we’ve laid some important foundation that’s going to help us build toward the future.

Thank you for your support and patience.

Update (8:30a PT): We’re still experiencing patches of slowness service-wide. Some of our systems are not cleanly restarting. We’re watching closely, bringing things back up manually, and fixing our automation tools accordingly!