Also, please be sure to provide packet dumps and full headers where possible so we can more easily determine the source of the issue.
Thanks, Ryan On Tue, Aug 11, 2009 at 2:00 PM, Alex Payne<[email protected]> wrote: > We're aware of these issues; sorry. > Our ops team tells me that the countermeasures that are being put in place > should not cause the 302 redirect behavior that impacted OAuth and other > services late last week. If you're seeing that behavior, please post here > and we'll coordinate with them to eliminate it. > > On Tue, Aug 11, 2009 at 13:58, Sean Callahan <[email protected]> wrote: >> >> Alex, >> >> Did not see this post and posted a new message. Still receiving lots >> of errors and no one can login on our site, tweetphoto.com, right now >> along with a handful of others (that I've tried myself). Just wanted >> to give you a heads up. Thanks! >> >> Sean >> >> On Aug 11, 1:11 pm, Alex Payne <[email protected]> wrote: >> > Our operations staff has informed me that the attack ceased several >> > minutes >> > ago. Site performance should be returning to normal. >> > >> > On Tue, Aug 11, 2009 at 12:23, Alex Payne <[email protected]> wrote: >> > > We're currently experiencing another wave of Distributed Denial of >> > > Service >> > > (DDoS) attacks against our system. Expect periodic slowness and errors >> > > until >> > > the attack passes or is countered by our operations team and hosting >> > > provider. Updates will be provided as we get them. >> > > Thanks for your patience. >> > >> > > -- >> > > Alex Payne - Platform Lead, Twitter, Inc. >> > >http://twitter.com/al3x >> > >> > -- >> > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x > > > > -- > Alex Payne - Platform Lead, Twitter, Inc. > http://twitter.com/al3x >
