All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Bad ping to colocrossing NY from the UK?
linuxthefish
Member
I'm getting very high ping to CC Buffalo over the past few weeks, is this normal or anything my provider can do? Using BlueVM's test IP I get 297ms, but to Chicago I get 117ms...
BlueVM NY:
4 13 ms 13 ms 17 ms 212.140.235.122
5 13 ms 13 ms 12 ms 217.41.169.61
6 41 ms 21 ms 22 ms 217.41.169.107
7 67 ms 18 ms 11 ms acc1-xe-1-2-0.sf.21cn-ipp.bt.net [109.159.251.67]
8 34 ms 23 ms 19 ms core1-te0-0-0-7.ealing.ukcore.bt.net [109.159.251.31]
9 18 ms 19 ms 31 ms peer2-xe-1-0-0.redbus.ukcore.bt.net [109.159.254.90]
10 23 ms 21 ms 19 ms 195.99.126.107
11 27 ms 34 ms 71 ms eth1-1.core1.lon2.uk.as5580.net [78.152.44.92]
12 105 ms 99 ms 99 ms eth1-2.edge1.nyc4.us.as5580.net [80.94.64.134]
13 138 ms 126 ms 124 ms 78.152.57.111
14 219 ms 222 ms 108 ms 10ge-1-3-0.01-02.er1.buf1.colocrossing.com [192.3.138.22]
15 130 ms 129 ms 134 ms 10ge-2.02-c50.buf1.colocrossing.com [192.3.207.26]
16 108 ms 116 ms 118 ms 198.46.142.3
BlueVM Chicago:
5 13 ms 12 ms 15 ms 217.41.169.61
6 15 ms 14 ms 12 ms 217.41.169.107
7 16 ms 18 ms 20 ms acc1-xe-0-2-0.sf.21cn-ipp.bt.net [109.159.251.65]
8 34 ms 22 ms 25 ms core2-te-0-13-0-10.ilford.ukcore.bt.net [109.159.251.183]
9 19 ms 26 ms 22 ms peer3-te-0-4-0-14.telehouse.ukcore.bt.net [109.159.252.57]
10 19 ms 28 ms 50 ms 166-49-211-248.eu.bt.net [166.49.211.248]
11 22 ms 36 ms 24 ms 82.112.101.73
12 28 ms 27 ms 35 ms ae-6.r22.londen03.uk.bb.gin.ntt.net [129.250.4.20]
13 94 ms 100 ms 93 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.126]
14 97 ms 107 ms 104 ms ae-0.r23.nycmny01.us.bb.gin.ntt.net [129.250.3.73]
15 137 ms 114 ms 129 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.40]
16 122 ms 134 ms 117 ms ae-1.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.146]
17 119 ms 121 ms 112 ms ae-0.server-central.chcgil09.us.bb.gin.ntt.net [129.250.202.134]
18 125 ms 112 ms 107 ms ae11.cr1.ord6.us.scnet.net [204.93.204.73]
19 164 ms 114 ms 108 ms 71.ae1.ar1.ord6.us.scnet.net [204.93.204.153]
20 116 ms 109 ms 116 ms as36352.xe-0-1-0.ar1.ord6.us.scnet.net [50.31.170.122]
21 109 ms 117 ms 113 ms 10ge-1.ip99.chi1.colocrossing.com [66.225.231.50]
22 137 ms 117 ms 126 ms 192.210.211.231
In the past few traceroutes there always seems to be an IP belonging to Atrato IP Networks that slows everything down to NY, in this case it's 78.152.57.111.
Comments
So they lied?
3 problems
1, BT is a crap ISP and oversold and priorities certain traffic over others
2, Your first hop ping is rather high
colocrossing is a crappy ISP
ColoCrossing:
HOST: N40L Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.0.1 0.0% 10 0.7 0.7 0.6 0.8 0.0 2.|-- cpc17-****-2-0-gw.7-4.ca 0.0% 10 10.2 15.1 8.2 43.1 10.6 3.|-- ****-core-1a-ae3-1390.net 0.0% 10 10.4 10.1 8.6 11.9 0.9 4.|-- popl-bb-1b-xe-4111-0.netw 0.0% 10 9.7 15.1 7.6 47.4 11.7 5.|-- popl-bb-2a-ae2-0.network. 0.0% 10 48.3 17.4 9.4 48.3 13.3 6.|-- nrth-bb-2a-ae0-0.network. 0.0% 10 12.9 20.5 10.6 56.6 15.0 7.|-- nrth-bb-2b-ae1-0.network. 0.0% 10 15.1 24.0 12.5 60.1 14.0 8.|-- leed-bb-2a-ae1-0.network. 0.0% 10 24.4 18.9 14.4 24.4 3.7 9.|-- leed-bb-1c-ae0-0.network. 0.0% 10 14.8 21.2 14.0 46.3 9.6 10.|-- teln-ic-2-ae1-0.network.v 0.0% 10 24.5 21.0 19.0 24.7 2.1 11.|-- ve1011.r1.lon1.uk.atrato. 0.0% 10 32.2 29.9 20.7 46.9 9.1 12.|-- eth2-6.core1.lon2.uk.as55 0.0% 10 19.3 21.5 18.5 27.3 3.1 13.|-- eth1-2.edge1.nyc4.us.as55 0.0% 10 112.0 106.7 100.1 116.6 5.5 14.|-- 78.152.57.87 10.0% 10 223.2 210.4 181.9 223.2 14.6 15.|-- 10ge-1-3-0.01-01.er2.buf1 0.0% 10 126.9 140.3 109.7 224.3 43.6 16.|-- 10ge-1.02-c50.buf1.colocr 10.0% 10 223.3 214.0 182.1 234.0 17.0 17.|-- 198.46.142.3 10.0% 10 223.7 247.3 206.3 404.6 60.8Choopa:
HOST: N40L Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.0.1 0.0% 10 0.7 0.7 0.7 0.7 0.0 2.|-- cpc17-****-2-0-gw.7-4.ca 0.0% 10 8.1 13.1 8.1 25.5 6.5 3.|-- ****-core-1a-ae3-1390.net 0.0% 10 8.3 9.0 7.3 12.1 1.6 4.|-- ****-core-1b-ge-100-0.net 0.0% 10 8.9 12.8 7.7 24.7 4.7 5.|-- nrth-bb-1b-xe-206-0.netwo 0.0% 10 13.8 23.4 12.2 67.9 16.2 6.|-- ae0.lon11.ip4.gtt.net 0.0% 10 18.0 15.2 10.5 29.1 5.3 7.|-- xe-1-2-3.nyc39.ip4.gtt.ne 0.0% 10 81.9 84.3 81.4 94.8 4.1 8.|-- gtt-gw.ip4.gtt.net 0.0% 10 83.4 85.3 81.4 89.8 3.3 9.|-- ae1-50g.ar1.nyc3.us.as443 0.0% 10 89.3 89.2 85.1 93.6 2.4 10.|-- as20473.ae7.ar1.nyc3.us.a 0.0% 10 93.9 89.2 83.2 95.2 4.5 11.|-- ethernet1-50-c3-9-c6-1.pn 0.0% 10 92.8 86.5 83.4 92.8 3.0 12.|-- www.choopa.com 0.0% 10 87.8 86.9 83.9 91.2 2.4It's just Atrato being amazing that is (no just really cheap and bad in EU especially)
Probably issues on the Bluevm test machine, @linuxthefish.
@udk please pm me your ip address there might be a return path issue there.
@jbiloh - It's still the same on the CC test IP's and my GVH box
(
traceroute to 198.12.69.74 (198.12.69.74), 30 hops max, 60 byte packets1 134.ip-92-222-172.eu (92.222.172.134) 0.236 ms 0.163 ms 0.094 ms
2 178.33.100.139 (178.33.100.139) 1.314 ms 1.332 ms 1.369 ms
3 fra-5-6k.fr.eu (91.121.128.124) 3.085 ms * *
4 ve500.r1.fra1.de.atrato.net (80.81.195.66) 6.290 ms 10.986 ms 6.233 ms
5 eth13-1.core1.par2.fr.as5580.net (78.152.44.244) 19.359 ms 19.329 ms 19.297 ms
6 eth7-1.core1.lon2.uk.as5580.net (78.152.44.242) 18.498 ms 18.107 ms 18.002 ms
7 eth1-2.edge1.nyc4.us.as5580.net (80.94.64.134) 167.794 ms 167.803 ms 167.596 ms
8 78.152.57.111 (78.152.57.111) 172.976 ms 78.152.57.87 (78.152.57.87) 274.682 ms 274.423 ms
9 10ge-1-2-0.01-02.er1.buf1.colocrossing.com (23.94.31.14) 180.965 ms 10ge-1-3-0.01-01.er2.buf1.colocrossing.com (75.127.11.230) 277.644 ms 175.618 ms
10 10ge-1.01-c24.buf1.colocrossing.com (198.12.69.74) 180.226 ms 180.417 ms 180.620 ms
Ok pm me your ip let me take a look.
Jacks-MacBook-Air:~ jack***$ traceroute 198.46.142.3 traceroute to 198.46.142.3 (198.46.142.3), 64 hops max, 52 byte packets 1 109.202.244.1 (109.202.244.1) 3.448 ms 1.457 ms 1.410 ms 2 5.151.250.49 (5.151.250.49) 8.517 ms 12.041 ms 10.067 ms 3 po2.csw0.thdo.as42689.net (77.244.129.94) 11.788 ms 12.060 ms 14.591 ms 4 ten2-1.br0.rbsov.as42689.net (77.244.129.78) 9.251 ms 10.080 ms 9.110 ms 5 tge2-1-506.edge1.lon2.uk.as5580.net (195.66.237.111) 15.409 ms 36.688 ms 26.461 ms 6 eth1-1.core1.lon2.uk.as5580.net (78.152.44.92) 8.921 ms 12.203 ms 9.341 ms 7 eth1-2.edge1.nyc4.us.as5580.net (80.94.64.134) 90.190 ms 95.423 ms 95.099 ms 8 78.152.57.87 (78.152.57.87) 212.818 ms * 211.559 ms 9 10ge-1-3-0.01-01.er2.buf1.colocrossing.com (75.127.11.230) 213.154 ms 10ge-1-2-0.01-02.er1.buf1.colocrossing.com (23.94.31.14) 211.953 ms 10ge-1-3-0.01-02.er1.buf1.colocrossing.com (192.3.138.22) 216.096 ms 10 10ge-1.02-c50.buf1.colocrossing.com (198.23.151.74) 218.399 ms 10ge-2.02-c50.buf1.colocrossing.com (192.3.207.26) 213.308 ms * 11 198.46.142.3 (198.46.142.3) 98.477 ms 124.462 ms 107.411 msJacks-MacBook-Air:~ jack***$ traceroute 192.210.211.231 traceroute to 192.210.211.231 (192.210.211.231), 64 hops max, 52 byte packets 1 109.202.244.1 (109.202.244.1) 1.903 ms 2.918 ms 2.259 ms 2 5.151.250.49 (5.151.250.49) 10.110 ms 13.916 ms 8.501 ms 3 po2.csw0.thdo.as42689.net (77.244.129.94) 13.540 ms 9.770 ms 9.061 ms 4 ten2-1.br0.rbsov.as42689.net (77.244.129.78) 18.819 ms 12.651 ms 8.974 ms 5 cr0-g2-13.thdo.bogons.net (93.186.33.33) 10.808 ms 10.612 ms 11.489 ms 6 83.231.233.185 (83.231.233.185) 9.736 ms 9.625 ms 10.142 ms 7 ae-2.r22.londen03.uk.bb.gin.ntt.net (129.250.2.77) 9.827 ms 9.787 ms 13.618 ms 8 ae-4.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.126) 91.020 ms 84.092 ms 81.170 ms 9 ae-0.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.73) 87.998 ms 80.315 ms 84.164 ms 10 ae-3.r20.chcgil09.us.bb.gin.ntt.net (129.250.2.40) 106.470 ms 106.018 ms 98.201 ms 11 ae-1.r06.chcgil09.us.bb.gin.ntt.net (129.250.4.146) 98.988 ms 104.834 ms 106.929 ms 12 ae-0.gtt-offnet.chcgil09.us.bb.gin.ntt.net (129.250.193.2) 130.574 ms 107.423 ms 119.991 ms 13 ae11.cr1.ord6.us.scnet.net (204.93.204.73) 109.629 ms 105.823 ms ae4.cr1.ord6.us.scnet.net (204.93.204.85) 112.393 ms 14 71.ae1.ar2.ord6.us.scnet.net (204.93.204.157) 102.161 ms 71.ae1.ar1.ord6.us.scnet.net (204.93.204.153) 106.555 ms 117.752 ms 15 as36352.xe-2-1-3.ar2.ord6.us.scnet.net (50.31.154.182) 110.896 ms as36352.xe-0-1-0.ar2.ord6.us.scnet.net (50.31.170.126) 110.666 ms as36352.xe-0-1-0.ar1.ord6.us.scnet.net (50.31.170.122) 109.612 ms 16 10ge-1.ip99.chi1.colocrossing.com (66.225.231.50) 102.309 ms 108.662 ms 10ge-2.ip99.chi1.colocrossing.com (96.8.112.166) 102.252 ms 17 192.210.211.231 (192.210.211.231) 100.652 ms 112.459 ms 108.749 ms Jacks-MacBook-Air:~ jack***$As @TarZZ92 says BT is really bad for DSL services. I have two DSL providers at home, BT and Yomura. BT seems to almost always hit Cogent for transatlantic traffic. I see to your IP its hits Atrato/Hibernia, in my experience ANYTHING that goes over Atrato's network is congested, heavy packet reordering or sometimes packet loss. This is not a reflection on Hibernia's network which has been rocksolid for us for 3 years but they are not providing IP but SDH/Wavelength services.
There is a return path issue with your route. We are working on this to correct it.
Just an FYI - I don't see 198.46.140.0/22 announced over Telia. Telia London is passing traffic via Atrato and Level 3 is passing it via XO.
CC Buffalo only has Atrato ATM, IIRC.
@serverian - they also have XO at a minimum.
Probably for failure, yeah. I have not seen any other route than Atrato for the last few months, though.
That's not true. If you look at routes you'll see about 40% of traffic flows over to XO right now. About 20% over Zayo and then the balance over Atrato.
Latency (from virgin media UK) has greatly improved now
Should be fixed now, thanks for pointing this out to us.
Much better now cheers, 110ms.
Hibernia had issues?
You should be surprised if they do NOT have issues.
Maybe I am missing something but the longest round trip I see from your traceroute is 118 ms ....
Hahahahaha! They had their blips.. But getting better nonetheless.
Closed at the request of the thread starter.