I'm seeing that as well. Guessing is the caches slowly warming up? On Fri, May 8, 2009 at 4:11 PM, Eric Blair <[email protected]> wrote:
> > Another maintenance-related question - are things completely back up and > running? I'm asking because I'm seeing inconsistent behavior. > > In my servers logs, I'm seeing a number of timeouts when talking to > Twitter. Also, when I try to run curl commands from my servers to Twitter, > they are _extremely_ slow, sometimes timing out. Some of my servers are > systems that regularly communicate with Twitter while others rarely do so. > > However, when I run the same curl command from my desktop, it runs in a > snap. > > I don't recall seeing anything like this in the past, where there would be > such a consistent difference between the two environments. > > --Eric > > > On May 8, 2009, at 6:41 PM, Doug Williams wrote: > > Eric, >> I was right next to Alex when he made the fix for Issue 300 and I remember >> seeing it deployed. I'll check into it. >> >> >> Thanks, >> Doug >> >> ---------------------------------------------------------------- >> Doug Williams | Platform Support | Twitter, Inc. >> >> 539 Bryant St. Suite 402, San Francisco, CA 94107 >> http://twitter.com/dougw >> >> >> >> On Fri, May 8, 2009 at 3:38 PM, Eric Blair <[email protected]> >> wrote: >> >> Yeah, I filed 300 a while ago and it was marked as fixed, so I was >> surprised when I saw HTML. >> >> --Eric >> >> >> On May 8, 2009, at 6:08 PM, Doug Williams wrote: >> >> The issues tell the story: >> >> >> http://code.google.com/p/twitter-api/issues/list?can=1&q=maintenance&colspec=ID+Stars+Type+Status+Priority+Owner+Summary+Opened+Modified+Component&cells=tiles >> >> Thanks, >> Doug >> -- >> >> Doug Williams >> Twitter Platform Support >> http://twitter.com/dougw >> >> >> >> >> On Fri, May 8, 2009 at 2:46 PM, Eric Blair <[email protected]> >> wrote: >> >> Any reason the API is serving up an HTML page instead of the normal error >> XML? >> >> --Eric >> >> >> On May 8, 2009, at 1:50 PM, Michael Bailey wrote: >> >> Thanks for the clarification Doug. Stock up on some RedBull and best of >> luck for a smooth upgrade to the team! >> Michael Bailey >> >> >> >> Doug Williams wrote: >> >> @Michael: Yes. The OAuth server makes use of the twitter.com web servers >> as well as the database backing store which is the focus of the maintenance. >> >> Thanks, >> Doug >> -- >> >> Doug Williams >> Twitter Platform Support >> http://twitter.com/dougw >> >> >> >> >> On Fri, May 8, 2009 at 10:00 AM, Michael Bailey <[email protected]> >> wrote: >> Which includes OAuth verification functionalities, yes? >> Michael Bailey >> Thought Leader and Serial Entrepreneur >> "Cultivating the landscape of the online multimedia community" >> Blog: http://www.mobasoft.com >> New Service: http://mobatalk.com >> >> >> >> >> Doug Williams wrote: >> >> Hi all. >> >> To clarify: the site will be down. twitter.com and search.twitter.comwill >> fail to serve content while the back end changes are being made. >> >> Thanks, >> Doug >> -- >> >> Doug Williams >> Twitter Platform Support >> http://twitter.com/dougw >> >> >> >> >> On Fri, May 8, 2009 at 7:31 AM, Nick Arnett <[email protected]> >> wrote: >> >> >> On Thu, May 7, 2009 at 10:33 PM, Abraham Williams <[email protected]> >> wrote: >> That is usually what "site maintenance" means... >> >> In my experience, a maintenance window means that the site could be down >> for any or all of that period. The way Doug wrote it, I'd imagine that they >> expect the site will only be down for a short time, but they're reserving an >> hour in case it takes longer for unanticipated reasons. >> >> We shall see... >> >> Nick >> >> >> >> >> >> >> > -- “When nothing seems to help, I go look at a stonecutter hammering away at his rock perhaps a hundred times without as much as a crack showing in it. Yet at the hundred and first blow it will split in two, and I know it was not that blow that did it, but all that had gone before.” — Jacob Riis
