We're getting problems on the iPhone clients again, it looks like the old 200 error might have cropped up again of serving HTML instead of XML too.
On Oct 18, 4:10 pm, Michael Steuer <[email protected]> wrote: > I only have two endpoints to test from. Hosted: fails. Home DSL: no > problem. I have several iPhone clients, but I'm bot sure if they're > proxies or connect to the API directly... > > On Oct 18, 2009, at 7:56 AM, John Kalucki <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> wrote: > > >>>> Does anyone else have problems connecting to the API at the moment > >>>> (Sunday morning October 18)? > > >>>> Dewald
