Desktop via Comcast, Chicago, local times: -last successful timeline call at 3:50am -one search query got a response, at 7am -no access to web site
Michael D. Ivey wrote: > > Yes. Unable to connect via Tweetie from home (one of my traceroutes > was from home) and lots of reports from iPhone, AT&T and Comcast users > in Southeast. > > Sent from my iPhone > > On Oct 18, 2009, at 9:56 AM, John Kalucki <jkalu...@gmail.com> wrote: > >> >> And here's the next question: >> >> Is anyone having trouble from non-service, non-hosted endpoints. In >> other words, problem from home ISPs and desktop clients? >> >> -John Kalucki >> http://twitter.com/jkalucki >> Services, Twitter Inc. >> >> >> On Oct 18, 7:55 am, John Kalucki <jkalu...@gmail.com> wrote: >>> OK. I think we have enough traceroutes for now. Thanks for sending >>> them in! >>> >>> If we need more datapoints or information, I'll update this thread. >>> >>> On Oct 18, 7:14 am, John Kalucki <jkalu...@gmail.com> wrote: >>> >>>> I don't see any operational issues from here, but I'm not an >>>> operational guy. At first glance the system looks fine, and the >>>> operational team isn't in response mode. This is puzzling. >>> >>>> Seems like a connectivity issue upstream from twitter. At lest a few >>>> developers: please send a traceroute to this list. Also, if you aren't >>>> timing out, but rather are getting an HTTP error, send the response >>>> headers. After say 4 or 5 responses, they'll probably have enough info >>>> to triage this. >>> >>>> -John Kaluckihttp://twitter.com/jkalucki >>>> Services, Twitter Inc. >>> >>>> On Oct 18, 6:40 am, Dewald Pretorius <dpr...@gmail.com> wrote: >>> >>>>> Does anyone else have problems connecting to the API at the moment >>>>> (Sunday morning October 18)? >>> >>>>> Dewald >
