We’re still seeing some slowness in various areas of the service. We’ll be making some schema changes to our slave databases tomorrow afternoon to help minimize the issue.
Twitter Status
Month
We’re still seeing some slowness in various areas of the service. We’ll be making some schema changes to our slave databases tomorrow afternoon to help minimize the issue.
Latency has been a problem for a good chunk of today. We’re working on changes now that are meant to improve the situation.
Wanted to provide an update on where we are in restoring services. The partial pagination fix we deployed appears stable. Some folks are still going to be missing Older links but we’re working to restore those.
IM remains offline today but we completed the testing of an important technology fix. Getting IM back for all users remains the top service we need to restore; we’re working on it.
The API limit is still being kept at 30 requests per hour to help us stabilize the service for everyone. Some folks will get “rate limit exceeded” error if you use API clients that request data from us at a higher rate. Please reconfigure them appropriately for the time being.
Most users will be able to paginate through older updates, but you may run into some situations where the Older links are not available. We’re continuing to work on restoring pagination for everyone.
IM is still offline but we are currently testing some fixes that enable the restoration of that service.
Due to excessive database load, we have disabled pagination on the web and IM updates. Also, we’ve lowered the API request limit to 30 requests per hour. We are working to restore.
