FWIW, our application has been experiencing these same issues for
several weeks now. I've seen repeated overcapacity errors being
returned (the "too many tweets" HTML page) on both GET and POST
requests. I don't have specifics on likely times of the day, though US
Central nighttime seems much less likely than weekly business hours.
Our servers are located in Dallas, TX.
Let me know if there's anything else that would be helpful for me to
On May 12, 9:54 am, John Kalucki <j...@twitter.com> wrote:
> It's probably on our end. I'll post some advice.
> On Wed, May 12, 2010 at 12:24 AM, Tjaap <jdmeij...@gmail.com> wrote:
> > John,
> > can you already tell us something about the latency issue?
> > Is it your opinion that the many connect failures I am seeing are
> > something on my end? Or could that be correlated with the timeouts?
> > Thanks,
> > Jaap