Can a Customer take their IP's with them? (Court says yes!)
Owen DeLong
owen at delong.com
Tue Jun 29 22:51:18 UTC 2004
OK... I'll take the risk here...
These guys look to be gross address polluters -- Here's what I found:
1. Pegasus Web Technologies is listed as AS25653 (ARIN whois)
2. route-views.oregon-ix.net has the following to say about prefixes
with origin in AS25653 (only the first listed path is shown for each
prefix):
route-views.oregon-ix.net>$ quote-regexp "_25653$" | include ^...[0-9]
*> 64.21.40.0/24 209.123.12.51 0 8001 25653 i
*> 64.247.26.0/24 209.123.12.51 0 8001 25653 i
*> 64.247.27.0/24 209.123.12.51 0 8001 25653 i
*> 64.247.30.0/24 209.123.12.51 0 8001 25653 i
*> 64.247.31.0/24 209.123.12.51 0 8001 25653 i
*> 64.247.34.0/24 209.123.12.51 0 8001 25653 i
*> 64.247.35.0/24 209.123.12.51 0 8001 25653 i
*> 64.247.47.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.3.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.28.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.32.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.33.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.35.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.36.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.37.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.38.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.39.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.40.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.41.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.42.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.43.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.44.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.49.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.50.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.51.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.52.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.53.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.54.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.55.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.60.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.62.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.63.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.64.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.65.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.74.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.75.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.76.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.77.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.78.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.85.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.86.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.87.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.88.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.89.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.97.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.98.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.106.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.107.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.108.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.109.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.110.0/24 209.123.12.51 0 8001 25653 i
*> 66.246.111.0/24 209.123.12.51 0 8001 25653 i
* 69.9.165.0/24 216.218.252.152 0 6939 4436
29791 25653 i
* 69.57.160.0/19 216.218.252.152 0 6939 8001
25653 i
* 69.72.128.0/18 216.218.252.152 0 6939 8001
25653 i
* 69.72.192.0/19 216.218.252.152 0 6939 8001
25653 i
* 69.72.224.0/19 216.218.252.152 0 6939 8001
25653 i
*> 207.99.34.0 209.123.12.51 0 8001 25653 i
*> 207.99.104.0 209.123.12.51 0 8001 25653 i
*> 207.99.126.0 209.123.12.51 0 8001 25653 i
*> 209.123.49.0 209.123.12.51 0 8001 25653 i
*> 209.123.61.0 209.123.12.51 0 8001 25653 i
*> 209.123.73.0 209.123.12.51 0 8001 25653 i
*> 209.123.134.0 209.123.12.51 0 8001 25653 i
*> 209.123.184.0 209.123.12.51 0 8001 25653 i
*> 209.123.246.0 209.123.12.51 0 8001 25653 i
*> 209.123.247.0 209.123.12.51 0 8001 25653 i
* 209.123.252.0/22 193.0.0.56 0 3333 6320 8001
25653 i
* 216.67.224.0/19 216.218.252.152 0 6939 8001
25653 i
*> 216.118.123.0 209.123.12.51 0 8001 25653 i
Of those, the following prefixes appear to have non-NAC transit paths:
69.9.165.0/24
And the following are not exclusively "8001 25653"
69.72.128.0/18
69.72.192.0/19
69.72.224.0/19
216.67.224.0/19
I am not encouraging anyone to take any specific action WRT these prefixes,
and, I have not been asked or encouraged directly or indirectly by Alex
Rubenstein or any other NAC employee to post this. In fact, I have not
been contacted by anyone from NAC other than Alex's original pre-TRO
post. I have done this research of my own choosing based on other posts
from the community and am posting the results purely for informational
purposes.
Owen
More information about the NANOG
mailing list