RE: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Schiller, Heather A
See my sig.. Did you try calling your local customer support team? While we do have a 24x7 team that handles DoS attacks, we don't have a 24x7 team that reads every post to nanog ;-) The local support offices have a process to contact us, you should be able to get assistance reasonably quick.

Re: DDOS attack via as702 87.118.210.122

2010-10-26 Thread James Hess
On Tue, Oct 26, 2010 at 9:12 AM, Jack Carrozzo wrote: > Well, I whois'd 702, got no match, said "hm, I see 701 all over the place, > lemmy take a look" and found: There is a match... I think "WHOIS as702" is erroneous WHOIS query syntax, typing "asX" not being the way to search for an A

Re: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Beavis
whois on 702(Verizon) http://www.robtex.com/as/as702.html goodluck. On Tue, Oct 26, 2010 at 5:51 AM, Serg Shubenkov wrote: > > Hello, list. > > Please send me off-list abuse contact for as702. > > -- > Serg Shubenkov, MAcomnet, Internet Dept., Head of Inet Department > phone: +7 495 7969392/907

RE: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Steve Adcock
manual work like a bit of ripe/cidr-report and used network tools for a whois you would get the answer. Cheers Steven -Original Message- From: Cutler James R [mailto:james.cut...@consultant.com] Sent: 26 October 2010 14:54 To: na...@merit.edu Subject: Re: DDOS attack via as702

Re: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Jack Carrozzo
Well, I whois'd 702, got no match, said "hm, I see 701 all over the place, lemmy take a look" and found: ASNumber: 701 - 705 ASName: UUNET etc. Sorry, it was left as an exercise to the reader - didn't mean to be flippant. -Jack CArrozzo On Tue, Oct 26, 2010 at 10:07 AM, Adrian Cha

Re: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Tim Jackson
Whois really isn't that hard Maybe reading: ASNumber: 701 - 705 is though.. t...@shitbox:/var/log$ whois a 702 -h whois.arin.net # # The following results may also be obtained via: # http://whois.arin.net/rest/asns;q=702?showDetails=true # ASNumber: 701 - 705 ASName: UUNET ASHan

Re: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Adrian Chadd
On Tue, Oct 26, 2010, Cutler James R wrote: > Jack, > > I agree that whois is hard. Please explain how you knew to query AS701 when > Serg asked about AS702. Brainfart. I understand why people confuse 701 with 702. $ whois -h whois.ripe.net AS702 % Information related to 'AS702' aut-num:

Re: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Cutler James R
Jack, I agree that whois is hard. Please explain how you knew to query AS701 when Serg asked about AS702. computer:~ me$ whois as702 No match for "AS702". >>> Last update of whois database: Tue, 26 Oct 2010 13:47:47 UTC <<< Regards. Cutler On Oct 26, 2010, at 9:22 AM, Jack Carrozzo

Re: DDOS attack via as702 87.118.210.122

2010-10-26 Thread Jack Carrozzo
Whois is hard, let's go shopping: ja...@anna ~ $ whois as701 # # The following results may also be obtained via: # http://whois.arin.net/rest/asns;q=as701?showDetails=true # ASNumber: 701 - 705 ASName: UUNET ASHandle: AS701 RegDate:1990-08-03 Updated:2008-07-2