Update on latency (fixed) 3 years ago

Monday and Tuesday of this week we have had connection problems to twitter.com between 0730 and 1400 PDT. Some users were seeing timeouts in their browsers on a regular basis through these periods.

We discovered the source of problem this evening and have fixed it.

For the technically inclined: It had to do with a limit set in our load balancer. We crossed a threshold of traffic that caused it to use up the connection pool available to it. The problem was, it was failing without throwing the usual error, due to a bug. We now know about that bug (as does our hosting partner), so it shouldn’t happen again.