You are confusing the Streaming API with the REST API a bit. The Streaming API rate limiting notices [1] for statuses are delivered in the stream and once the limitation period expires the matches will start automatically being delivered again. This generally means your keywords are too generic or common.
If you are getting a response other then 200 check for the coresponding reason on Twitter's list [2].
Comments
You are confusing the Streaming API with the REST API a bit. The Streaming API rate limiting notices [1] for statuses are delivered in the stream and once the limitation period expires the matches will start automatically being delivered again. This generally means your keywords are too generic or common.
If you are getting a response other then 200 check for the coresponding reason on Twitter's list [2].
[1] http://dev.twitter.com/pages/streaming_api_concepts#filter-l... [2] http://dev.twitter.com/pages/streaming_api_response_codes