Between 4:00pm and 9:25pm PST today some users were unable to sign in to twitter. This issue was due to a bug in our front end code, which has been patched. We apologize for any inconvenience caused by this.
Update [12:12pm PDT]: During a planned deploy in one of our core services, we experienced unexpected complications that made Twitter unavailable for many users starting at 11:01am. We rolled back the change as soon as we identified the issue and began a controlled recovery to ensure stability of other parts of the service. The site was fully recovered by 11:47am PDT. We apologize for the inconvenience.
Most users are experiencing issues accessing Twitter on web and mobile apps. We’re looking into it.
Between 13:19 and 13:37 PST today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps. This was due to an issue with our caching layer in one region.
Traffic was redirected away from the problematic components, and the issue has now been resolved.
For about 5 minutes, from 13:36-13:41, users experienced issues viewing timelines on twitter.com. The issue also affected the ability to get new Tweets on mobile clients. This was due to a code-related error, which was quickly rolled back. We apologize for the inconvenience.
Some users may experience issues trying to access twitter.com. Access to Twitter on mobile apps is not affected.
Update: As of 14:19 PDT, this issue has been resolved. Due to a code-related error, a series of web servers went down from 13:48-14:19 PDT, making the twitter.com website inaccessible for some users. We apologize for any inconvenience.
At 20:49 UTC, our DNS registrar experienced an issue in which it appears DNS records for various organizations were modified, including one of Twitter’s domains used for image serving, twimg.com. Viewing of images and photos was sporadically impacted. By 22:29 UTC, the original domain record for twimg.com was restored. No Twitter user information was affected by this incident.
[UPDATE, 8/28/13: Post updated to reflect that the issue was with our DNS registrar, not our DNS provider.]
Due to an error in a routine change, Twitter was not available from 1:08pm PDT to 1:33pm PDT. We rolled back the erroneous change as soon as we identified the issue. Additionally, some users may have experienced Tweet delivery delay from 1:33pm PDT and 1:53pm PDT. We apologize for the inconvenience.
Some users may be experiencing issues accessing Twitter. Our engineers are currently working to resolve the issue.
We are temporarily turning off API v1 later today, Wednesday, March 20th, for one hour — approximately 3-4 pm PDT (10-11 pm GMT). **Only third-party applications that have not yet transitioned over to API v1.1, the new version of the API, will be affected.** If you’re using one of those apps during this one-hour window, you’ll experience a service disruption. Thank you for your patience during this test.
This blackout test is one of several that will take place in the weeks leading up to retiring API v1. We’re doing this to help developers understand the impact that retirement will have on their applications and services. This post has more information; you can also follow @twitterapi for updates.
Earlier today, some users experienced a bug on twitter.com. While scrolling through another user’s profile, it falsely appeared to the viewer that the user had retweeted a Tweet that the viewer hadn’t actually sent.
Update: Dec 9, 3:10pm PST Instagram has disabled photo integration with Twitter. As a result, photos are no longer appearing in Tweets or user photo galleries.
While tweeting links to Instagram photos is still possible, you can no longer view the photos on Twitter, as was previously the case.
Users are experiencing issues with viewing Instagram photos on Twitter. Issues include cropped images. This is due to Instagram disabling its Twitter cards integration, and as a result, photos are being displayed using a pre-cards experience. So, when users click on Tweets with an Instagram link, photos appear cropped.
We’re committed to keeping Twitter a safe and open community. As part of that commitment, in instances when we believe an account may have been compromised, we reset the password and send an email letting the account owner know this has happened along with information about creating a new password. This is a routine part of our processes to protect our users.
In this case, we unintentionally reset passwords of a larger number of accounts, beyond those that we believed to have been compromised. We apologize for any inconvenience or confusion this may have caused.
We’ve identified an issue with autocompleted mentions on Twitter for iPhone and iPad versions 5.0 and 5.0.1 running on iOS 6. When you compose a tweet with an autocompleted mention at the end of the tweet, the correct username is not included when the tweet is sent. For example: if you type ’@e’ and you select ’@elephant’ from the autocomplete suggestions list, the tweet composer will show ’@elephant’, but the delivered tweet will show as ’@e.’ Since this only occurs when the @username is at the end of the tweet, you can work around this issue by adding additional text after the @username. We are working to fix this issue as soon as possible. Our apologies for the inconvenience, including to users who are receiving unintended mentions due to this bug.
Update: A bug with profile photos and background images affected a very small percentage of users. This has now been resolved. No accounts or user information were compromised. We apologize for any confusion and the inconvenience.
We have temporarily disabled profile settings changes for all users. Our apologies for the inconvenience.