For me the API behavior is now back again to this morning, with around 2 to 5 rejections per second, and most being successful on the first or second backed-off retry.
Dewald On Aug 11, 6:22 pm, Alex Payne <[email protected]> wrote: > Just found out that our hosting provider put some hardware in place that may > cause disruptions. Our operations team just spoke them, and they should be > taking it down in 15 - 30 minutes. > > > > On Tue, Aug 11, 2009 at 14:03, Andrew Badera <[email protected]> wrote: > > > On Tue, Aug 11, 2009 at 5:01 PM, Andrew Badera<[email protected]> wrote: > > > On Tue, Aug 11, 2009 at 4:57 PM, Alex Payne<[email protected]> wrote: > > >> Yes, I've just been informed that the attack has resumed, and that our > > >> service provider is putting network hardware in place to counter the > > attack. > > >> We're trying to work with them to ensure minimal impact to the API, but > > in > > >> the near term there may be issues with OAuth and the Streaming API. > > >> This is a bit of a juggling act, as we're trying to coordinate our team, > > the > > >> operations team, our service provider's staff, and specialists that > > they've > > >> brought in for this issue. Please bear with us. > > > > Thanks for the update Alex. No worries here, you all seem to be > > > keeping us much more comfortably updated than most of Friday. > > > > --ab > > > *Thursday, not Friday > > -- > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
