That's a Cogent issue. Let's not blame CC on everything
. You can say CC shouldn't just use Cogent though. What ping are you getting? (out of interest)?
New York - What Interest is there?
- Thread starter Reece-DM
- Start date
. You can say CC shouldn't just use Cogent though. What ping are you getting? (out of interest)?
I saw the same thing with L3 as well. I don't think there is very much bandwidth that runs from NYC to Buffalo. The only time I saw a trace go direct when it was from a university in NYC to Buffalo.That's a Cogent issue. Let's not blame CC on everything
Other than that I've always seen it going through Chicago :S
I would have figured Telia would be the favored transit to get to Europe. It should give fairly nice latency. Then again, if it's having to backhaul that sucks
Francisco
Then maybe it is a CC problem. It depends on where they backhaul transit from. I would have thought they organized a real POP in Buffalo. Hm.I saw the same thing with L3 as well. I don't think there is very much bandwidth that runs from NYC to Buffalo. The only time I saw a trace go direct when it was from a university in NYC to Buffalo.
Other than that I've always seen it going through Chicago :S
I would have figured Telia would be the favored transit to get to Europe. It should give fairly nice latency. Then again, if it's having to backhaul that sucks
Francisco
I haven't seen that great results from Telia actually. At least not worth the pricing it asks for.
peterw
New Member
Last edited by a moderator:
peterw
New Member
No. They don't even have a looking glass http://www.cogentco.com/en/network/looking-glass
drmike
100% Tier-1 Gogent
I missed the end of this thread
Routing out of Buffalo is often wrong directed from CC's network. The Chicago preference, yes, exists.
Frankly, I don't believe the upstream providers are the reason for the routing issues.
I tested two NYC based sites (government and school district) and found the routing of one prior via Chicago. The other was fine. Today, they are both fine and Telia or XO handles most of the route with little handoff.
Prior, I was seeing lots of Telia to XO to someone else. It was common to see Telia to XO to Cogent and then back again to Telia.
Hard to say what has changed in past month, but from my simple tests, much better.
Routing out of Buffalo is often wrong directed from CC's network. The Chicago preference, yes, exists.
Frankly, I don't believe the upstream providers are the reason for the routing issues.
I tested two NYC based sites (government and school district) and found the routing of one prior via Chicago. The other was fine. Today, they are both fine and Telia or XO handles most of the route with little handoff.
Prior, I was seeing lots of Telia to XO to someone else. It was common to see Telia to XO to Cogent and then back again to Telia.
Hard to say what has changed in past month, but from my simple tests, much better.
drmike
100% Tier-1 Gogent
Of course, one more test and this funny route from Buffalo:
7: te0-2-0-0.mpd22.jfk02.atlas.cogentco.com 10.520ms asymm 9
8: vlan52.ebr2.Chicago2.Level3.net 44.577ms asymm 11
9: level3.jfk05.atlas.cogentco.com 10.478ms asymm 8
10: ae-3-3.ebr2.Atlanta2.Level3.net 47.307ms asymm 11
11: ae-71-71.ebr1.NewYork1.Level3.net 41.281ms
12: ae-2-52.edge1.Miami2.Level3.net 43.352ms asymm 10
13: ae-1-100.ebr1.Washington12.Level3.net 41.129ms asymm 11
14: ae-6-6.ebr1.Atlanta2.Level3.net 41.208ms asymm 11
15: ae-1-100.ebr2.Atlanta2.Level3.net 41.510ms asymm 11
16: ae-2-2.ebr2.Miami1.Level3.net 40.986ms asymm 10
17: ae-2-52.edge1.Miami2.Level3.net 40.942ms asymm 10
Buffalo ---> NYC ---> Chicago ---> NYC ---> Atlanta ---> NYC --> Miami --> DC --> Atlanta --> Miami
Doh!
7: te0-2-0-0.mpd22.jfk02.atlas.cogentco.com 10.520ms asymm 9
8: vlan52.ebr2.Chicago2.Level3.net 44.577ms asymm 11
9: level3.jfk05.atlas.cogentco.com 10.478ms asymm 8
10: ae-3-3.ebr2.Atlanta2.Level3.net 47.307ms asymm 11
11: ae-71-71.ebr1.NewYork1.Level3.net 41.281ms
12: ae-2-52.edge1.Miami2.Level3.net 43.352ms asymm 10
13: ae-1-100.ebr1.Washington12.Level3.net 41.129ms asymm 11
14: ae-6-6.ebr1.Atlanta2.Level3.net 41.208ms asymm 11
15: ae-1-100.ebr2.Atlanta2.Level3.net 41.510ms asymm 11
16: ae-2-2.ebr2.Miami1.Level3.net 40.986ms asymm 10
17: ae-2-52.edge1.Miami2.Level3.net 40.942ms asymm 10
Buffalo ---> NYC ---> Chicago ---> NYC ---> Atlanta ---> NYC --> Miami --> DC --> Atlanta --> Miami
Doh!
wlanboy
Content Contributer
Have a nice Buffalo -> Chicago routing too: BUF -> NY ->CHI
3 . (172.245.12.225) 0.799 ms host.colocrossing.com (192.3.9.141) 0.905 ms 0.832 ms
4 te7-4.ccr01.buf02.atlas.cogentco.com (38.122.36.45) 10.280 ms 207.86.157.13 (207.86.157.13) 0.393 ms te7-4.ccr01.buf02.atlas.cogentco.com (38.122.36.45) 10.252 ms
5 nyk-bb1-link.telia.net (80.91.246.37) 9.655 ms 9.620 ms 9.663 ms
6 nyk-b3-link.telia.net (80.91.248.174) 9.899 ms te9-7.ccr01.jfk01.atlas.cogentco.com (154.54.43.6) 10.347 ms te4-4.ccr01.jfk01.atlas.cogentco.com (154.54.42.142) 10.254 ms
7 te0-6-0-6.ccr22.jfk02.atlas.cogentco.com (154.54.24.150) 10.453 ms tmobile-ic-302276-war-b1.c.telia.net (213.248.83.118) 24.822 ms 24.653 ms
8 eth4-3.r1.nyc1.us.atrato.net (78.152.44.201) 24.605 ms 24.584 ms 24.508 ms
9 eth1-3.r1.chi1.us.atrato.net (78.152.35.240) 13.172 ms 24.060 ms eth2-4.r1.chi1.us.atrato.net (78.152.34.150) 24.130 ms
Routing to Florida is nice too: BUF -> NY -> Washington -> Miami -> NY -> Tampa
3 . (172.245.12.225) 0.799 ms host.colocrossing.com (192.3.9.141) 0.905 ms 0.832 ms
4 te7-4.ccr01.buf02.atlas.cogentco.com (38.122.36.45) 10.280 ms 207.86.157.13 (207.86.157.13) 0.393 ms te7-4.ccr01.buf02.atlas.cogentco.com (38.122.36.45) 10.252 ms
5 nyk-bb1-link.telia.net (80.91.246.37) 9.655 ms 9.620 ms 9.663 ms
6 nyk-b3-link.telia.net (80.91.248.174) 9.899 ms te9-7.ccr01.jfk01.atlas.cogentco.com (154.54.43.6) 10.347 ms te4-4.ccr01.jfk01.atlas.cogentco.com (154.54.42.142) 10.254 ms
7 te0-6-0-6.ccr22.jfk02.atlas.cogentco.com (154.54.24.150) 10.453 ms tmobile-ic-302276-war-b1.c.telia.net (213.248.83.118) 24.822 ms 24.653 ms
8 eth4-3.r1.nyc1.us.atrato.net (78.152.44.201) 24.605 ms 24.584 ms 24.508 ms
9 eth1-3.r1.chi1.us.atrato.net (78.152.35.240) 13.172 ms 24.060 ms eth2-4.r1.chi1.us.atrato.net (78.152.34.150) 24.130 ms
Routing to Florida is nice too: BUF -> NY -> Washington -> Miami -> NY -> Tampa
Code:
3 . (172.245.12.225) 2.571 ms host.colocrossing.com (192.3.9.141) 0.961 ms 0.949 ms
4 207.86.157.13 (207.86.157.13) 0.403 ms te7-4.ccr01.buf02.atlas.cogentco.com (38.122.36.45) 10.280 ms 10.418 ms
5 nyk-bb1-link.telia.net (80.91.246.37) 9.778 ms 9.634 ms 9.645 ms
6 te9-7.ccr01.jfk01.atlas.cogentco.com (154.54.43.6) 10.310 ms 216.156.0.249.ptr.us.xo.net (216.156.0.249) 57.282 ms 69.087 ms
7 te-3-0-0.rar3.washington-dc.us.xo.net (207.88.12.74) 64.221 ms xo-ic-138322-nyk-b6.c.telia.net (213.248.67.62) 15.485 ms te0-2-0-0.mpd22.jfk02.atlas.cogentco.com (154.54.40.30) 10.429 ms
8 be2060.ccr21.jfk05.atlas.cogentco.com (154.54.31.10) 10.780 ms te-3-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.9) 63.342 ms 63.361 ms
9 level3.jfk05.atlas.cogentco.com (154.54.11.218) 10.283 ms level3.jfk05.atlas.cogentco.com (154.54.12.250) 10.167 ms te-4-0-0.rar3.miami-fl.us.xo.net (207.88.12.6) 60.839 ms
10 te-4-0-0.rar3.miami-fl.us.xo.net (207.88.12.6) 54.124 ms vlan70.csw2.NewYork1.Level3.net (4.69.155.126) 46.051 ms te-4-0-0.rar3.miami-fl.us.xo.net (207.88.12.6) 53.900 ms
11 64.220.113.122.ptr.us.xo.net (64.220.113.122) 57.560 ms ae0d0.mcr1.tampa-fl.us.xo.net (216.156.0.218) 51.488 ms 51.232 ms
12 4.69.201.70 (4.69.201.70) 46.250 ms 4.69.201.66 (4.69.201.66) 47.279 ms 64.220.113.122.ptr.us.xo.net (64.220.113.122) 51.712 ms
13 ae-1-100.ebr1.Washington12.Level3.net (4.69.143.213) 56.858 ms v996.core1.esnet.com (216.139.207.17) 52.184 ms 51.984 msTest IP for anyone: 23.81.66.251
I'll be adding a looking glass later, please note I am waiting on final IP allocations from DC then things will be live and ready for everyone.
[SIZE=12.727272033691406px]Also final note: We will be getting our own allocation from ARIN soon enough which will be in effect within the next month or so[/SIZE]
I'll be adding a looking glass later, please note I am waiting on final IP allocations from DC then things will be live and ready for everyone.
[SIZE=12.727272033691406px]Also final note: We will be getting our own allocation from ARIN soon enough which will be in effect within the next month or so
[/SIZE]
Last edited by a moderator:
drmike
100% Tier-1 Gogent
Thanks @wlanboy. Textbook examples wrong routing.
I don't muck at the network routing level, but seems be something afoul in Buffalo. These routes weren't busted like this until Cogent and XO got thrown in the mix and Level 3 was basically removed.
Sad, because Buffalo is actually pretty speedy from my location and upstream. That's even with my upstream routing everything through Chicago. So latency = 35-40ms whereas if routed right would be < 20ms. My upstreams stupidity on that, not Colocrossing's.
I don't muck at the network routing level, but seems be something afoul in Buffalo. These routes weren't busted like this until Cogent and XO got thrown in the mix and Level 3 was basically removed.
Sad, because Buffalo is actually pretty speedy from my location and upstream. That's even with my upstream routing everything through Chicago. So latency = 35-40ms whereas if routed right would be < 20ms. My upstreams stupidity on that, not Colocrossing's.
wlanboy
Content Contributer
Yup. I can confirm that the routing was way better at the beginning of 2012. I even moved my vps from Chicago to Buffalo these days.
Main reason why I had 4 vps in Buffalo (now 2).
wlanboy
Content Contributer
Thank you for sharing.
From UK:
4 ldn-b3-link.telia.net (80.239.195.133) 1.206 ms 1.201 ms 1.188 ms
5 ldn-bb1-link.telia.net (213.155.133.2) 1.234 ms ldn-bb1-link.telia.net (80.91.245.26) 1.265 ms ldn-bb1-link.telia.net (80.91.251.166) 1.203 ms
6 ldn-b5-link.telia.net (80.91.246.147) 1.120 ms 1.336 ms ldn-b5-link.telia.net (213.155.132.195) 1.220 ms
7 abovenet-ic-151536-ldn-b5.c.telia.net (213.248.76.86) 1.229 ms 4.181 ms 4.111 ms
8 xe-0-0-1.mpr2.lhr2.uk.above.net (64.125.21.29) 1.453 ms 1.445 ms 1.441 ms
9 ge-3-3-0.mpr1.la5.us.above.net (64.125.26.37) 89.356 ms 89.336 ms 89.312 ms
10 xe-0-0-0.cr2.lga5.us.above.net (64.125.29.42) 69.939 ms 69.921 ms 69.898 ms
11 xe-0-1-0.mpr2.lga7.us.above.net (64.125.27.117) 69.803 ms 69.791 ms 69.890 ms
12 208.184.35.178.IPYX-067818-004-ZYO.above.net (208.184.35.178) 70.703 ms 70.564 ms 73.487 ms
From NL:
3 jointtransit.telecity2.openpeering.nl (82.150.153.93) 1.628 ms 1.706 ms 1.723 ms
4 er1.ams1.nl.above.net (195.69.144.122) 5.584 ms 5.555 ms 5.545 ms
5 ge-3-3-0.mpr1.ams1.nl.above.net (64.125.25.13) 2.232 ms 2.215 ms 2.229 ms
6 xe-5-3-0.cr2.lga5.us.above.net (64.125.25.57) 107.715 ms 101.043 ms 101.026 ms
7 xe-0-1-0.mpr2.lga7.us.above.net (64.125.27.117) 77.135 ms 77.172 ms 77.161 ms
8 208.184.35.178.IPYX-067818-004-ZYO.above.net (208.184.35.178) 77.342 ms 77.342 ms 77.464 ms
From Tallin:
3 r9-ae3-0-Tln-Linx-EE.linxtelecom.net (195.222.7.169) 0.354 ms 0.345 ms 0.326 ms
4 r9-ae2-0-Sln-Song-SE.linxtelecom.net (212.47.201.190) 28.000 ms 5.864 ms 27.960 ms
5 xe-10-3-1-651.bar1.Stockholm1.Level3.net (213.242.110.77) 5.712 ms 5.716 ms 5.709 ms
6 ae-113-3503.bar1.Stockholm1.Level3.net (4.69.158.250) 35.470 ms ae-111-3501.bar1.Stockholm1.Level3.net (4.69.158.242) 35.938 ms ae-114-3504.bar1.Stockholm1.Level3.net (4.69.158.254) 35.762 ms
7 ae-45-45.ebr3.Frankfurt1.Level3.net (4.69.143.166) 34.911 ms 34.920 ms ae-48-48.ebr3.Frankfurt1.Level3.net (4.69.143.178) 35.688 ms
8 ae-83-83.csw3.Frankfurt1.Level3.net (4.69.163.10) 35.618 ms ae-93-93.csw4.Frankfurt1.Level3.net (4.69.163.14) 35.610 ms ae-83-83.csw3.Frankfurt1.Level3.net (4.69.163.10) 35.554 ms
9 ae-4-90.edge5.Frankfurt1.Level3.net (4.69.154.201) 46.021 ms 43.711 ms ae-3-80.edge5.Frankfurt1.Level3.net (4.69.154.137) 35.645 ms
10 xe-0-2-0.mpr1.fra4.de.above.net (64.125.14.5) 35.750 ms 35.734 ms 35.846 ms
11 xe-3-1-0.mpr2.ams5.nl.above.net (64.125.24.102) 36.714 ms 36.777 ms 37.231 ms
12 xe-0-2-0.cr2.lga5.us.above.net (64.125.27.185) 121.623 ms 121.653 ms 121.647 ms
13 xe-0-1-0.mpr2.lga7.us.above.net (64.125.27.117) 121.905 ms 121.889 ms 121.870 ms
14 208.184.35.178.IPYX-067818-004-ZYO.above.net (208.184.35.178) 128.312 ms 128.292 ms 128.358 ms
Nice!
Thank you
http://serverbear.com/benchmark/2013/08/21/PumZZFzf3Xp4yK7Z
Thats a benchmark from one of the 100Mbps OVZ nodes. However we will be rolling out 1Gbps shortly
Last edited by a moderator:
wlanboy
Content Contributer
I would like to see smaller packages too.http://serverbear.com/benchmark/2013/08/21/PumZZFzf3Xp4yK7Z
Thats a benchmark from one of the 100Mbps OVZ nodes. However we will be rolling out 1Gbps shortly
1024 / 512 MB of RAM is just a waste of resources for my small Ruby web services.
Hi,
Sorry seems as if VPSb glitched and didn't post my reply.
Anyways; We won't be sticking with 512MB+ Plans, more on the lines of going up in intervals of 128MB > 256MB > 384MB then to 512MB > 1GB ect. Some of the smaller ones will be offered on a 6/Mo or 12/Mo basis.
I forgot about custom VPS as well..
Reece
Sorry seems as if VPSb glitched and didn't post my reply.
Anyways; We won't be sticking with 512MB+ Plans, more on the lines of going up in intervals of 128MB > 256MB > 384MB then to 512MB > 1GB ect. Some of the smaller ones will be offered on a 6/Mo or 12/Mo basis.
I forgot about custom VPS as well..
Reece
Last edited by a moderator:
According to Jon Biloh, they will be dropping Cogent on September 10th and adding in a lot of Level 3. Hopefully this will resolve all of the routing issues and Buffalo will become a viable location (again). It's still three weeks away, but that's not too much longer.