Twitter Status

We are working to restore both of these services.

Update: User search has been restored.

We’re investigating a bug that causes improperly sized images for backgrounds and avatars. This should only be affected images uploaded in the last several days.

Update (2:01p): We’ve pushed a fix for the improper image upload problem. This will cause JPG upload problems for some users but resolves the more serious mis-sizing issue. We will do a second update to resolve the JPG issue.

Some T-Mobile users will not be receiving all updates via text due to a problem with our provider. We’ve resolved this issue but users will see some missing updates via SMS.

Due to a DNS error, some users may have problems reaching search.twitter.com. The problem has been corrected and you’ll be able to reach the site as soon as the change propagates through DNS to you.

The site has been sluggish the past couple days, but we’ve been making good progress on some of the more serious bugs.

• We’ve largely resolved the database inconsistency issues that were responsible for a wide range of problems. These include: fluctuating direct message counts and missing updates. Some older updates (from before 3/25) may still not have reappeared. But new updates should no longer be missing.
• Some improvements to follow/unfollow. There are still folks running into problems trying to follow or unfollow users. However, the inconsistencies related to this have improved some and we have more improvements on the way. The biggest issue right now is the latency people encounter when trying to follow; we’re working to resolve that.
• Image uploading for avatars and background images should be much improved
• Users with bounced email addresses can now have us try to send mail again (rather than having to write in). And we’ve resolved a deliverability problem we were having with Hotmail.

There’s still a lot of people running into trouble because of the site slowness. And slowness, itself, is a problem. We’re working hard on these issues and will post more as we make progress.

We’re tracking down a bug that is causing trouble for those using these functions. We’ll re-enable as soon as it’s fixed.

We’ve just released an update that solves some of the slowness issues we’ve been seeing lately. However, more work remains. Here are the top issues we’re still working on:

• Problems with following: Folks are seeing erroneous messages about being “over the follow limit.” Also some changes with following seem not to apply right away or to stall out.
• Missing updates: Some users are seeing missing updates from their timelines because of replication issues. But these updates are not lost … they’re just not being displayed when they should. This is a critical problem and we’re working to improve database performance to address it.
• Photo uploading: Users are still running into some problems uploading JPGs for both avatars and background images.

We’ve got all hands on deck working on these problems and we’ll continue to keep posting updates here about our progress.

Some users will be missing updates from their timeline due to a database issue we’re actively working to resolve. This won’t affect everyone and the updates are not permanently lost. Thanks for being patient as we work this out.

Update (4:40p): We’re making progress on the missing tweets problem. As of right now, updates should be flowing through normally. However, there will be some gaps from earlier in the day which we intend to backfill later. It’s possible we may experience another problem like (where not all updates appear in the timeline for some users). But we’re doing everything we can to address the situation.

We’re seeing lots of reports of “error D1051” from people trying to register a phone on twitter.com. We think this is being passed on from the provider we use to send SMS.

Also, many people are running into problems when trying to upload images for either avatar or background image (PNGs or JPGs under 700kb should be accepted.)

We’re working on both of these critical bugs.

We’re recovering from an unplanned maintenance window and will be back soon.

Update: Actually, it turns out that while we had slowness, we never were down. Sorry (but grateful) for the false alarm.

Users will experience delays of up to 45 minutes in receiving direct messages. Also, some changes to follower/following relationships may be similarly delayed.

This should not affect tweets or timeilnes.

For about an hour earlier tonight, some users would have experienced gaps in their timelines or inconsitencies when trying follow. We will be rebuilding the missing statuses and will also work to correct the discrepancies with follower/following relationships introduced during this time.

Our upstream SMS provider will perform planned maintenance from 10:00 to 10:30 PDT tonight. This maintenance will not affect AT&T and T-Mobile customers; customers of other carriers will not be able to use SMS with Twitter during this period.

We’re currently working with our SMS provider to fix delivery problems with all inbound and outbound SMS. Delivery seems to be returning to normal after an a partial outage that started 45 minutes ago.

Some folks may experience inconsistencies in information seen on Twitter. Specifically, you may see a fluctuation in follower counts, direct messages or other data. We’re working to resolve this.

Due to a problem with our upstream provider (not on the Twitter or Virgin Mobile side), Virgin Mobile text messages were not being delivered correctly. This problem has now been resolved.

We’re seeing a delay of several hours in posting inbound SMS. As a result, updates that you post via text message won’t show up on Twitter right away.

We’ll have a fix out for this shortly. When the fix, is made live older updates will be posted as new. Apologies for the delay.

We’ve fixed the problem folks were having with signing in to Twitter.

Some users are receiving an error while logging in. We are fixing this issue now.

We experienced a brief data center power failure this morning affecting a small number of servers. Site performance was degraded for 5 minutes.