New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
@ItsChrisG Any Idea on IXReach, London ?? I haven't seen any of My traceroute going through them ever !
Chris, from Hinet Taiwan. Make it like QuadraNet a route to HiNet
From China Telecom to LG:
From LG to China Telecom:
It gets stuck at the fourth hop every time.
Download speed (on a 100Mbps connection):
From OVH Quebec DC to LG
traceroute to 158.69.27.163 (158.69.27.163), 30 hops max, 60 byte packets
1 internal.swiftnode.com (104.255.32.129) [AS63294] 8.195 ms 8.161 ms 8.133 ms
2 mx1.edge.swiftnode.com (104.255.32.254) [AS63294] 0.335 ms 0.246 ms 0.360 ms
3 104.149.1.73 (104.149.1.73) [AS40676] 26.482 ms 26.461 ms 26.452 ms
4 unassigned.psychz.net (107.160.2.125) [AS40676] 0.263 ms 0.350 ms 0.341 ms
5 any2ix.coresite.com (206.72.210.214) [AS14365/AS4039/AS1784] 0.587 ms 0.483 ms
0.644 ms
6 nwk-5-a9.nj.us (198.27.73.165) [AS16276] 60.297 ms 60.209 ms 60.614 ms
7 bhs-g2-a9.qc.ca (192.99.146.101) [AS16276] 69.006 ms 69.017 ms bhs-g2-a9.qc.ca
(198.27.73.207) [AS16276] 68.906 ms
8 bhs-3b-a9.qc.ca (198.27.73.98) [AS16276] 69.018 ms bhs-3a-a9.qc.ca (198.27.73.94) [AS16276] 69.192 ms 69.118 ms
9 ironsteel.igniteservers.com (158.69.27.163) [AS16276] 68.551 ms 68.591 ms 68.632 ms
From: Malaysia, ISP: Celcom;
That's not from OVH to their looking glass, it's the other way around.
From Perth, Australia - iiNet
traceroute to 104.255.32.139 (104.255.32.139), 30 hops max, 38 byte packets 2 xe-0-0-1.cr1.per1.on.ii.net (150.101.33.94) 17.688 ms 16.629 ms 27.661 ms 3 aex.cr1.adl2.on.ii.net (150.101.33.18) 205.662 ms 205.608 ms 206.580 ms 4 ae16.br1.syd4.on.ii.net (150.101.33.188) 227.536 ms 226.909 ms 263.728 ms 5 te0-0-0-0.br1.hkg2.on.ii.net (150.101.33.199) 227.023 ms 227.056 ms 226.922 ms 6 te1-1-0.bdr1.sin1.on.ii.net (150.101.33.222) 204.585 ms 205.672 ms 205.151 ms 7 116.51.27.45 (116.51.27.45) 217.594 ms 218.250 ms 218.690 ms 8 ae-1.r20.sngpsi05.sg.bb.gin.ntt.net (129.250.3.146) 218.168 ms 9 ae-3.r00.sngpsi05.sg.bb.gin.ntt.net (129.250.7.21) 218.234 ms 217.800 ms 10 fe3-18.br01.sin02.pccwbtn.net (63.218.165.101) 210.583 ms 211.031 ms 210.837 ms 11 TenGE0-2-0-9.br03.lax05.pccwbtn.net (63.218.72.186) 320.199 ms 338.762 ms 290.205 ms 12 ae-0.4088.lax.edge.swiftnode.com (104.255.32.14) 290.837 ms 292.410 ms 289.826 ms 13 vc01.dist01.swiftnode.com (104.255.32.255) 331.247 ms 307.069 ms 327.629 ms 14 lg.swiftnode.com (104.255.32.139) 290.361 ms !C 289.603 ms !C 289.970 ms !C
From Vietnam (Viettel ISP)
From LG
The iginiteshit user is not good at helping people, he good at posting sales link spam
on topic, why its not really good from my home AS17451 ? Shouldn't that Asian optimized?
Coming from I'm guessing a 12 year old. How about not spamming this guys thread with nonsense, geez does this forum have spamming rules or are users allowed to carry on like kids.
I don't think there are rules against spamming. If there were you clearly wouldn't be here anymore.
You don't even know how to ping an IP correctly... I bet you'd advertise on your damn site "Lowest pings, guaranteed" and show a ping to 127.0.0.1...
Seriously. Just stop.
Stop what exactly I didn't claim to be an expert nor do I boast on my skills of anything nor do I spam or disrespect / bash other users on this site unlike some people here. I might have misread a few post and posted some offer but no spam. I'm not an expert at SYSADMIN I'm only in my second year of computer science but I do learn daily from this website and users which is why I'm here. None the less their are asshole here who think there so much better than other and bash its just not cool IMO, but I don't take any hard to it nor do I lose sleep over it.
Just my opinion I don't have anything to prove. So with that being said your response probably won't be read by me so feel free to not respond.
Yep, the path via this exchanges is REALLY long and he seems to not have weight set for it (probably unable to do so as it is not his link) - My home ISP is on AMSIX and DECIX yet the route takes crappy HE (via Psychz) as the path is shorter.
Generally also strange to have a Tier1 (NTT) as direct upstream while using a Tier2 (PCCW) and even a Tier3 (Psychz) as well - That network design is very unpredictable, and the x6 FEVVO prepend to Psychz is a nice try but useless to HE connected peers/customers...
Graz, Austria:
from adsl telkom indonesia to LG
from LG to me
timeout because my isp block icmp.
why traffic goes to china telecom not any2ix?
are you located in LA? i'm sure my isp AS1797/AS7713 have direct peering at any2ix
He's definitely located in LA. This is probably exactly why he's running these tests.
Spain to LA
LA to Spain
indonesia comnet plus to LG
from LG to indonesia comnet plus
good, via pccw
Preston, UK
<
pre> C:\Users\G>tracert 104.255.32.139
Tracing route to lg.swiftnode.com [104.255.32.139] over a maximum of 30 hops:
1 5 ms 2 ms <1 ms routerlogin.net [192.168.0.1]
2 10 ms 11 ms 9 ms cpc2-pres14-2-0-gw.pres.cable.virginm.net [80.19
2.156.1]
3 11 ms 9 ms 22 ms pres-core-2a-ae6-617.network.virginmedia.net [80
.0.161.37]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 32 ms 31 ms 31 ms ams2-ic-1-ae0-0.network.virginmedia.net [62.253.188.158]
8 34 ms 38 ms 36 ms TenGE13-2.br02.ams01.pccwbtn.net [80.249.209.37]
9 182 ms 181 ms 179 ms TenGE0-2-0-6.br03.lax05.pccwbtn.net [63.218.72.1
74]
10 203 ms 204 ms 203 ms ae-0.4088.lax.edge.swiftnode.com [104.255.32.14]
11 221 ms 214 ms 214 ms vc01.dist01.swiftnode.com [104.255.32.255]
12 203 ms 203 ms 204 ms lg.swiftnode.com [104.255.32.139]
Trace complete.
From amsterdam UPC
1 10.15.115.129 (10.15.115.129) 6.953 ms 7.236 ms 7.856 ms 2 212.142.61.105 (212.142.61.105) 9.739 ms 9.691 ms 12.805 ms 3 84.116.244.37 (84.116.244.37) 29.491 ms 29.130 ms 30.529 ms 4 84.116.135.182 (84.116.135.182) 9.536 ms 9.557 ms 9.478 ms 5 ge2-11.br01.ams01.pccwbtn.net (63.218.65.33) 11.878 ms 11.057 ms 11.505 ms 6 tenge0-2-0-1.br03.lax05.pccwbtn.net (63.218.72.166) 188.150 ms 189.125 ms 188.494 ms 7 ae-0.4088.lax.edge.swiftnode.com (104.255.32.14) 185.593 ms 184.608 ms 185.783 ms 8 * * * 9 lg.swiftnode.com (104.255.32.139) 186.373 ms 184.970 ms 184.776 ms
@ItsChrisG This is the ugliest route I've seen from Western Canada to LA (typically 40-45ms).
Vancouver -> London -> LA.
Edit:
The reverse:
from AS6830 Liberty Global Operations B.V.
(unitymedia/UPC germany)
@ItsChrisG -
From Denver:
To Denver:
From Monterrey, Mexico, using Axtel optic fiber:
From Cablevision:
Peak 10, Charlotte, North Carolina
Nice IP: 66-187-224-xx
Jakarta (fastnet) To LG
Tracing route to lg.swiftnode.com [104.255.32.139]
over a maximum of 30 hops:
1 22 ms 8 ms 14 ms
2 18 ms 35 ms 19 ms be8-pe04-cg03.fast.net.id [202.73.96.26]
3 14 ms 12 ms 19 ms be8-cg03-pe04.fast.net.id [202.73.96.25]
4 24 ms 36 ms 23 ms lynx-static-116-68-231-201.lynx.net.id [116.68.231.201]
5 * 31 ms 38 ms lynx-static-116-68-231-217.lynx.net.id [116.68.231.217]
6 23 ms 23 ms 33 ms 203.208.191.137
7 35 ms * 35 ms 203.208.153.142
8 23 ms 56 ms 68 ms 203.208.152.34
9 67 ms 51 ms 73 ms 203.208.178.170
10 62 ms 56 ms 56 ms 63-218-211-249.static.pccwglobal.net [63.218.211.249]
11 83 ms 212 ms 231 ms TenGE0-2-0-6.br03.lax05.pccwbtn.net [63.218.72.174]
12 225 ms 233 ms 219 ms ae-0.4088.lax.edge.swiftnode.com [104.255.32.14]
13 255 ms 225 ms * vc01.dist01.swiftnode.com [104.255.32.255]
14 * * 213 ms lg.swiftnode.com [104.255.32.139]
Trace complete.
LG to Jakarta
traceroute to 111.95.102.199 (111.95.102.199), 30 hops max, 60 byte packets
1 internal.swiftnode.com (104.255.32.129) [AS63294] 16.225 ms 16.184 ms 16.168 ms
2 mx1.edge.swiftnode.com (104.255.32.254) [AS63294] 0.423 ms 0.492 ms 0.482 ms
3 fe3-29.br01.lax05.pccwbtn.net (63.218.73.133) [AS3491] 2.235 ms 1.942 ms 1.924 ms
4 63-218-72-126.static.pccwglobal.net (63.218.72.126) [AS3491] 0.921 ms TenGE12-1.br01.lax05.pccwbtn.net (63.218.72.158) [AS3491] 1.021 ms 63-218-72-126.static.pccwglobal.net (63.218.72.126) [AS3491] 1.106 ms
5 singtel.ge9-10.br01.lax05.pccwbtn.net (63.218.73.102) [AS3491] 0.534 ms 0.368 ms 0.495 ms
6 203.208.172.185 (203.208.172.185) [AS7473] 0.451 ms 203.208.172.145 (203.208.172.145) [AS7473] 0.366 ms 0.380 ms
7 203.208.183.146 (203.208.183.146) [AS19905] 0.581 ms 203.208.173.161 (203.208.173.161) [AS7473] 172.278 ms 203.208.149.26 (203.208.149.26) [AS7473] 0.519 ms
8 203.208.151.229 (203.208.151.229) [AS19905] 182.669 ms 203.208.171.9 (203.208.171.9) [AS19905] 184.726 ms 203.208.173.73 (203.208.173.73) [AS7473] 193.684 ms
9 203.208.153.110 (203.208.153.110) [AS7473] 184.627 ms 203.208.183.13 (203.208.183.13) [AS19905] 179.403 ms 203.208.152.1 (203.208.152.1) [AS19905] 189.513 ms
10 203.208.158.10 (203.208.158.10) [AS7473] 172.308 ms 203.208.191.138 (203.208.191.138) [AS7473] 173.831 ms 203.208.158.34 (203.208.158.34) [AS7473] 186.358 ms
11 203.208.153.110 (203.208.153.110) [AS7473] 187.328 ms 203.208.152.1 (203.208.152.1) [AS19905] 181.803 ms lynx-static-116-68-231-218.lynx.net.id (116.68.231.218) [AS38569/AS55794] 175.594 ms
12 203.208.191.138 (203.208.191.138) [AS7473] 186.441 ms lynx-static-116-68-231-198.lynx.net.id (116.68.231.198) [AS38569/AS55794] 187.844 ms 203.208.191.138 (203.208.191.138) [AS7473] 190.460 ms
13 lynx-static-116-68-231-218.lynx.net.id (116.68.231.218) [AS38569/AS55794] 187.001 ms be8-pe04-cg03.fast.net.id (202.73.96.26) [AS23700] 200.320 ms lynx-static-116-68-231-218.lynx.net.id (116.68.231.218) [AS38569/AS55794] 195.898 ms
14 * * lynx-static-116-68-231-198.lynx.net.id (116.68.231.198) [AS38569/AS55794] 201.946 ms
15 be8-pe04-cg03.fast.net.id (202.73.96.26) [AS23700] 200.743 ms 197.831 ms 209.811 ms
16 * * *
17 * * *
-- Traceroute timed out --
http://lg.320tb.com/ gives me a time out and 104.255.32.139 times out when pinging. Doesn't seem good
Sorted, worst to best:
› hostcmd OpenNIC "(fgrep syslocation /etc/snmp/snmpd.conf; fping -qc 10 104.255.32.139 2>&1) | tr '\n' ' '" | sort -t/ -rnk8
[OpenNIC] 94.242.57.130 - syslocation Saint Petersburg, Russia 104.255.32.139 : xmt/rcv/%loss = 10/8/20%, min/avg/max = 336/357/360
[OpenNIC] 163.47.20.30 - syslocation Sydney, Australia 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 328/328/329
[OpenNIC] 41.185.78.25 - syslocation Cape Town, South Africa 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 310/315/323
[OpenNIC] 185.65.206.121 - syslocation Istanbul, Turkey 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 293/303/310
[OpenNIC] 163.47.21.44 - syslocation Auckland, New Zealand 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 297/298/298
[OpenNIC] 103.250.184.85 - syslocation Pune, India 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 282/285/292
[OpenNIC] 106.185.41.36 - syslocation Tokyo, Japan 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 254/255/258
[OpenNIC] 46.151.215.199 - syslocation Riyadh, Saudi Arabia 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 245/246/247
[OpenNIC] 193.182.144.83 - syslocation Tel Aviv-Yafo, Israel 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 222/222/222
[OpenNIC] 103.241.0.207 - syslocation Perth, Australia 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 218/220/224
[OpenNIC] 41.215.240.141 - syslocation Cairo, Egypt 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 214/219/227
[OpenNIC] 91.229.79.104 - syslocation Kiev, Ukraine 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 217/217/217
[OpenNIC] 151.236.24.245 - syslocation Hafnarfjordur, Iceland 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 208/216/229
[OpenNIC] 94.46.12.224 - syslocation Lisbon, Portugal 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 208/215/222
[OpenNIC] 95.129.41.126 - syslocation Athens, Greece 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 210/210/210
[OpenNIC] 185.61.149.228 - syslocation Riga, Latvia 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 210/210/211
[OpenNIC] 46.108.39.139 - syslocation Bucharest, Romania 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 201/206/209
[OpenNIC] 176.62.0.26 - syslocation Zagreb, Croatia 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 202/202/203
[OpenNIC] 185.81.165.90 - syslocation Vilnius, Lithuania 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 197/197/197
[OpenNIC] 178.17.170.224 - syslocation Chisinau, Moldova 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 196/197/197
[OpenNIC] 91.247.228.155 - syslocation Oslo, Norway 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 192/192/192
[OpenNIC] 103.25.56.238 - syslocation Adelaide, Australia 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 188/189/191
[OpenNIC] 95.175.99.231 - syslocation Ulvila, Finland 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 188/188/189
[OpenNIC] 212.117.180.145 - syslocation Roost, Luxembourg 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 187/187/188
[OpenNIC] 123.30.137.66 - syslocation Ho Chi Minh City, Viet Nam 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 186/186/187
[OpenNIC] 103.25.202.192 - syslocation Chai Chee, Singapore 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 183/186/192
[OpenNIC] 31.220.5.106 - syslocation Stockholm, Sweden 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 180/181/185
[OpenNIC] 5.134.117.239 - syslocation Madrid, Spain 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 178/178/179
[OpenNIC] 88.82.109.119 - syslocation Balzers, Liechtenstein 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 177/177/177
[OpenNIC] 192.121.47.47 - syslocation Milan, Italy 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 176/176/177
[OpenNIC] 151.236.10.36 - syslocation Vienna, Austria 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 174/174/175
[OpenNIC] 79.133.43.124 - syslocation Vienna, Austria 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 171/171/172
[OpenNIC] 62.141.38.230 - syslocation Dusseldorf, Germany 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 170/171/171
[OpenNIC] 84.200.83.161 - syslocation Frankfurt, Germany 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 169/170/179
[OpenNIC] 37.235.55.46 - syslocation Douglas, Isle of Man 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 164/167/172
[OpenNIC] 192.121.170.22 - syslocation Zurich, Switzerland 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 167/167/169
[OpenNIC] 78.47.34.12 - syslocation Falkenstein, Germany 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 166/166/166
[OpenNIC] 185.112.156.159 - syslocation Budapest, Hungary 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 166/166/166
[OpenNIC] 217.78.6.191 - syslocation Dublin, Ireland 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 157/165/217
[OpenNIC] 192.71.249.83 - syslocation Oostkamp, Belgium 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 158/163/171
[OpenNIC] 185.97.7.7 - syslocation Frankfurt, Germany 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 162/162/162
[OpenNIC] 93.158.205.94 - syslocation Amsterdam, Netherlands 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 161/161/161
[OpenNIC] 92.222.80.28 - syslocation Strasbourg, France 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 158/158/158
[OpenNIC] 111.223.227.125 - syslocation Melbourne, Australia 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 158/158/158
[OpenNIC] 74.207.232.103 - syslocation Atlanta, USA 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 155/156/161
[OpenNIC] 31.220.43.191 - syslocation Amsterdam, Netherlands 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 156/156/157
[OpenNIC] 178.79.174.162 - syslocation London, England 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 150/156/163
[OpenNIC] 103.53.199.71 - syslocation Tsuen Wan, Hong Kong 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 155/155/157
[OpenNIC] 185.99.132.5 - syslocation Auckland, New Zealand 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 132/132/133
[OpenNIC] 104.245.39.112 - syslocation Orlando, USA 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 91.4/91.4/91.6
[OpenNIC] 104.237.136.225 - syslocation Dallas, USA 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 90.7/91.1/91.8
[OpenNIC] 104.237.144.172 - syslocation Newark, USA 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 81.5/81.6/81.8
[OpenNIC] 69.28.67.83 - syslocation Toronto, Canada 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 65.0/65.1/65.4
[OpenNIC] 104.219.55.89 - syslocation Dallas, USA 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 60.5/60.7/60.9
[OpenNIC] 104.245.33.185 - syslocation San Francisco, USA 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 30.1/30.3/30.4
[OpenNIC] 74.207.241.202 - syslocation Fremont, USA 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 29.1/29.2/29.3
[OpenNIC] 23.226.230.72 - syslocation Seattle, United States 104.255.32.139 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 29.0/29.2/29.6