I'd be more than happy to wait longer for snazzy API 2.0 features so that the Platform team can build a QoS system that monitors the API's availability and performance from the outside. That will enable Twitter to catch these kinds of issues long before we do.
Dewald On Oct 18, 12:47 pm, Michael Steuer <[email protected]> wrote: > This outage is now going on 7 hours. Any word from Twitter as to an > ETA for resolution? > > On Oct 18, 2009, at 8:08 AM, John Meyer <[email protected]> wrote: > > > > > John Kalucki 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. > > > Yep. (comcast, cannot access through either the website or desktop > > clients).
