Twitter Search API returns strange characters - is it me or is it them?

We are creating an application that accesses Twitter's JSONP lookup.

It mostly works fine, but sometimes the request returns a JSONP callback consisting of weird unpaired characters.

Here's an example: http://search.twitter.com/search.json?result_type=recent&rpp=100&geocode=51.4375857,-0.1658648,1km&page=5&callback=jsonp1272532482854

(If you change page = 5 to a value less than 5 in the url, it works fine)

So

• Am I doing something wrong?

• Can anyone suggest a workaround?

Edit: This is no longer a problem, so I guess it was a bug, fixed.