 espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2
 ·Clear Wireless
| Discounted price for partial accessInteresting Cogent would take the discount route instead of improving their network, but they did lose a good chunk of customers after the recent Telia depeering. Given that they've been depeered a few times in the past, with Level(3) and Telia being the most recent I would be hesitant to sign a 3 year agreement with them even if they were used as only one of several upstream providers.
Latency performance with Cogent isn't always ideal either as they are missing large sections of mid-continental routing. Want to go from Chicago to Jacksonville? They don't have a link between Chicago and Atlanta like most carriers; instead you get to take the path all the way up through Boston and then back down the coast.
traceroute to www.colo4jax.com (38.113.65.18), 30 hops max, 40 byte packets
1 69.65.40.62 (69.65.40.62) 0.356 ms 0.351 ms 0.810 ms
2 so2-0-0-0.er1.Chi1.Servernap.net (69.39.239.169) 1.515 ms 2.012 ms 2.010 ms
3 gi0-8.na21.b000359-1.ord01.atlas.cogentco.com (66.28.21.17) 2.006 ms 2.506 ms 2.503 ms
4 gi0-7.3574.core01.ord01.atlas.cogentco.com (38.112.38.45) 2.484 ms 2.484 ms 2.482 ms
5 po14-0.core01.alb02.atlas.cogentco.com (154.54.1.57) 19.780 ms 19.778 ms *
6 po14-0.core01.bos01.atlas.cogentco.com (66.28.4.109) 22.722 ms 22.734 ms 22.722 ms
7 po0-0.core02.jfk02.atlas.cogentco.com (154.54.7.78) 27.869 ms 28.081 ms 28.065 ms
8 po13-0.core01.phl01.atlas.cogentco.com (66.28.4.2) 30.116 ms 30.259 ms 30.250 ms
9 po5-0.core01.dca01.atlas.cogentco.com (66.28.4.17) 33.856 ms 33.857 ms 33.848 ms
10 po10-0.core01.atl01.atlas.cogentco.com (154.54.7.153) 46.148 ms 46.252 ms 46.241 ms
11 po6-0.core01.jax01.atlas.cogentco.com (154.54.3.198) 52.655 ms 52.684 ms 53.157 ms
12 vl3501.na21.b005947-0.jax01.atlas.cogentco.com (38.112.34.230) 52.651 ms 53.149 ms 53.144 ms
13 Tical_Network_Solutions.dmarc.cogentco.com (66.28.230.34) 52.643 ms 53.125 ms 53.126 ms
14 shellx.tical.net (38.113.65.18) 52.602 ms 52.605 ms 52.602 ms
|
|
 DogfatherPremium
join:2007-12-26
Laguna Hills, CA | You get what you pay for I suppose. |
|
|
|
 53059959Temp banned from BBR more then anyone
join:2002-10-02
PwnZone | reply to espaeth
thats not unusual latency.
most providers go chicago -> dallas or chicago -> new york city.
Only a select few providers don't go from atlanta -> nyc or dallas. |
|
| reply to espaeth
Would you be happier if they just did what other carriers do and enable 'no mpls ip propagate-ttl' or the equivalent vendor command? Voila. Looks like direct connectivity to you.
Hops != bad connectivity. |
|
 Jerm
join:2000-04-10
Richland, WA
kudos:2 | reply to espaeth
Poor geographic routing choices isn't limited to Cogent. If you use Verizon in my area 50% of the time to get to a Seattle based site you go down to Cali then back up (seattle-sfo-seattle). |
|
espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2 Reviews:
·Clear Wireless
| reply to jrowley
said by jrowley:Hops != bad connectivity. I didn't say anything at all about hops, I said they had less than ideal physical pathways in some area.
Compare it to another facility that is connected to Level(3) in Tampa (even further south than Jacksonville) and round trip latency is about 10ms less than Cogent because Chicago and Atlanta are directly connected. Whether that 10ms breaks things for you or not depends entirely on your application.
traceroute to www.sagonet.com (65.110.32.145), 30 hops max, 40 byte packets
1 69.65.40.62 (69.65.40.62) 0.710 ms 0.691 ms 0.690 ms
2 so2-0-0-0.er1.Chi1.Servernap.net (69.39.239.169) 1.752 ms 1.752 ms 1.749 ms
3 ge-6-20.car1.Chicago1.Level3.net (4.79.65.49) 14.968 ms 14.967 ms 14.966 ms
4 ae-32-56.ebr2.Chicago1.Level3.net (4.68.101.190) 13.589 ms 13.597 ms 13.595 ms
5 ae-3.ebr2.Atlanta2.Level3.net (4.69.132.74) 34.223 ms 34.235 ms 34.233 ms
6 ae-12-51.car2.Atlanta1.Level3.net (4.68.103.3) 137.050 ms 112.702 ms 112.688 ms
7 WBS-CONNECT.car2.Atlanta1.Level3.net (4.78.211.54) 35.994 ms 35.773 ms 36.244 ms
8 ve40.core01a.tpa.sagonet.net (63.246.159.41) 44.334 ms 44.329 ms 44.324 ms
9 gige1.as01.dist.nms.tpa.sagonet.net (65.110.32.31) 43.799 ms Gige2.as01.dist.nms.tpa.sagonet.net (65.110.32.79) 44.795 ms 45.315 ms
10 www.sagonet.com (65.110.32.145) 44.422 ms 44.351 ms 44.335 ms
|
|
espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2 Reviews:
·Clear Wireless
| reply to 53059959
said by 53059959:Only a select few providers don't go from atlanta -> nyc or dallas. I don't know if it's necessarily that few.
Global Crossing, Telia, Level(3), Sprint, Qwest, Verizon/UUNet and XO all have direct paths from ORD to ATL.
ATT & Savvis route via St Louis. |
|
 SLDPremium
join:2002-04-17
San Francisco, CA | reply to espaeth
Just for kicks, I ran a trace from Houston to your facility in Jacksonville - a much different story:
1 38.104.62.62 (38.104.62.62) 2.562 ms 2.699 ms 2.868 ms
2 gi0-8.na21.b015437-0.iah02.atlas.cogentco.com (38.104.62.61) 0.639 ms 0.968 ms 1.264 ms
3 gi5-0.3821.core01.iah02.atlas.cogentco.com (66.250.8.165) 0.507 ms 0.520 ms 0.524 ms
4 gi1-7.core01.iah01.atlas.cogentco.com (66.28.4.113) 0.963 ms 0.969 ms 0.978 ms
5 po15-0.core01.tpa01.atlas.cogentco.com (66.28.4.46) 20.963 ms 21.070 ms *
6 po3-0.core01.jax01.atlas.cogentco.com (66.28.4.154) 25.943 ms 25.976 ms 26.068 ms
7 vl3501.na21.b005947-0.jax01.atlas.cogentco.com (38.112.34.230) 26.085 ms 26.443 ms 26.624 ms
8 Tical_Network_Solutions.dmarc.cogentco.com (66.28.230.34) 26.536 ms 26.644 ms 26.833 ms
9 shellx.tical.net (38.113.65.18) 26.170 ms 26.418 ms 26.200 ms
|
|
53059959Temp banned from BBR more then anyone
join:2002-10-02
PwnZone | reply to espaeth
it may say its a direct route on the network map, and the reverse dns may go from directly atl to chi but you'll notice most of the time the latency is roughly the same as if it were going through new york, because it is |
|
