Users are seeing an elevated number of errors on twitter.com and we’re working to recover from this problem.
Users are seeing an elevated number of errors on twitter.com and we’re working to recover from this problem.
We pushed out a change today that disabled the feature which keeps you logged in when you close your browser. It will be available again shortly.
We have been experiencing increasing latency over the past week that is affecting both twitter.com and the Twitter API. We have identified some potential solutions and are working to resolve the issue.
We identified and resolved a bug that permitted a user to “force” other users to follow them. We’re now working to rollback all abuse of the bug that took place. Follower/following numbers are currently at 0; we’re aware and this too should shortly be resolved.
Update (10:18 AM PST): Of note: protected updates did not become public as a result of this bug.
Update (2:42 PM PST): We’re continuing work on rolling back abuse of the bug; in the meantime, if there’s folks you’re following that you didn’t choose to follow, you can block them or unfollow them.
Update (6:30 PM PST): We’ve finished our cleanup of the spurious followings generated a result of this bug. If you are still seeing folks you are following who you didn’t choose to follow, please use the block or unfollow tools to remedy.
As of 5:18 UTC (10:18pm PDT) Twitter became largely unavailable. We’re investigating.
UPDATE: 5:40 UTC (10:40pm PDT) Site recovering, but still slow. Timeline processing is delayed.
UPDATE: 6:05 UTC (11:05pm PDT) Site is generally available and timeline processing for most users has been current throughout this incident. Users returning to the site after a long absence, and a small random fraction of all users, may not have a timeline available for display. No tweets have been lost and all timelines should eventually display correctly.
UPDATE: 6:30 UTC (11:30pm PDT) All timelines should now display correctly.