From 11:22am to 12:16pm PST, users may have experienced issues accessing www.twitter.com. Other services including mobile were not affected.
This issue has now been resolved. We are sorry for any inconvenience.
Between 16:18 - 16:59 PST today, some users may have experienced issues reaching Twitter services.
This issue has now been resolved.
We apologize for any inconvenience.
Between 14:55 - 15:14 PST today, some users may have experienced issues viewing timelines on Twitter’s mobile apps, web, and via the api.
This issue has now been resolved.
We apologize for any inconvenience.
Between 21:02 - 21:20 PST today, some users may have experienced issues viewing timelines on twitter.com and with Twitter’s mobile apps.
This issue has now been resolved.
We apologize for any inconvenience.
[ Update 16:21 PST ]
Between 15:18 and 16:11 PST today, some users were unable to Tweet and received a notice telling them they’ve been locked out.
This issue has now been fully resolved. We apologize for any inconvenience caused by this.
We are aware of an issue where some users are unable to Tweet and have received a notice telling them they’ve been locked out.
Our engineers are currently investigating this issue.
Between 15:07 and 15:28 PDT today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
Traffic was redirected away from the problematic components, and the issue has been resolved.
We apologize for any inconvenience.
Between 16:51 and 18:30 PST today , users experienced a delay in tweets appearing in their timelines. This issue has been fully resolved.
We apologize for any inconvenience caused by this.
[ Update 9:28 PST ]
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.
Between 17:25 and 18:05 PST, some users may have experienced issues sending and viewing tweets on twitter.com and twitter’s mobile apps.
The issue has been stabilized and we apologize for any inconvenience.
Between 12:05 and 12:35pm PT, some users may have experienced issues sending and viewing tweets on twitter.com and Twitter’s mobile apps.
The source of this issue has been identified and we apologize for any inconvenience.
Between 18:49 and 19:23 PDT today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
The source of this issue has been identified, and we apologize for any inconvenience.
Update:
Between 12:41 and 13:09 PDT today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
Traffic was redirected away from the problematic components, and the issue has been resolved.
We apologize for any inconvenience.
Some users may be experiencing issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
Between 14:01 and 14:20 PDT today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
Traffic was redirected away from the components that were experiencing problems, and the issue has now been resolved.
We apologize for any inconvenience.
Between 13:26-14:39 PDT, some users may have experienced a delay in Tweets showing up in their home timelines. This issue has now been resolved. We apologize for the inconvenience
Update: Traffic was redirected away from the components that were experiencing problems, and the issue has been resolved as of 15:27 PDT.
We apologize for any inconvenience.
Some users may be experiencing issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
On 4/7/2014 we were made aware of a critical vulnerability in OpenSSL (CVE-2014-0160), the security library that is widely used across the internet and at Twitter.
We were able to determine that twitter.com and api.twitter.com servers were not affected by this vulnerability.
We are continuing to monitor the situation.
Update [March 26 at 10:55am PDT]: This issue has been resolved, and affected Tweets, along with the favorites and retweets on those Tweets, have been restored.
We are currently researching a bug that has caused some Tweets to not be displayed.
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 19:05 and 19:29 PST today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
Traffic was redirected away from the components that were experiencing problems, and the issue has now been resolved.
We apologize for any inconvenience.
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.
We apologize for the inconvenience.
Between 10:39AM and 10:48AM PST today, some users may have experienced issues viewing and sending Tweets on twitter.com and Twitter’s mobile apps.
This issue has been addressed and we apologize for the inconvenience.
Between 14:02 and 14:16 PST today, some users were not able to load timelines on mobile devices.
This issue has been addressed and we apologize for the inconvenience.
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.]
Update: As of 14:19 PDT, this issues has been resolved.
Due to unexpected issues during a maintenance, some users were not able to get to twitter.com or load mobile timelines from 13:55 until 14:19 PDT. We apologize for the inconvenience.
Some users may be experiencing issues reaching twitter right now.
Our engineers are currently working to resolve this.
Update: This issue has been resolved.
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.
Some web users may be experiencing empty timelines and some users may be experiencing an issue with Twitter on mobile devices. Our engineers are currently working on this issue.
Update: This issue is resolved as of 6:37pm PST.
Update: This issue has been resolved.
Some users may be experiencing an issue when uploading a photo. Our engineers are currently working on this issue.
Update: As of 8:50am PT, this issue has been resolved.
Some users may be experiencing an issue with our service. Our engineers are currently working on this issue.
Some users may have experienced an issue with links contained within Tweets. This issue has been resolved as of 7:10 am PST.
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.
Update: This issue has been resolved as of 5am PST.
Some users may be experiencing an issue with our service. Our engineers are currently working on this issue.
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.
This issue has been resolved.
Update: This issue has been resolved.
Some twitter.com users may be experiencing issues uploading photos from the website.
Our engineers are currently working to resolve the issue.
Update:
We experienced intermittent issues affecting web and mobile users, globally, between approximately 7:00am and 9:50am PST.
This incident has now been resolved. We apologize to users who were affected by this, and we’re working to ensure that similar issues do not occur.
Some users may be experiencing issues accessing Twitter. Our engineers are currently working to resolve the issue.
Update: This incident has been resolved.
Some users may be experiencing issues accessing Twitter.
Our engineers are currently working to resolve the issue.
Update: This incident has been resolved.
Some users are currently experiencing issues with twitter.com and some mobile clients. Our engineers are working on this issue.
Update: This issue has been resolved.
Some users may be experiencing an issue when uploading a photo. Our engineers are currently working on this issue.
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.
Update: This issue is now resolved.
Some users may be experiencing a delay with new tweets in their timelines. Our engineers are currently working on this issue.
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.
As always, we recommend that people review these tips on how to keep their Twitter accounts secure: https://support.twitter.com/articles/76036-keeping-your-account-secure#
Users may be experiencing issues accessing Twitter. Our engineers are currently working to resolve the issue.
This issue has now been resolved.
Some users may currently be unable to upload or update avatar images.
Our engineers are currently working on this issue.
This issue has now been resolved.
Currently, Users are not be able to upload or update avatar or background images. Our engineers are currently working on this issue.
Update: This issue has been resolved.
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: Twitter for iPhone and iPad update is now available to address issue with autocomplete mentions in iOS 6. http://itunes.apple.com/us/app/twitter/id333903271
Update: This issue has been resolved.
Some users may be experiencing duplicate mentions and retweets in their connect tab. Our engineers are currently working on this issue.
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.
Update: This issue has been resolved.
Some users may be experiencing an issue when uploading a profile photo; our engineers are currently working on this issue.