Persistent 503 Error Responses on Stream connects


#1

I’m building an app using the streaming api, and am consistently encountering 503 responses when attempting to open the connection. I am then “backing off” (30 secs, 1 minute, 2, minutes, and finally 4 minutes between reconnection attempts) but am still… after hours… unable to establish a connection and always receiving a 503. Could this possibly be a problem on my end, or should I trust my code and just wait for capcity to improve on the Twitter side of the equation?