We are seeing this behavior across the Twitter accounts of multiple customers. Unfortunately it does not seem to be reproducible upon demand - subsequent calls with the same parameters return proper JSON.
The typical behavior is that the JSON will be prefixed by one or two seemingly random ASCII characters and then the JSON will cut off mid stanza.