All, Much appreciated for the support. Below are a few sites which we're having reachabliity issues to. If you operate one of these networks please check that you can see our allocated blocks and can trace to the following addresses: Allocated blocks: 99.224.0.0/12 99.240.0.0/13 99.248.0.0/14 99.252.0.0/16 99.253.128.0/19 /32's for traces: 99.245.135.129 99.246.224.1 99.244.192.1 lavalife.com AS 15290 Youtube.com AS 36561 Google.com AS 15169 RTSConsulting.com AS 7252 chatsuites.com AS 11595 www.cnn.com AS 1668 www.homedepot.ca Akaimai www.bia2music.com AS 3561 Nbc.ca AS 3848 Costco.ca AS 11283 WWW.ACANAC.C AS 33139 www.cnnsi.com AS 5662 skysport.com AS 4355 CBS.SPORTSLINE.COM AS 6641 www.liveworld.com AS 19148 ebay.com AS 11643 www.nascar.com AS 5662 www.zep.com AS 27584 Thanks in advance, -David -----Original Message----- From: Daniel J. Frasnelli [mailto:daniel.frasnelli@verizonbusiness.com] Sent: Monday, April 23, 2007 11:02 AM To: David Lemon Subject: RE: IP Block 99/8 David, Appears to be correct in our configurations and it passes my "traceroute inside AS701" test. Let me know if the problem appears to be with our public networks (701/702/703) and I'll route the issue appropriately. VR, Daniel J. Frasnelli <daniel.frasnelli@verizonbusiness.com> 22001 Loudoun County Parkway Ashburn, VA 20147 (+001) 703.886.5632 - office (+001) 571.594.7397 - mobile Verizon Business - Network & Information Security % traceroute -n 99.246.224.1 traceroute to 99.246.224.1 (99.246.224.1), 30 hops max, 40 byte packets [snip] 3 207.18.173.189 0.799 ms 0.500 ms 0.636 ms 4 152.63.34.166 0.734 ms 0.960 ms 0.569 ms 5 152.63.40.49 3.092 ms 3.454 ms 3.217 ms 6 152.63.38.117 3.018 ms 2.947 ms 3.160 ms 7 64.125.13.89 5.075 ms 4.826 ms 4.832 ms 8 64.125.30.113 4.956 ms 4.948 ms 5.027 ms 9 216.200.56.2 27.961 ms 28.020 ms 27.879 ms 10 66.185.80.189 27.939 ms 27.960 ms 27.851 ms 11 66.185.80.42 22.859 ms 22.784 ms 23.111 ms 12 66.185.81.62 26.379 ms 26.702 ms 26.643 ms 13 66.185.81.85 28.074 ms 28.094 ms 28.023 ms 14 64.71.241.70 28.087 ms 27.892 ms 28.068 ms 15 66.185.90.251 25.769 ms^C % traceroute -n 99.245.135.129 traceroute to 99.245.135.129 (99.245.135.129), 30 hops max, 40 byte packets [snip] 3 207.18.173.189 0.490 ms 0.439 ms 0.704 ms 4 152.63.34.158 0.818 ms 0.701 ms 0.572 ms 5 152.63.40.49 2.984 ms 3.129 ms 3.200 ms 6 152.63.38.117 3.097 ms 3.125 ms 2.873 ms 7 64.125.13.89 4.866 ms 5.290 ms 5.157 ms 8 64.125.30.113 4.963 ms 5.012 ms 4.828 ms 9 216.200.56.2 27.969 ms 28.070 ms 27.862 ms 10 66.185.80.189 27.888 ms 27.827 ms 28.085 ms 11 66.185.83.117 28.453 ms 28.340 ms 28.620 ms 12 66.185.83.94 25.472 ms 25.646 ms 25.479 ms 13 66.185.90.100 29.384 ms^C % traceroute -n 99.244.192.1 traceroute to 99.244.192.1 (99.244.192.1), 30 hops max, 40 byte packets [snip] 3 207.18.173.189 0.470 ms 0.568 ms 0.571 ms 4 152.63.34.158 0.868 ms 0.764 ms 0.835 ms 5 152.63.40.49 3.032 ms 3.320 ms 3.333 ms 6 152.63.38.117 3.138 ms 2.924 ms 3.070 ms 7 64.125.13.85 4.851 ms 5.212 ms 52.033 ms 8 64.125.30.113 4.772 ms 4.761 ms 4.833 ms 9 216.200.56.2 27.941 ms 27.758 ms 27.963 ms 10 66.185.80.189 27.947 ms 27.771 ms 27.708 ms 11 66.185.81.214 28.246 ms 28.157 ms 28.088 ms 12 24.153.4.230 28.118 ms 28.216 ms 29.882 ms 13 66.185.90.212 29.041 ms^C On Mon, 2007-04-23 at 13:42 +0000, David Lemon wrote:

All,

My name is David Lemon, and I work within the same group as Shai. We're still in dire need of assistance from this list as we still have

many complaints from residential customers that cannot reach certain sites. Shai has provided a few /32's from blocks that we have currently started to provision. Unfortunately we cannot swap these blocks for different blocks with ARIN.

As you can see we do indeed own these blocks:

whois 99.245.135.129 [whois.arin.net]

OrgName: Rogers Cable Communications Inc. OrgID: RCC-99 Address: One Mount Pleasant City: Toronto StateProv: ON PostalCode: M4Y-2Y5 Country: CA

NetRange: 99.224.0.0 - 99.253.159.255 CIDR: 99.224.0.0/12, 99.240.0.0/13, 99.248.0.0/14, 99.252.0.0/16, 99.253.0.0/17, 99.253.128.0/19 NetName: ROGERS-CAB-99

We also have these blocks within RADB as well:

whois -h whois.radb.net 99.240.0.0/13 [whois.radb.net] route: 99.240.0.0/13 descr: ROGERS-13-BLOCK origin: AS812 notify: radb-notify@rogers.wave.ca mnt-by: MAINT-AS812 changed: radb-maint@rogers.wave.ca 20070412 source: RADB

etc..

If anyone has any questions, or I can provide any additional information which anyone may require, please feel free to email me directly or call our TAC @ 416.935.5700.

Thanks in advance for your support,

-David

-----Original Message----- Sent: Friday, April 20, 2007 14:38 PM To: 'nanog@merit.edu' Subject: IP Block 99/8

We recently started to assign these blocks. So all the ranges are not assigned yet. Following are some...

99.245.135.129 99.246.224.1 99.244.192.1

-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Frank Bulk Sent: Friday, April 20, 2007 2:14 PM To: nanog@merit.edu Subject: RE: IP Block 99/8

Please provide a pingable IP address on each block so that we can check.

Thanks,

Frank

-----Original Message----- Sent: Friday, April 20, 2007 1:09 PM To: 'nanog@merit.edu' Subject: IP Block 99/8

Hi,

I am Shai from Rogers Cable Inc. ISP in Canada. We have IP block 99.x.x.x assigned to our customers. Which happened to be bogons block in the past and was given to ARIN in Oct 2006. As we have recently started using this block, we are getting complaints from our customers

who are unable to surf some web sites. After investigation we found that there are still some prefix lists/acls blocks this IP block.

We own the following blocks:

99.224.0.0/12 99.240.0.0/13 99.248.0.0/14 99.252.0.0/16 99.253.128.0/19

Please update your bogons list.

Shai.

end