Locations queries become "Unknown URL"

[smcrawler]

I have streamed geo-tagged tweets for couple of months, using
https://stream.twitter.com/1/statuses/filter.json?locations=-180,-90,180,90

Just this morning I received:
“Unknown URL. See Twitter Streaming API documentation at http://dev.twitter.com/pages/streaming_api”

Meanwhile, querying a word works well, such as
https://stream.twitter.com/1.1/statuses/filter.json?track=money

Anyone experience the same and how you have dealt with? Thanks.

[waleoyediran]

I am currently observing this issue with
userstream.twitter.com:443 /2/user.json

Unknown URL. See Twitter Streaming API documentation at http://dev.twitter.com/pages/streaming_api

[whattheshot]

Same here, my game crashed tonight using phirehose library:

Phirehose: HTTP failure 3 of 20 connecting to stream: HTTP ERROR 404: Not Found (Unknown URL. See Twitter Streaming API documentation at http://dev.twitter.com/pages/streaming_api). Sleeping for 40 seconds.

According to the status page, stream.twitter.com is down but not user streams. Why are we affected?

Thanks.

[whattheshot]

@waleoyediran suggested to change Phirehose to use the User Stream V1.1 instead of V2, and it seems to work. But for how long? Do we need to switch back to V2 when it will be fixed?

[andypiper]

Already responded to your Tweet, but it sounds like you may have missed the recent announcement that those older endpoints are now no longer available (I know that it is confusing that there was a /2/ in the URL, but the current correct URLs all include /1.1/ - this dates from before we had a consistent versioning across our API endpoints).

[waleoyediran]

Thank you @andypiper
It is clear to me now.