Streaming API 420 error

228 views

Skip to first unread message

Josiah Carlson

unread,

Apr 22, 2011, 4:23:53 AM4/22/11

to twitter-deve...@googlegroups.com

Hello,

We've been using some of the streaming API (specifically /statuses/filter.json and occasionally /statuses/sample.json), and recently I have noticed that we are seeing only 420 errors from our auth tokens for all of our dev, staging, and prod applications. Two sets of those auth tokens are never used for streaming unless I run them manually, sometimes with an hour between tests.

status.twitter.com says that there *was* a streaming error, but it was resolved. Anyone else having issues?

Thank you,

- Josiah

Josiah Carlson

unread,

Apr 22, 2011, 11:36:43 AM4/22/11

to twitter-deve...@googlegroups.com

A small update...

After letting it rest over night, I was able to get /statuses/filter.json to work on my office machine using any set of keys, but attempting to run with any keys on ec2 gets us a 420. Immediately after the 420 in ec2, I can run without issue in the office. I've tried a few of our different hosts in ec2, but they all seem to get a 420 error.