Site streams listener read timeouts



Getting read timeout errors from site streams listener and 503 errors reporting overloaded twitter servers. This has been going on for at least an hour now. API status reports streams operating normally.

Did I miss an api change for site streams?


We’ve certainly had a little bit of API instability today - although I would have expected the API status page to pick that up. We’re sorry for any inconvenience, this should be returning to normal. If that’s not that case, feel free to contact the site streams support email address that you should be aware of.


The issue appears to have been resolved. Thank you for the reply


You can keep an eye on service status via the API status page and the status blog.