POST track request gateway timeout (502)


DISREGARD - Apparently the API console is broken for the streaming API. twurl helped me diagnose the issues on my end.

I work on an application that relies on the streaming API to grab tweets. For the last few days I’ve been unable to get any tweets whatsoever. I am always getting timeout errors and as a result, my production account is getting 420 errors (back off) despite having not been running for some time now. My dev account is getting timeouts both via code and when using the API console. Is the streaming API down or are parts of it malfunctioning?