|
Lets assume that over backbones, nothing staying in NYC will take more than 2ms (can be verified from any good backbone).
For example... If something takes 20ms, that means it takes 10 times longer...
From NYC -> NYC (over ALGX)
We go through chicago.
Cost of performance, approx 30ms. (15 times more lag)
3 g12-8.core01.jfk01.atlas.cogentco.com (66.28.65.33) 0.980 ms 1.380 ms 0.783 ms
4 p13-0.core02.jfk02.atlas.cogentco.com (66.28.4.121) 0.825 ms 0.826 ms 0.653 ms
5 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 26.679 ms 26.841 ms 27.251 ms
6 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 26.668 ms 26.613 ms 26.663 ms
7 206.220.243.179 (206.220.243.179) 30.461 ms 30.532 ms 30.374 ms
8 ord2-core3-pos6-0.atlas.algx.net (165.117.48.97) 30.799 ms 30.670 ms 30.743 ms
9 ord2-core2-pos6-0.atlas.algx.net (165.117.48.93) 31.042 ms 30.749 ms 31.641 ms
10 jfk3-core2-pos5-0.atlas.algx.net (165.117.48.37) 30.782 ms 31.699 ms 30.250 ms
11 jfk3-core4-pos6-0.atlas.algx.net (165.117.48.166) 30.670 ms 30.711 ms 30.282 ms
From NYC -> NYC (over ATT)
We go through California!
cost of performance, approx 74 ms. (37 times more lag)
3 g12-8.core01.jfk01.atlas.cogentco.com (66.28.65.33) 1.879 ms 0.902 ms 0.790 ms
4 p4-0.core01.jfk02.atlas.cogentco.com (66.28.4.10) 2.469 ms 0.757 ms 0.746 ms
5 p4-0.core02.dca01.atlas.cogentco.com (66.28.4.81) 6.863 ms 7.177 ms 7.829 ms
6 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.125) 18.803 ms 18.852 ms 18.374 ms
7 p15-0.core01.jax01.atlas.cogentco.com (66.28.4.137) 25.960 ms 24.961 ms 24.687 ms
8 p14-0.core01.tpa01.atlas.cogentco.com (66.28.4.141) 30.290 ms 29.679 ms 29.699 ms
9 p5-0.core01.iah01.atlas.cogentco.com (66.28.4.45) 49.415 ms 49.313 ms 49.364 ms
10 p14-0.core01.san01.atlas.cogentco.com (66.28.4.6) 80.513 ms 80.003 ms 80.182 ms
11 p4-0.core01.lax01.atlas.cogentco.com (66.28.4.77) 83.459 ms 82.451 ms 82.814 ms
12 p6-0.br01.lax10.atlas.psi.net (154.54.1.30) 82.618 ms 82.598 ms 82.722 ms
13 p4-0.sw.peering2.tier1.psi.net (154.54.1.34) 82.405 ms 82.607 ms 82.724 ms
14 nw.peering.tier1.us.psi.net (154.13.2.106) 92.831 ms 92.762 ms 92.725 ms
15 154.13.74.2 (154.13.74.2) 85.746 ms 85.726 ms 85.753 ms
16 gbr3-p50.sffca.ip.att.net (12.123.13.66) 86.496 ms 85.722 ms 85.765 ms
17 gbr3-p20.cgcil.ip.att.net (12.122.2.154) 100.680 ms 101.007 ms 100.956 ms
18 gbr3-p30.n54ny.ip.att.net (12.122.2.174) 140.906 ms 139.790 ms 140.116 ms
19 gbr1-p100.n54ny.ip.att.net (12.122.1.150) 140.302 ms 140.184 ms 139.986 ms
20 ar10-a300s1.n54ny.ip.att.net (12.123.0.217) 140.503 ms 141.644 ms 140.618 ms
From NYC -> NYC (over Cable And Wireless - CW)
We go through California!
cost of performance, 163ms! (81.5 times more lag)
3 g3-8.core01.jfk01.atlas.cogentco.com (66.28.65.29) 0.957 ms 0.890 ms 0.835 ms
4 p13-0.core02.jfk02.atlas.cogentco.com (66.28.4.121) 0.812 ms 0.700 ms 0.720 ms
5 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 26.700 ms 26.755 ms 26.613 ms
6 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 26.882 ms 26.717 ms 27.076 ms
7 p5-0.core01.sfo01.atlas.cogentco.com (66.28.4.42) 72.462 ms 72.842 ms 72.502 ms
8 p15-0.core02.sfo01.atlas.cogentco.com (66.28.4.70) 72.581 ms 72.487 ms 72.527 ms
9 p6-0.tr1.sfr1.netrail.net (66.28.28.58) 72.782 ms 73.411 ms 72.730 ms
10 ge-2-2-0--0.pr1.SanFrancisco1.CA.us.netrail.net (205.215.12.2) 72.860 ms 73.353 ms 73.134 ms
11 205.215.2.86 (205.215.2.86) 73.119 ms 73.502 ms 73.089 ms
12 agr1-loopback.SantaClara.cw.net (208.172.146.101) 76.436 ms 76.603 ms 76.657 ms
13 dcr1-so-6-0-0.SantaClara.cw.net (208.172.156.37) 76.204 ms 76.114 ms 75.911 ms
14 dcr2-loopback.NewYork.cw.net (206.24.194.100) 163.998 ms 165.480 ms 164.017 ms
15 agr1-so-6-0-0.NewYork.cw.net (206.24.207.194) 165.858 ms 165.150 ms 165.611 ms
16 bar15-loopback.NewYork.cw.net (206.24.194.32) 165.417 ms * 164.357 ms
From NYC -> NYC (over qwest)
We go through Atlanta.
cost of performance, 40ms. (20 times more lag)
3 g3-8.core01.jfk01.atlas.cogentco.com (66.28.65.29) 1.073 ms 0.935 ms 1.039 ms
4 p4-0.core01.jfk02.atlas.cogentco.com (66.28.4.10) 0.840 ms 0.778 ms 0.757 ms
5 p4-0.core02.dca01.atlas.cogentco.com (66.28.4.81) 6.906 ms 7.038 ms 7.109 ms
6 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.125) 18.703 ms 18.736 ms 18.428 ms
7 g3-0.pr1.atl01.netrail.net (66.28.28.202) 18.496 ms 18.909 ms 18.261 ms
8 205.215.2.54 (205.215.2.54) 18.564 ms 18.250 ms 18.259 ms
9 atl-core-03.inet.qwest.net (205.171.21.105) 18.610 ms 18.491 ms 18.964 ms
10 wdc-core-03.inet.qwest.net (205.171.5.241) 33.598 ms 33.690 ms 33.601 ms
11 wdc-core-02.inet.qwest.net (205.171.24.5) 33.884 ms 33.833 ms 33.811 ms
12 jfk-core-01.inet.qwest.net (205.171.5.233) 42.495 ms 42.716 ms 42.517 ms
13 jfk-edge-02.inet.qwest.net (205.171.30.90) 42.581 ms 42.630 ms 43.144 ms
From NYC -> NYC (over Level3)
We go through California!
Cost of performance, 150ms. (75 times more lag)
3 g12-8.core01.jfk01.atlas.cogentco.com (66.28.65.33) 1.186 ms 10.128 ms 1.202 ms
4 p13-0.core02.jfk02.atlas.cogentco.com (66.28.4.121) 0.751 ms 1.244 ms 1.278 ms
5 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 27.873 ms 26.879 ms 26.831 ms
6 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 26.737 ms 26.752 ms 26.903 ms
7 p5-0.core01.sfo01.atlas.cogentco.com (66.28.4.42) 75.616 ms 72.649 ms 72.365 ms
8 p15-0.core02.sfo01.atlas.cogentco.com (66.28.4.70) 72.528 ms 72.515 ms 72.607 ms
9 p6-0.tr1.sfr1.netrail.net (66.28.28.58) 72.970 ms 72.964 ms 72.795 ms
10 ge-2-2-0--0.pr1.SanFrancisco1.CA.us.netrail.net (205.215.12.2) 73.003 ms 72.932 ms 73.362 ms
11 pos4-0.edge1.paix-sjo1.Level3.net (209.245.146.177) 72.972 ms 73.430 ms 73.134 ms
12 unknown.Level3.net (209.245.146.181) 74.013 ms 74.680 ms 73.406 ms
13 ae0-52.mp2.SanJose1.Level3.net (64.159.2.33) 74.341 ms 74.269 ms 75.063 ms
14 so-2-0-0.mp2.NewYork1.Level3.net (64.159.1.85) 150.261 ms 150.842 ms 150.377 ms
From NYC -> NYC (over UUnet)
We go through Chicago.
Cost of performance 39ms (20 times more lag)
3 g12-8.core01.jfk01.atlas.cogentco.com (66.28.65.33) 1.084 ms 1.647 ms 0.756 ms
4 p4-0.core01.jfk02.atlas.cogentco.com (66.28.4.10) 0.907 ms 0.766 ms 0.727 ms
5 p4-0.core02.dca01.atlas.cogentco.com (66.28.4.81) 7.219 ms 6.843 ms 25.148 ms
6 p6-0.br01.dca01.atlas.psi.net (154.54.1.62) 6.603 ms 6.525 ms 6.876 ms
7 p6-0.se.peering.tier1.psi.net (154.54.1.78) 7.929 ms 7.719 ms 7.976 ms
8 nc.peering.tier1.us.psi.net (154.13.2.67) 43.608 ms 44.330 ms 43.543 ms
9 204.255.168.217 (204.255.168.217) 36.496 ms 36.371 ms 36.737 ms
10 0.so-5-2-0.XL2.CHI2.ALTER.NET (152.63.68.6) 36.525 ms 36.551 ms 36.538 ms
11 0.so-1-0-0.TL2.CHI2.ALTER.NET (152.63.67.121) 37.394 ms 36.808 ms 37.090 ms
12 129.at-6-0-0.TR1.LAX9.ALTER.NET (152.63.0.110) 38.596 ms 38.892 ms 38.859 ms
13 0.so-1-0-0.XL2.NYC9.ALTER.NET (152.63.23.130) 38.631 ms 38.513 ms 38.550 ms
14 0.so-0-0-0.XR2.NYC9.ALTER.NET (152.63.9.89) 39.453 ms 39.463 ms 41.040 ms
15 180.ATM7-0.XR2.EWR1.ALTER.NET (152.63.17.241) 38.745 ms 45.038 ms 38.897 ms
16 192.ATM7-0.GW6.EWR1.ALTER.NET (152.63.24.185) 41.844 ms 39.384 ms 39.301 ms
Now, some people who run their businesses on cogent will say "Well, it depends on where on cogent's network you are, my city is better!" Believe it all you want, but cogent's routing is so backwards, that I've seen situations where you could be in california, tracing to california over one of the networks above that go through california, and now it will go through a peering point in virginia.
Others will say... "Well, My sites are fast", to you, perhaps... But certainly not to everyone. If you believe cogent cares about *ANYTHING* more than "cheapest route", you are highly mistaken. If it will cost them $0.0001 more to send your packet through a good route, they wont.
I think I covered every major network on here, and every single one has a much worse route than what you would call quality. For surfing, yeah, this is probably good enough, but I wouldn't be caught dead trusting my business to this.
|