We're looking into reports of unexpected and persistent HTTP 500 response codes to requests on the Twitter REST API.
Applications experiencing this problem are receiving HTTP 500 with error code 131 when making authenticated requests to the API. Some developers have found that all apps owned by their account exhibit the issue while accounts owned by other accounts do not.
Some developers are also reporting issues with HTTP 503 responses when connecting to stream.twitter.com. We are unsure if these are related.
We'll provide updates when we better understand and are working toward resolution on the issue.
Updates
- We believe we've identified and resolved the issue. Please let us know in the forums if you're still experiencing this issue