Some users have reported the inability to Retweet - we are actively investigating the issue.
Update (1:12p): - We have identified the problem and restored Retweet functionality for all users.
Some users have reported the inability to Retweet - we are actively investigating the issue.
Update (1:12p): - We have identified the problem and restored Retweet functionality for all users.
The “find people” feature is currently disabled while we investigate and fix an issue. We expect to re-enable the feature shortly.
We are actively investigating a critical issue whereby users’ tweets are not being delivered to all of those users’ followers. This issue particularly affects users with a very large number of followers.
Update (6:37p): We have identified several contributing issues and have made improvements. Some tweets continue to be delayed or undelivered, and we are continuing to investigate the issue.
Update (12:00a): We have made further improvements and have substantially corrected the fault. We are monitoring for any further instances of the issue.
We are working to recovery from an unplanned downtime and will update more as we learn the cause of this outage.
Update (11:28p): Twitter’s DNS records were temporarily compromised but have now been fixed. We are looking into the underlying cause and will update with more information soon.
We are aware of and investigating the causes of timeline delays and missing tweets. Retweet is back up and fully functional.
Posting tweets via SMS is currently unavailable. Some tweets are also not being delivered via text (the outbound service). We are actively working on the underlying cause of both problems and hope to restore service soon.
Update (12/14 6:30pm). The issue has been resolved.
Due to latency issues with the Facebook API not all tweets created from our Facebook application will be posted on Twitter.
Update (12/11 3:58p): This has now been resolved.
Some users are seeing tweets (that aren’t retweets) from users they do not follow. We have a Known Issues page with more information and we are working on fixing the underlying cause.
We are working to respond to a disruption in service that started approximately 10 minutes ago.
Update (11:38p): We are now recovering from this interruption.
Update (12:01a): Some users may notice stale timeilnes as we recover.
We briefly experienced a very high rate of errors due to the same underlying problem as yesterday. We are working to permanently resolve this problem.
Starting about 10 minutes ago, we began experiencing a very high rate of errors and we are working on the underlying problem.
Update (3:40): We’ve corrected the problem and the site is returning to normal.