October 2009
14 posts
Update on SMS and Direct Message email bugs
We are pushing additional fixes for the issue reported yesterday regarding missing email notifications for Direct Messages. We believe this should fully resolve the delivery issue.
We are still working on a number of inconsistencies with the SMS service. This includes the inability to remove or add a phone and unresponsiveness to commands sent over SMS. This is being treated with highest priority...
Lists test is being temporarily disabled
Those who are in the test group for lists will temporarily see the feature disabled as we make some changes.
Update (8:13p): This has been re-enabled.
Not receiving emails for Direct Messages
Users have the option of receiving email notification for Direct Messages. However, not all of these emails are being sent. We are investigating the source of this bug.
Update (3:03): We believe this issue has now been resolved and we are testing the fix.
SMS problems still being worked on
Last night we posted about some ongoing SMS problems. An emergency fix we did last night appeared to address many of the symptoms but we still have problems with SMS commands not being accepted.
We are continuing to work on this.
SMS problems being worked on
We are currently working on problems affecting the SMS service for Twitter. Users will notice that Twitter is not responding correctly to commands sent over the SMS service. Also, users are unable to start using the SMS service by adding their device on the web or sending START to the SMS short code.
These are urgent problems and we are working to correct them.
Update (9:35p): These problems...
Expanding Lists feature to 5 percent
We are expanding availability of Lists to 5 percent of users and will work our way up to a full roll-out in the coming weeks.
Elevated error rate being worked on
For the past several hours, we’ve been contending with a high rate of errors on twitter.com. This problem is being caused by over-consumption of resources on our webservers due to several changes we’ve made in the past few days. These changes are necessary for the future growth of the product. As a result we are working through the inefficiencies in the system in order to decrease the...
Responding to network connectivity problems
We are currently investigating a problem whereby some Twitter clients in widely scattered network locations are unable to connect to twitter.com.
Update (Sunday 1:36pm PDT): Network should be back to normal now. We are investigating the cause of the outage and will update this with more information when we know more
Lists Beta Released to More Users
To further test our beta Lists feature, we’ve introduced it to a larger group of users.
Timelines currently 30 minutes behind
Timelines are currently lagging by 30 minutes. We are working on this issue and things should be back to normal soon.
Researching username, password change problems
We’re currently researching reports from users who are locked out after trying to reset their passwords or change their email address or user names. This seems to affect new users as well as long term users; we do not advise changing your user name, email address, or password at this time. We will update Status with more news as it becomes available.
Update (Thursday 3:58pm):...
Responding to increased errors, inability to tweet
We’re looking into the cause of the 500 errors that are being seen by users on twitter.com. We’re also working on the posting problems that many people are running into when trying to create tweets.
Update (Tuesday 3:43pm) We’re still looking into tweet creation problems. Specifically, reports of erroneous error messages and/or no error message, but inability to post tweets....
Timeline delays this morning
We are currently investigating a problem causing many users’ timelines to be delayed. We will update with status here shortly.
Update (10:50a): Timelines remain stale for users. We are deploying fixes to address the problem.
Update (12:27p): This issue has been resolved and timelines are updating normally once again.
Update (12:54p): The problems this morning were caused by a bug...
Recovering from unplanned downtime
We’re currently diagnosing the causes of an unplanned site outage that happened a few minutes ago. We are recovering from this issue now and apologize for the interruption in service.