Update: Sun Aug 1 05:31 UTC 2010
Twitter’s hosting provider, NTT America, will begin scheduled maintenance at 11:00PM PT/06:00AM UTC. This maintenance will last approximately five hours.
During this maintenance, there will be periods of time when some users are unable to use Twitter. We do not expect these periods will last for the entire maintenance window.
We’re currently working on remedying the issue blocking users from updating their profiles.
Update Sat Jul 31 21:05 UTC 2010: Users may experience an elevated rate of errors.
Update Sat Jul 31 22:05 UTC 2010: Users can now update their profiles. Issues related to edits to user profiles, auth-tokens, signups, api and mobile clients, avatar and profile images are now resolved.
Twitter’s hosting provider, NTT America, is upgrading a portion of our internal network starting July 31 at 11PM Pacific. ( August 1 at 600 UTC)
This maintenance will last approximately five hours. During this time, there may be intermittent periods when some users are unable to use Twitter.
During these intermittent periods you will see the maintenance page — as pictured above — which will link to our status blog where you can read the latest updates on the progress of the maintenance.
The Twitter API is returning an elevated level of errors. Engineers are working to address the problem.
Update Fri Jul 30 15:25 UTC: The problem has been resolved.
We’re looking into expired SSL certificate errors now and working quickly to resolve it. The problem affects a small portion of TweetDeck API requests.
Update (11:05 PST, 18:05 UTC): We believe this issue has been resolved.
We’re looking into expired SSL certificate errors now and working quickly to resolve it. The problem affects a small portion of TweetDeck API requests.
We’ve temporarily disabled avatar upload as we do some work; we’ll update again when it’s reenabled.
Update (18:10 PST, 01:10 UTC): Avatar uploading is reenabled.
In a related issue (that is also being worked on), our help center is currently down; we’re working to bring it back up.
Update (15:30 PST, 22:30 UTC): The Help Center is back up.
We’re currently working on remedying the issue blocking users from updating their profiles.
Update (11:20 PST, 18:20 UTC): oAuth tokens are also affected by this; we continue to work to resolve the issue.
Update (12:30 PST, 19:30 UTC): Signups are currently disabled as we recover from this issue.
Update (14:00 PST, 21:00 UTC): API and mobile clients are currently experiencing some issues; we’re working on remedying this issue.
Update (22:00 PST, 05:00 UTC): Issues with API, mobile, oAuth tokens, and users updating their profiles continue; we continue to work to remedy the situation. Signups remain disabled for the time being.
Update (23:45 PST, 06:45 UTC): API issues, oAuth tokens, and signups are restored to normalcy. User edits and mobile continue to experience issues.
Update (00:38 PST, 07:38 UTC): Avatar and background image upload are disabled, as are user settings; we will be continuing work on recovering from this throughout the night and will update again in the morning.
Update (12:30 PST, 19:30 UTC): We are fully recovered.
It’s a known issue that is now resolved. All followings and unfollowings are now real-time and up to date.
We are aware of an SSL issue on our API and are in the process of fixing it. This issue does not pose a threat to account security.
Update (10:40 AM PST, 17:40 UTC): This issue has been resolved.
Many users are receiving incorrect “Rate Limit Exceeded” errors through the Twitter API. We are investigating the cause and will update when it is resolved.
Update (7/14/10 4:15 PM PST, 23:15 UTC): This issue has been fixed but we are running tests to ensure that there are no further problems. Please contact the Twitter Support team if you are continue to receive erroneous rate limit error messages: http://bit.ly/twicket
We’re hearing reports from developers that they’re running into some incorrect rate limits; we’re looking into it.
Some users are experiencing an issue in which they’re not receiving all of their @ replies; we’re working on a fix.
We’re working to resolve an issue with the mobile website, http://mobile.twitter.com.
UPDATE: Resolved at 15:31 UTC / 8:31 PDT.
We’ve received reports of elevated error rates for users; we’re currently investigating.
Update (9:47 AM PST, 16:47 UTC): This is unplanned downtime. Infrastructure and operations engineers are working to fully restore Twitter. Expect more updates soon.
Update (9:55 AM PST, 16:55 UTC): We are now recovering from a period of high unavailability.
We are experiencing an issue temporarily with the intermediary SSL certificate for the API; we expect the issue to be resolved shortly. In the meantime, you may experience issues using the API; we’re working to resolve the issue now.
Update (8:22 AM PST, 15:22 UTC): This issue is resolved.
