Now the website seems fine.  However, trying to post a status update from my
desktop client (using OAuth, don't know if that makes a difference), it just
hangs when sending the request.  Status updates from twitter.com seem to
work just fine.
Ryan

On Mon, Oct 12, 2009 at 4:19 PM, bear <bea...@gmail.com> wrote:

>
> John,
>
> I'm going to be in San Fran the week of Nov 5th, I would love to meet
> with the Twitter Ops team on how we (we being Seesmic and possibly
> other large consumers of Twitter) can help you guys respond faster to
> these issues.
>
> If there was someone (or thing) to poke I could have given you guys
> early warning more than an hour before you updated the status blog as
> I was seeing a dramatic increase in the error rate trends.
>
> As it stands now all I can do is look at twitter, the IRC channel and
> this and wonder what's going on until someone remembers to update the
> status blog.
>
>
>
> On Oct 12, 3:49 pm, John Kalucki <jkalu...@gmail.com> wrote:
> > We updated the status blog:http://status.twitter.com.
> >
> > On Oct 12, 12:44 pm, Dewald Pretorius <dpr...@gmail.com> wrote:
> >
> > > It's now even on Mashable:
> >
> > >http://mashable.com/2009/10/12/http-server-error-twitter/
> >
> > > On Oct 12, 4:36 pm, ryan alford <ryanalford...@gmail.com> wrote:
> >
> > > > Thanks Dewalt.  I was beginning to think something was wrong with my
> app.
> > > >  Atleast I know I am not the only one seeing these slow downs.
> > > > Ryan
> >
> > > > On Mon, Oct 12, 2009 at 3:26 PM, Dewald Pretorius <dpr...@gmail.com>
> wrote:
> >
> > > > > Their system must just be overloaded at the moment.
> >
> > > > > I have been seeing response times in the 10+ seconds region per
> simple
> > > > > API call since earlier this morning.
> >
> > > > > Dewald
> >
> > > > > On Oct 12, 3:56 pm, RTuosto <ryantuo...@gmail.com> wrote:
> > > > > > I'm getting this error when looking
> athttp://www.twitter.comaswell
> > > > > > as user pages.  Whats the issue?
> >
> >
>

Reply via email to