Williams , "nanog@nanog.org"
> Subject: RE: Hijacked Network Ranges - paging Cogent and GBLX/L3
> Message-ID:
> <7A848D4888ADA94B8A46A17296740133B38D3E5473@DEXTER.oasis-tech.local>
> Content-Type: text/plain; charset="us-ascii"
>
> I would go
174 12189 19181 33611 i
-Original Message-
From: Ido Szargel [mailto:i...@oasis-tech.net]
Sent: Tuesday, January 31, 2012 3:06 PM
To: Schiller, Heather A; Kelvin Williams; nanog@nanog.org
Subject: RE: Hijacked Network Ranges - paging Cogent and GBLX/L3
I would go at first by advert
I would go at first by advertising your prefixes as a /24 as well, just
randomly checked 2 different locations and the as-path to 11325 is shorter
than to 33611
This seems to be the case for customers of Tiscali and L3, so this will
probably get most of your traffic back to you...
Regards,
Ido
--
Sorry -- was looking at the wrong thing. Doh!
--heather
-Original Message-
From: Schiller, Heather A
Sent: Tuesday, January 31, 2012 3:05 PM
To: 'Keegan Holley'
Cc: Kelvin Williams; nanog@nanog.org
Subject: RE: Hijacked Network Ranges - paging Cogent and GBLX/L3
Looks
Looks fixed now..
--heather
-Original Message-
From: Keegan Holley [mailto:keegan.hol...@sungard.com]
Sent: Tuesday, January 31, 2012 2:50 PM
To: Schiller, Heather A
Cc: Kelvin Williams; nanog@nanog.org
Subject: Re: Hijacked Network Ranges - paging Cogent and GBLX/L3
To be honest I
To be honest I haven't had much success it convincing a tier 1 to
modify someone else's routes on my behalf for whatever reason. I also
have had limited success in getting them to do anything quickly. I'd
first look to modify your advertisements as much as possible to
mitigate the issue and then
Or roll it up hill:
33611 looks like they get transit from 19181, who's only upstream appears to be
12189.
12189 gets connectivity from 174 and 3549.
174 = Cogent
3549 = GBLX/L3
--Heather
-Original Message-
From: Kelvin Williams [mailto:kwilli...@altuscgi.com]
Sent: Tuesday, J
7 matches
Mail list logo
