I'm getting between 3 and 10 502's per second, with an added bonus of
about 1 connection refused per second.

Over-worked and under-staffed. That's how I would diagnose the
symptoms, such as our complaining about bad system performance and
poor communication. One human being can only do so much and then the
rest of the tasks land on the floor.


On Oct 21, 1:08 pm, Andrew Badera <and...@badera.us> wrote:
> What's there to talk about? What can we do? As always we're at
> Twitter's mercy and the status blog is 3 days out of date.
> I've definitely been seeing them too. Not horrible today, but a pretty
> steady stream really since mid-last week I believe.
> ∞ Andy Badera
> ∞ +1 518-641-1280
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me:http://www.google.com/search?q=andrew%20badera
> On Wed, Oct 21, 2009 at 12:05 PM, RandyC <bioscienceupda...@gmail.com> wrote:
> > I have been seeing enormous numbers of 502's and 500's for API calls
> > from Qwest DSL business, Rackspace, and Amazon Cloud instances since
> > Saturday through today.  Working through the UI to log into accounts
> > is equally painful with constant fail whales after two to three
> > attempts.  Seems like a couple of bad hair days so far and very
> > difficult to get much done.  I'm surprised more people aren't talking
> > about this unless we're the only ones affected.

Reply via email to