Operation timed out after 0 milliseconds, 0 bytes received



Hi Twitter,

Lately we’ve been getting this error a lot: "Operation timed out after 0 milliseconds with 0 out of 0 bytes received."
Note that most of our calls actually complete successfully, and the strange thing is, that we’re getting this error in a somewhat specific timespan: It starts around 13:00:00 GMT +00:00 and ends around 20:00:00 GMT +00:00.

Now I have noticed that we’re also reaching the ratelimit nowadays, but usually we get a nice response telling us the ratelimit is reached. Could these problems be related? And if not, are there any other reasons that could explain this strange behaviour?