Yes, this issue was resolved. Additionally, we put a higher-capacity firewall in place since that network event.
On Thu, Nov 6, 2008 at 12:02 AM, twibble <[EMAIL PROTECTED]> wrote: > > Alex, > > is this issue fully resolved? Right now I cannot connect to > twitter.com any more from certain hosts. It works from others. The > host in question is api.twibble.de (80.83.114.92) which used to work > fine over the last months. > curl http://twitter.com > curl: (7) couldn't connect to host > > Thanks, > Thilo > > On Oct 28, 7:01 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> We're noticing highnetworklatency and timeouts on twitter.com today, >> which some of you are probably noticing in your apps. The problem >> doesn't appear to be within our cluster, and we're working with our >> service provider to sort it out. We'll be tracking the issue >> onhttp://status.twitter.com/. >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
