how-to block ads
|
|
Uniqs:
717 |
Share Topic
 |
 |
|
|
|
 DigitalXeronThere is a lack of sanity
join:2003-12-17
Hamilton, ON
2 edits | All of Cogeco's eggs in few baskets?Hi,
I have noticed via traceroutes that Cogeco's network seems to take US-destined routes (that aren't routed via a TorIX-connected network) via two providers: Cogent or Bell.
I find this rather alarming as it essentially leaves Cogeco's network up to be at the mercy of either Bell or Cogent. For a network as large as Cogeco, I'd urge Cogeco to peer with more networks that can carry US traffic.
Taking a few non-TorIX well known websites for instance:
yahoo.com:
cplexus# traceroute yahoo.com
traceroute to yahoo.com (98.139.180.149), 30 hops max, 60 byte packets
1 border.unimatrix01.digibase.ca (72.38.129.201) 2.564 ms 2.647 ms 2.898 ms
2 10.64.172.1 (10.64.172.1) 11.750 ms 12.512 ms 14.880 ms
3 d226-5-225.home.cgocable.net (24.226.5.225) 16.226 ms 17.192 ms 20.437 ms
4 67.69.228.101 (67.69.228.101) 21.237 ms 23.933 ms 24.889 ms
5 bx1-ashburn_xe0-1-0.net.bell.ca (64.230.185.138) 41.766 ms 42.832 ms 42.694 ms
6 Yahoo-Peering.net.bell.ca (64.230.185.130) 42.544 ms 42.633 ms 43.122 ms
7 ae-6.pat1.dce.yahoo.com (216.115.102.172) 46.742 ms ae-6.pat2.dcp.yahoo.com (216.115.102.178) 38.394 ms ae-6.pat1.dce.yahoo.com (216.115.102.172) 37.406 ms
8 ae-6.pat1.che.yahoo.com (216.115.96.81) 57.682 ms ae-2-d181.pat2.da3.yahoo.com (216.115.104.115) 50.314 ms 35.495 ms
9 ae-5.pat1.bfz.yahoo.com (216.115.96.65) 54.703 ms ae-2.pat2.bfz.yahoo.com (216.115.100.74) 53.237 ms ae-0.pat2.nyc.yahoo.com (216.115.100.93) 36.193 ms
10 ae-3.msr2.bf1.yahoo.com (216.115.100.31) 45.028 ms ge-0-0-0.pat2.bfz.yahoo.com (216.115.97.209) 64.266 ms ae-5.pat1.bfz.yahoo.com (216.115.96.65) 42.136 ms
11 ae-3.msr2.bf1.yahoo.com (216.115.100.31) 48.112 ms ae-3.msr1.bf1.yahoo.com (216.115.100.29) 59.248 ms ae-4.msr1.bf1.yahoo.com (216.115.100.25) 64.326 ms
12 et-18-25.fab3-1-gdc.bf1.yahoo.com (98.139.128.57) 48.834 ms et-18-25.fab7-1-gdc.bf1.yahoo.com (98.139.128.65) 61.497 ms xe-8-0-0.clr1-a-gdc.bf1.yahoo.com (98.139.232.89) 55.976 ms
13 et-17-1.fab1-1-gdc.bf1.yahoo.com (98.139.128.37) 53.581 ms et-17-1.fab4-1-gdc.bf1.yahoo.com (98.139.128.43) 57.905 ms et-18-25.fab3-1-gdc.bf1.yahoo.com (98.139.128.57) 53.435 ms
14 po-12.bas2-7-prd.bf1.yahoo.com (98.139.129.195) 56.701 ms po-13.bas1-7-prd.bf1.yahoo.com (98.139.129.209) 64.882 ms po-11.bas2-7-prd.bf1.yahoo.com (98.139.129.179) 69.477 ms
15 * * *
Bell route taken.
slashdot.org:
cplexus# traceroute slashdot.org
traceroute to slashdot.org (216.34.181.45), 30 hops max, 60 byte packets
1 border.unimatrix01.digibase.ca (72.38.129.201) 2.216 ms 2.352 ms 2.609 ms
2 10.64.172.1 (10.64.172.1) 6.155 ms 10.183 ms 12.443 ms
3 d226-5-233.home.cgocable.net (24.226.5.233) 19.480 ms 20.388 ms 20.407 ms
4 38.122.17.9 (38.122.17.9) 23.785 ms 23.820 ms 23.801 ms
5 te3-7.ccr01.buf02.atlas.cogentco.com (154.54.82.101) 15.868 ms 16.795 ms 16.851 ms
6 te8-7.ccr01.alb02.atlas.cogentco.com (154.54.81.137) 22.365 ms te7-7.ccr02.alb02.atlas.cogentco.com (154.54.42.246) 110.517 ms 111.409 ms
7 te9-7.ccr02.jfk01.atlas.cogentco.com (154.54.42.146) 44.251 ms 42.033 ms 39.336 ms
8 te0-3-0-7.ccr21.jfk02.atlas.cogentco.com (154.54.7.69) 22.206 ms te0-4-0-6.ccr21.jfk02.atlas.cogentco.com (154.54.40.34) 22.029 ms 22.036 ms
9 te0-1-0-6.ccr21.jfk07.atlas.cogentco.com (154.54.46.74) 21.997 ms 23.152 ms te0-4-0-1.ccr21.jfk07.atlas.cogentco.com (154.54.80.174) 21.893 ms
10 savvis.jfk07.atlas.cogentco.com (154.54.11.242) 34.486 ms 33.470 ms 33.044 ms
11 cr1-tengig-0-8-3-0.NewYork.savvis.net (204.70.198.13) 35.771 ms 36.618 ms 32.659 ms
12 cr1-tengig-0-7-0-0.chicago.savvis.net (204.70.196.245) 33.674 ms 37.501 ms 36.395 ms
13 hr1-te-12-0-1.elkgrovech3.savvis.net (204.70.198.73) 34.041 ms 36.634 ms 36.224 ms
14 das3-v3037.ch3.savvis.net (64.37.207.178) 36.338 ms 37.242 ms 34.593 ms
15 64.27.160.194 (64.27.160.194) 47.438 ms 45.906 ms 40.245 ms
16 slashdot.org (216.34.181.45) 37.256 ms 36.430 ms 35.398 ms
Cogent route taken
Reddit.com:
cplexus# traceroute reddit.com
traceroute to reddit.com (173.223.232.64), 30 hops max, 60 byte packets
1 border.unimatrix01.digibase.ca (72.38.129.201) 2.297 ms 2.374 ms 2.639 ms
2 10.64.172.1 (10.64.172.1) 7.401 ms 12.025 ms 13.015 ms
3 d226-5-229.home.cgocable.net (24.226.5.229) 13.941 ms 14.828 ms 14.795 ms
4 67.69.228.101 (67.69.228.101) 14.816 ms 14.821 ms 14.805 ms
5 bx5-chicagodt_xe5-0-3.net.bell.ca (64.230.186.82) 28.753 ms bx5-chicagodt_xe5-0-2.net.bell.ca (64.230.186.78) 28.637 ms bx5-chicagodt_xe6-1-0.net.bell.ca (64.230.186.90) 28.416 ms
6 xe-1-0-6.ar2.ord1.us.nlayer.net (69.31.111.97) 28.714 ms 24.911 ms 27.484 ms
7 ae4-52.cr1.ord1.us.nlayer.net (69.31.111.145) 26.403 ms 21.497 ms 22.869 ms
8 xe-1-2-0.cr1.slc1.us.nlayer.net (69.22.142.102) 60.229 ms 57.860 ms 59.051 ms
9 xe-2-0-1.cr1.sfo1.us.nlayer.net (69.22.142.97) 74.458 ms 75.392 ms 75.415 ms
10 ae3-60g.cr1.pao1.us.nlayer.net (69.22.143.170) 87.503 ms 84.395 ms 88.163 ms
11 ae1-50g.ar1.pao1.us.nlayer.net (69.22.153.17) 78.149 ms 81.729 ms 74.016 ms
12 as20940.xe-1-0-5.ar1.pao1.us.nlayer.net (69.22.130.82) 80.723 ms 79.660 ms 80.674 ms
13 a173-223-232-64.deploy.akamaitechnologies.com (173.223.232.64) 75.346 ms 76.165 ms 76.207 ms
Bell route taken
Facebook.com:
cplexus# traceroute facebook.com
traceroute to www.facebook.com (69.171.229.13), 30 hops max, 60 byte packets
1 border.unimatrix01.digibase.ca (72.38.129.201) 2.264 ms 2.372 ms 2.626 ms
2 10.64.172.1 (10.64.172.1) 7.416 ms 10.871 ms 11.860 ms
3 d226-5-233.home.cgocable.net (24.226.5.233) 22.163 ms 23.067 ms 23.079 ms
4 cgowave-busy3-ubr.cgocable.net (24.226.6.133) 11.687 ms 12.524 ms 12.553 ms
5 67.69.228.101 (67.69.228.101) 13.597 ms 14.245 ms 14.213 ms
6 bx5-chicagodt_xe3-1-0-0.net.bell.ca (64.230.186.246) 24.991 ms 22.384 ms bx5-chicagodt_xe-0-0-3_0.net.bell.ca (64.230.186.106) 26.024 ms
7 facebook_bx5-chicagodt (184.150.181.143) 24.623 ms 25.049 ms 21.615 ms
8 ae1.bb01.sea1.tfbnw.net (74.119.78.74) 88.184 ms ae0.bb02.sea1.tfbnw.net (74.119.79.34) 90.208 ms ae1.bb01.sea1.tfbnw.net (74.119.78.74) 91.748 ms
9 ae5.bb02.prn1.tfbnw.net (74.119.79.99) 100.288 ms 97.809 ms 99.507 ms
10 ae1.dr03.prn1.tfbnw.net (204.15.23.89) 94.096 ms ae0.dr04.prn1.tfbnw.net (204.15.23.87) 123.789 ms 127.235 ms
11 po1022.csw06b.prn1.tfbnw.net (204.15.22.55) 99.687 ms po1023.csw06a.prn1.tfbnw.net (74.119.78.237) 93.121 ms po1022.csw06b.prn1.tfbnw.net (204.15.22.55) 99.950 ms
12 * * *
Bell route taken
Tumblr.com:
cplexus# traceroute tumblr.com
traceroute to tumblr.com (50.97.149.179), 30 hops max, 60 byte packets
1 border.unimatrix01.digibase.ca (72.38.129.201) 2.280 ms 2.384 ms 2.635 ms
2 10.64.172.1 (10.64.172.1) 6.437 ms 10.334 ms 11.324 ms
3 d226-5-225.home.cgocable.net (24.226.5.225) 12.255 ms 12.264 ms 12.238 ms
4 67.69.228.101 (67.69.228.101) 12.990 ms 12.959 ms 12.944 ms
5 bx5-chicagodt_xe6-1-0.net.bell.ca (64.230.186.90) 24.560 ms bx5-chicagodt_xe5-0-3.net.bell.ca (64.230.186.82) 25.467 ms 25.471 ms
6 te1-7.bbr01.eq01.chi01.networklayer.com (206.223.119.63) 26.386 ms 26.253 ms 27.281 ms
7 ae20.bbr01.eq01.dal03.networklayer.com (173.192.18.136) 54.324 ms 56.839 ms 52.002 ms
8 ae5.dar01.sr01.dal05.networklayer.com (173.192.18.215) 49.656 ms 50.620 ms ae6.dar02.sr01.dal05.networklayer.com (50.97.18.193) 50.556 ms
9 po2.fcr02.sr02.dal05.networklayer.com (173.192.118.141) 56.746 ms 50.196 ms po1.fcr02.sr02.dal05.networklayer.com (173.192.118.139) 48.913 ms
10 50.97.149.179-static.reverse.softlayer.com (50.97.149.179) 48.684 ms 53.190 ms 46.551 ms
Bell route taken
It's rare for Cogeco traffic that is en-route to the US that isn't over a TorIX network to take a route that doesn't involve either Cogent or Bell. This is hazardous and therefore my opinion that Cogeco should investigate getting more direct peering.
Reason I'm saying this is that as a business client of Cogeco, My organization operates several services that are contingent on communicating with US associates/associate systems in real-time on a 24/7 basis and notice overnight often times that traffic will get dropped. When I traceroute, it seems many times the drops are over Cogent's or Bell's network. I'm sure that home users would also benefit from having their traffic taking other routes as well as it'd mean less blips or "Cannot connect to server" pages.
This whole situation has resulted in my organization setting up a VPS operated in a Hurricane Electric network (HE is a TorIX-connected provider), giving my organization the option to bypass Cogeco's usual routing and route via another network at our discretion. During our testing, we noticed that we can achieve increased stability over just taking the Cogeco routes.
In closing: I hope this is taken to heart and Cogeco adopts a more diverse group of upstreams/peers.
Edit: Fixing a traceroute mispaste (tumblr.com)
--
--Kradorex Xeron
[an error occurred while processing this signature] | | |
|
cog_biz_useri ruin threads apparently
join:2011-04-19
Hamilton, ON | i believe cogeco had access to edaptivity/cygnal several years ago, before shaw bought out mountain cable... at the time, it was a high-speed tier-2 connection. i don't think that peering exists anymore. | |
Keiro
join:2005-10-25
Bakersfield, CA | reply to DigitalXeron
I'm one of the associates that peer more or less directly with DigitalXeron, and frankly, I have to agree.
Cogeco's peering is shitty at best. Aren't they large enough as is to be considered a Tier1 ISP? :/
Also - why only two peering? Doesn't that leave them wide open to widespread issues if Cogent or Bell has issues?
I know the answer is yes, but as to the why, that's what I'm wondering. Wouldn't it be better for them to not rely as much on Cogent and Bell, given their repeated issues vis-a-vis US-Canada peering?
--
Wanderer of the Stars...
ShatteredTears NOC
Managing: ShatteredTears IRC
EidolonHost | |
| reply to DigitalXeron
SONET ring is redundant. If the route is deemed "down" it will route around it. wikipedia sonet.
You have nothing to worry about. Also, traceroute output is a terrible way to get a view of the network. | |
DigitalXeronThere is a lack of sanity
join:2003-12-17
Hamilton, ON | reply to anonymers1
Re: All of Cogeco's eggs in few baskets? said by anonymers1 :SONET ring is redundant. If the route is deemed "down" it will route around it. wikipedia sonet.
You have nothing to worry about. Also, traceroute output is a terrible way to get a view of the network.
While I am aware that SONET is highly reliable, it is not fool proof. For instance, if you don't have a lot of diversity on a SONET ring and only say have 2 nodes on that ring, if one of the nodes fail (instead of the paths), then that whole ring is technically down.
It primarily concerns me that there may be a lack of diversity on those rings or that there may be a failure within Bell or Cogent's networks (outside of the inter-provider SONET, and Cogeco's network won't see that path as "down" and therefore won't find an alternate path.
I think the SONET rings may be over-saturated with Bell/Cogent nodes, without any other providers being on those rings ("Well, if this Bell node is down, we'll try another Bell node").
--
--Kradorex Xeron
[an error occurred while processing this signature] | |
 nitzguyPremium
join:2002-07-11
Sudbury, ON
 ·TekSavvy DSL
| said by DigitalXeron:said by anonymers1 :SONET ring is redundant. If the route is deemed "down" it will route around it. wikipedia sonet.
You have nothing to worry about. Also, traceroute output is a terrible way to get a view of the network.
While I am aware that SONET is highly reliable, it is not fool proof. For instance, if you don't have a lot of diversity on a SONET ring and only say have 2 nodes on that ring, if one of the nodes fail (instead of the paths), then that whole ring is technically down. It primarily concerns me that there may be a lack of diversity on those rings or that there may be a failure within Bell or Cogent's networks (outside of the inter-provider SONET, and Cogeco's network won't see that path as "down" and therefore won't find an alternate path. I think the SONET rings may be over-saturated with Bell/Cogent nodes, without any other providers being on those rings ("Well, if this Bell node is down, we'll try another Bell node"). As a complete worst case scenario, Cogeco Ontario has a direct peer in Cogeco Quebec which has separate routes out so...I'm sure if somehow both BELL and Cogent went down, then...they'd route out there...they wouldn't let 120k customers out in the lurch...while it may not be ideal from your standpoint, that's who they've decided to peer with and I'm pretty sure that won't be changing anytime soon, they obviously get a decent enough price from these providers.... | |
exsevenPremium,VIP
join:2003-05-23
Beamsville, ON
kudos:1 | There is quite a few more transit/peers than 2. Just cause the op didn't see them doesn't mean they aren't there | |
| reply to DigitalXeron
Cogeco has 4 transit providers that I am aware of. In addition to Bell and Cogent they also use Peer1 and Tinet. The routes cherrypicked in the original post all happen to go through Bell or Cogent but there are many other routes that go out through Peer1 or Tinet.
According to HE's BGP tool info page for Cogeco (AS7992) Tinet and Peer1 handle the majority of the inbound routes. Cogent and Bell are in a distant 3rd and 4th, respectively. See »bgp.he.net/AS7992#_asinfo
I personally have never had a problem with Cogeco's routing. | |
| »www.watchmouse.com/en/worldwide.php
For comparison here are the routes to each of the North American Watchmouse test servers:
Toronto/Hamilton -- Peer 1
traceroute to c2.watchmouse.net (74.82.200.102), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 8.519 ms 6.258 ms 6.032 ms
2 d226-12-93.home.cgocable.net (24.226.12.93) 18.446 ms 16.798 ms 17.689 ms
3 d226-6-130.home.cgocable.net (24.226.6.130) 15.254 ms 14.001 ms 18.595 ms
4 64.34.137.61 (64.34.137.61) 14.234 ms 13.619 ms 14.690 ms
5 72.51.9.92 (72.51.9.92) 14.631 ms 14.814 ms 15.899 ms
6 ge-3-48.core.hamilton.caratnetworks.com (173.234.189.2) 15.889 ms 21.380 ms 15.762 ms
7 torvz08.caratnetworks.com (74.82.200.66) 16.098 ms 23.832 ms 14.327 ms
8 c2.watchmouse.net (74.82.200.102) 16.200 ms 16.159 ms 16.015 ms
Vancouver -- Peer 1
traceroute to bc.watchmouse.net (64.40.107.161), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 11.372 ms 7.589 ms 9.635 ms
2 d226-12-89.home.cgocable.net (24.226.12.89) 13.186 ms 11.495 ms 10.047 ms
3 64.34.137.61 (64.34.137.61) 9.659 ms 10.019 ms 9.593 ms
4 10ge.xe-2-0-0.tor-151f-cor-1.peer1.net (216.187.114.145) 14.301 ms 9.972 ms 9.760 ms
5 oc48.so-2-0-3.van-hc21e-cor-1.peer1.net (216.187.114.137) 70.036 ms 70.967 ms 70.752 ms
6 oc48.so-2-0-0.van-spenc-cor-1.peer1.net (216.187.89.98) 71.917 ms 70.277 ms 69.366 ms
7 10ge.xe-0-2-0.van-spenc-dis-1.peer1.net (216.187.89.206) 70.568 ms 70.694 ms 86.664 ms
8 pix-gw.netnation.com (206.223.127.3) 71.999 ms 70.223 ms 80.745 ms
9 v63-s1-csr.netnation.com (64.40.105.13) 72.963 ms 71.253 ms 71.218 ms
10 bc.watchmouse.com (64.40.107.161) 70.729 ms 71.169 ms 71.975 ms
Chicago -- Peer 1
traceroute to cg.watchmouse.net (67.212.182.130), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 6.578 ms 6.706 ms 5.979 ms
2 d226-12-89.home.cgocable.net (24.226.12.89) 10.800 ms 10.520 ms 12.861 ms
3 64.34.137.61 (64.34.137.61) 10.408 ms 11.628 ms 10.358 ms
4 10ge.xe-2-0-0.tor-151f-cor-1.peer1.net (216.187.114.145) 9.983 ms 10.272 ms 9.324 ms
5 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net (216.187.114.133) 12.205 ms 9.469 ms 10.891 ms
6 10ge.xe-0-0-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 21.743 ms 21.099 ms 19.754 ms
7 mpr1.ord7.us (206.223.119.86) 23.362 ms 25.239 ms 31.528 ms
8 xe-2-2-0.cr1.ord2.us.above.net (64.125.26.249) 50.758 ms 27.959 ms 27.305 ms
9 xe-1-1-0.er1.ord2.us.above.net (64.125.26.186) 27.759 ms 23.297 ms 82.221 ms
10 64.124.200.138.allocated.above.net (64.124.200.138) 26.350 ms 26.311 ms 27.223 ms
11 asw-c10.r02.ord02.singlehop.net (99.198.126.122) 29.130 ms 27.921 ms 27.043 ms
12 cg.watchmouse.net (67.212.182.130) 26.880 ms 25.066 ms 25.804 ms
Chicago #2 -- Peer 1
traceroute to ord.watchmouse.net (173.203.117.242), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 6.932 ms 6.160 ms 6.155 ms
2 d226-12-93.home.cgocable.net (24.226.12.93) 16.901 ms 19.388 ms 17.309 ms
3 d226-6-130.home.cgocable.net (24.226.6.130) 15.185 ms 14.133 ms 14.747 ms
4 64.34.137.61 (64.34.137.61) 14.417 ms 15.406 ms 13.471 ms
5 216.187.113.73 (216.187.113.73) 13.642 ms 14.978 ms 15.244 ms
6 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net (216.187.114.133) 16.265 ms 13.793 ms 13.741 ms
7 10ge.xe-0-0-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 25.509 ms 24.900 ms 23.144 ms
8 bbr1.ord1.rackspace.net (206.223.119.14) 26.194 ms 25.622 ms 26.271 ms
9 coreb.ord1.rackspace.net (184.106.126.146) 28.990 ms 27.340 ms 27.654 ms
10 core1-coreb.ord1.rackspace.net (184.106.126.129) 25.502 ms 26.936 ms 26.821 ms
11 core1-aggr301a-1.ord1.rackspace.net (173.203.0.169) 26.049 ms 26.472 ms 27.357 ms
12 ord.watchmouse.net (173.203.117.242) 25.819 ms 27.071 ms 25.959 ms
New York -- Tinet
traceroute to ny.watchmouse.net (208.85.4.114), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 9.623 ms 6.273 ms 7.115 ms
2 d226-12-89.home.cgocable.net (24.226.12.89) 9.420 ms 9.816 ms 10.845 ms
3 xe-2-2-0.tor10.ip4.tinet.net (77.67.69.237) 10.875 ms 10.795 ms 10.980 ms
4 xe-11-0-0.chi10.ip4.tinet.net (89.149.182.89) 27.597 ms 43.111 ms 28.763 ms
5 213.200.66.54 (213.200.66.54) 29.516 ms 28.992 ms 28.834 ms
6 aby1-ar3-xe-0-0-0-0.us.twtelecom.net (66.192.253.178) 47.798 ms 49.732 ms 48.501 ms
7 208-85-4-114.static.turnkeyinternet.net (208.85.4.114) 48.866 ms 49.199 ms 48.147 ms
Ashburn, VA (Amazon East Coast) -- Peer 1
traceroute to ec2-204-236-207-37.compute-1.amazonaws.com (204.236.207.37), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 7.377 ms 6.631 ms 7.429 ms
2 d226-12-89.home.cgocable.net (24.226.12.89) 9.532 ms 9.752 ms 9.828 ms
3 64.34.137.61 (64.34.137.61) 12.950 ms 10.860 ms 9.303 ms
4 10ge.xe-0-3-0.nyc-telx-dis-1.peer1.net (216.187.114.194) 23.572 ms 24.097 ms 50.198 ms
5 10ge.ten1-2.wdc-sp2-cor-2.peer1.net (216.187.115.222) 30.349 ms 28.871 ms 29.784 ms
6 10ge.ten1-1.wdc-sp2-cor-1.peer1.net (216.187.120.253) 29.832 ms 30.358 ms 29.638 ms
7 10ge.xe-0-0-0.wdc-eqx-dis-1.peer1.net (216.187.115.233) 29.831 ms 29.286 ms 29.787 ms
8 equinix02-iad2.amazon.com (206.223.115.35) 35.593 ms 34.583 ms 34.240 ms
9 72.21.220.45 (72.21.220.45) 33.322 ms 33.950 ms 33.277 ms
10 72.21.222.149 (72.21.222.149) 34.762 ms 36.267 ms 33.510 ms
11 216.182.224.81 (216.182.224.81) 34.102 ms 34.615 ms 38.084 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 ec2-204-236-207-37.compute-1.amazonaws.com (204.236.207.37) 34.747 ms 35.589 ms 37.971 ms
Florida -- Bell
traceroute to fl.watchmouse.net (208.84.149.251), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 10.348 ms 7.246 ms 7.164 ms
2 d226-12-85.home.cgocable.net (24.226.12.85) 17.575 ms 17.544 ms 17.799 ms
3 67.69.228.5 (67.69.228.5) 47.626 ms 17.955 ms 19.920 ms
4 bx4-chicagodt_pos2-0-0.net.bell.ca (64.230.186.174) 33.189 ms 34.864 ms 34.891 ms
5 chi2-pr1-ae5-218.us.twtelecom.net (64.132.69.145) 31.307 ms 31.668 ms 31.747 ms
6 orl1-ar3-xe-1-0-0-0.us.twtelecom.net (66.192.243.202) 63.033 ms 64.784 ms 61.974 ms
7 66.35.95.118 (66.35.95.118) 62.064 ms 64.388 ms 63.133 ms
8 aid.rapidvps.net (208.77.97.197) 62.014 ms 63.387 ms 62.150 ms
9 fl.watchmouse.com (208.84.149.251) 63.638 ms 62.694 ms 63.466 ms
Dallas -- Bell
traceroute to dfw.watchmouse.net (173.203.208.248), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 8.017 ms 5.633 ms 6.098 ms
2 d226-12-93.home.cgocable.net (24.226.12.93) 16.738 ms 17.507 ms 19.223 ms
3 67.69.228.5 (67.69.228.5) 20.065 ms 50.357 ms 19.123 ms
4 bx5-chicagodt_xe3-1-0-0.net.bell.ca (64.230.186.246) 30.732 ms
bx5-chicagodt_xe6-1-0.net.bell.ca (64.230.186.90) 31.415 ms 32.222 ms
5 chi-bb1-link.telia.net (213.248.85.25) 28.276 ms 29.745 ms 27.609 ms
6 dls-bb1-link.telia.net (213.248.80.149) 92.154 ms
dls-bb1-link.telia.net (80.91.248.209) 54.765 ms
dls-bb1-link.telia.net (213.248.80.149) 54.034 ms
7 rackspace-ic-127247-dls-bb1.c.telia.net (213.248.88.174) 56.766 ms 54.522 ms 53.762 ms
8 core7-edge3-vlan3307.dfw1.rackspace.net (174.143.123.114) 51.088 ms 52.771 ms 52.359 ms
9 aggr931a-23.dfw1.rackspace.net (98.129.84.87) 57.399 ms 55.420 ms 56.058 ms
10 dfw.watchmouse.net (173.203.208.248) 56.531 ms 54.517 ms 56.306 ms
Austin -- Cogent
traceroute to ss.watchmouse.net (216.139.225.125), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 7.035 ms 7.752 ms 6.897 ms
2 d226-12-85.home.cgocable.net (24.226.12.85) 17.617 ms 18.871 ms 19.040 ms
3 d226-6-134.home.cgocable.net (24.226.6.134) 19.336 ms 18.577 ms 20.264 ms
4 38.122.17.17 (38.122.17.17) 17.862 ms 15.924 ms 15.451 ms
5 te7-7.ccr01.buf02.atlas.cogentco.com (154.54.24.221) 17.359 ms 17.048 ms 17.602 ms
6 te4-2.ccr02.cle04.atlas.cogentco.com (154.54.27.86) 25.465 ms 24.195 ms 26.666 ms
7 te0-5-0-6.ccr21.ord01.atlas.cogentco.com (154.54.45.130) 30.944 ms 31.687 ms 29.785 ms
8 te0-4-0-0.ccr21.mci01.atlas.cogentco.com (154.54.6.158) 47.709 ms 41.979 ms 50.492 ms
9 te0-3-0-1.ccr21.dfw01.atlas.cogentco.com (154.54.46.186) 53.354 ms 53.029 ms 53.531 ms
10 te0-2-0-2.mpd21.iah01.atlas.cogentco.com (154.54.2.13) 60.644 ms 61.432 ms 60.201 ms
11 te4-3.ccr01.aus02.atlas.cogentco.com (154.54.1.65) 61.860 ms 62.265 ms 61.453 ms
12 te4-2.ccr01.aus03.atlas.cogentco.com (154.54.7.114) 66.596 ms 65.543 ms 67.234 ms
13 38.104.4.90 (38.104.4.90) 100.671 ms 101.861 ms 101.505 ms
14 xe-3-3.dist-rtr-01.aus.us.siteprotect.com (216.139.253.66) 99.659 ms 101.199 ms 99.423 ms
15 xe-26.core-sw-01.aus.us.siteprotect.com (216.139.253.50) 101.893 ms 104.728 ms 125.861 ms
16 ss.watchmouse.com (216.139.225.125) 102.638 ms 100.819 ms 101.787 ms
Santa Clara, CA -- Peer 1
traceroute to ca.watchmouse.net (69.12.222.167), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 10.967 ms 6.467 ms 5.653 ms
2 d226-12-81.home.cgocable.net (24.226.12.81) 17.659 ms 10.263 ms 9.482 ms
3 64.34.137.61 (64.34.137.61) 11.088 ms 10.538 ms 38.010 ms
4 slave4.did-it.net (216.187.113.78) 10.501 ms 10.494 ms 11.882 ms
5 10ge.xe-5-0-0.tor-1yg-cor-1.peer1.net (216.187.114.49) 10.419 ms 12.825 ms 9.959 ms
6 10ge.xe-0-0-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 19.663 ms 20.829 ms 21.618 ms
7 oc48.so-2-1-0.van-spenc-cor-1.peer1.net (216.187.88.197) 69.414 ms 69.553 ms 70.766 ms
8 oc48.so-2-1-0.sea-wes7-dis-1.peer1.net (216.187.89.189) 74.589 ms 71.879 ms 72.014 ms
9 406.ae0.gw.equinix-sj.sonic.net (206.81.80.107) 91.287 ms 96.739 ms 92.198 ms
10 0.ge-0-1-0.gw2.sr.sonic.net (64.142.0.205) 94.538 ms 96.958 ms 95.274 ms
11 gig0-2.dist3-1.sr.sonic.net (208.201.224.165) 97.130 ms 97.887 ms 97.449 ms
12 70-36-170-194.static.sonic.net (70.36.170.194) 97.723 ms 95.624 ms 99.649 ms
13 usscz01.watchmouse.net (69.12.222.167) 98.194 ms 97.411 ms 97.577 ms
San Francisco, CA -- Tinet
traceroute to sf.watchmouse.net (69.59.179.208), 64 hops max, 72 byte packets
1 10.90.192.1 (10.90.192.1) 8.286 ms 5.618 ms 6.146 ms
2 d226-12-81.home.cgocable.net (24.226.12.81) 10.859 ms 10.030 ms 12.061 ms
3 xe-2-2-0.tor10.ip4.tinet.net (77.67.69.237) 9.247 ms 10.335 ms 11.453 ms
4 xe-9-1-0.chi10.ip4.tinet.net (89.149.187.78) 21.069 ms 21.829 ms 23.662 ms
5 xe-0.equinix.chcgil09.us.bb.gin.ntt.net (206.223.119.12) 22.960 ms 22.406 ms 23.373 ms
6 ae-0.r21.chcgil09.us.bb.gin.ntt.net (129.250.3.98) 22.826 ms 23.179 ms 23.783 ms
7 ae-5.r20.snjsca04.us.bb.gin.ntt.net (129.250.3.107) 79.412 ms 81.333 ms 82.242 ms
8 ae-4.r05.plalca01.us.bb.gin.ntt.net (129.250.5.32) 86.029 ms 84.536 ms 87.939 ms
9 xe-0-0-0-1.r05.plalca01.us.ce.gin.ntt.net (140.174.41.102) 81.753 ms 83.822 ms 80.345 ms
10 vl22.access11.sfo2.servepath.com (208.96.31.12) 84.108 ms 85.794 ms 86.031 ms
11 sf.watchmouse.com (69.59.179.208) 81.870 ms 78.266 ms 77.214 ms
So out of 11 destinations we have Peer 1 = 6, Bell = 2, Tinet = 2, Cogent = 1. | |
|
