To those with hiccups, connection drops, etc in Sabah/Sarawak..
I have this same experiences occasionally when using direct connection.
I now re-route all connections to Europe through Mumbai via VPN server and..
I have not the fastest connection through VPN only 20Mbps via Mumbai but it's stable
and I use backup system to backup all my data from here to servers in EU, Russia
over this connection: 100+GB on a day and no drops or issues.
When I connect directly from KL to Europe I also get drops, lost connection, etc.
But it is weird, as my friends in KL direct connection to Europe have 100Mbps and
on top of that extreme stable!
btw you can all compare connections using tracert
goto windows and type in:
tracert google.co.uk
or
tracert nyt.com
or any server located in US or EU to find about how international connections being routed.
You can specify IPv4 or IPv6 but I always use IPv4 only especially to avoid DNS leaks
In linux you can do this as well:
https://www.computerhope.com/unix/utracero.htmWould be interesting if we all post where we are located:
mainland MY, Sabah, Sarawak and then tracert for example:
tracert 151.101.1.164 (California)
tracert 157.159.10.207 (Paris)
tracert 72.229.28.185 (New York)
tracert 103.15.170.110 (London)
CODE
// Clearly this goes to a mirror in Singapore and not over the ocean.
Tracing route to 151.101.1.164 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 172.22.64.1
2 31 ms 31 ms 31 ms 58.71.245.62
3 * * * Request timed out.
4 39 ms 32 ms 31 ms 58.71.243.49
5 * 32 ms * 58.71.244.246
6 57 ms 32 ms 32 ms 58.71.241.105
7 * * * Request timed out.
8 55 ms 41 ms 41 ms 202.122.151.30
9 37 ms 37 ms 37 ms 54113.sgw.equinix.com [27.111.228.34]
10 37 ms 36 ms 37 ms 151.101.1.164
Trace complete.
CODE
// Clearly this goes through Japan, USA and then to Europe (VERY WEIRD to route 3/4 over the planet instead of 1/4)
tracert 157.159.10.207
Tracing route to 157.159.10.207 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 172.22.64.1
2 45 ms 31 ms 31 ms 58.71.245.62
3 * * * Request timed out.
4 31 ms 31 ms 30 ms 58.71.243.49
5 * * 32 ms 58.71.244.246
6 40 ms 38 ms 31 ms 58.71.241.105
7 * * * Request timed out.
8 * * * Request timed out.
9 31 ms 32 ms 32 ms 172.22.144.146
10 34 ms 32 ms 29 ms ae-9.r20.kslrml02.my.bb.gin.ntt.net [203.78.193.237]
11 76 ms 76 ms 75 ms ae-3.r25.tkokhk01.hk.bb.gin.ntt.net [129.250.2.195]
12 117 ms 118 ms 118 ms ae-7.r24.osakjp02.jp.bb.gin.ntt.net [129.250.2.42]
13 * * * Request timed out.
14 205 ms 206 ms 206 ms ae-11.r04.sttlwa01.us.bb.gin.ntt.net [129.250.2.6]
15 217 ms 218 ms 217 ms ae7.cr4-sea2.ip4.gtt.net [199.229.231.89]
16 336 ms 335 ms 336 ms et-3-3-0.cr4-par7.ip4.gtt.net [213.200.119.214]
17 335 ms 331 ms 331 ms renater-gw-ix1.gtt.net [77.67.123.206]
18 345 ms 344 ms 344 ms te1-1-orsay-rtr-021.noc.renater.fr [193.51.177.120]
19 342 ms 341 ms 342 ms te1-1-evry-rtr-021.noc.renater.fr [193.51.177.102]
20 347 ms 347 ms 346 ms reve-gi8-1-evry-rtr-021.noc.renater.fr [193.51.181.221]
21 351 ms 349 ms 350 ms 195.83.166.162
22 332 ms 333 ms 332 ms int-50-g.reve.fr [194.57.241.204]
23 345 ms 348 ms 345 ms 157.159.8.2
24 335 ms 335 ms 335 ms 157.159.10.207
Trace complete.
CODE
tracert 72.229.28.185
Tracing route to cpe-72-229-28-185.nyc.res.rr.com [72.229.28.185]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.22.64.1
2 31 ms 31 ms 30 ms 58.71.245.62
3 * * * Request timed out.
4 31 ms 31 ms 31 ms 58.71.243.49
5 32 ms 31 ms * 58.71.244.246
6 31 ms 31 ms 62 ms 58.71.241.105
7 * * * Request timed out.
8 41 ms 42 ms 41 ms gi0-2.shtp-pe704.maxis.net.my [202.122.151.198]
9 39 ms 39 ms 39 ms 203.208.148.213
10 37 ms 37 ms 37 ms 203.208.152.82
11 207 ms 208 ms 208 ms 203.208.153.162
12 211 ms 212 ms 211 ms 0.xe-8-3-0.pr0.sjc20.tbone.rr.com [66.109.11.137]
13 296 ms 292 ms 293 ms bu-ether14.snvacaid17w-bcr00.tbone.rr.com [66.109.6.138]
14 288 ms 292 ms 293 ms bu-ether14.chcgildt87w-bcr00.tbone.rr.com [66.109.6.15]
15 289 ms 294 ms 294 ms bu-ether17.atlngamq47w-bcr01.tbone.rr.com [66.109.6.94]
16 294 ms 292 ms 294 ms agg2.nyquny9101r.nyc.rr.com [107.14.19.23]
17 300 ms 299 ms 300 ms agg1.nycynymy02h.nyc.rr.com [68.173.198.43]
18 287 ms 287 ms 288 ms agg2.nycynymy10m.nyc.rr.com [68.173.202.103]
19 * * * Request timed out.
20 363 ms 310 ms 313 ms cpe-72-229-28-185.nyc.res.rr.com [72.229.28.185]
Trace complete.
CODE
// clearly this one is much faster as the one to Paris! This one goes from Singapore straight to UK
tracert 103.15.170.110
Tracing route to ei-web03.ash2.squiz.cloud [103.15.170.110]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.22.64.1
2 32 ms 31 ms 31 ms 58.71.245.62
3 * * * Request timed out.
4 31 ms 32 ms 31 ms 58.71.243.49
5 31 ms 31 ms * 58.71.244.246
6 68 ms 56 ms 36 ms 58.71.241.105
7 * * * Request timed out.
8 * * * Request timed out.
9 32 ms 32 ms 33 ms 172.22.144.146
10 30 ms 34 ms 29 ms ae-9.r20.kslrml02.my.bb.gin.ntt.net [203.78.193.237]
11 34 ms 34 ms 33 ms ae-1.r21.kslrml02.my.bb.gin.ntt.net [129.250.7.43]
12 35 ms 35 ms 35 ms ae-8.r21.sngpsi07.sg.bb.gin.ntt.net [129.250.2.168]
13 193 ms 192 ms 192 ms ae-8.r24.londen12.uk.bb.gin.ntt.net [129.250.7.64]
14 193 ms 192 ms 194 ms ae-1.r04.londen12.uk.bb.gin.ntt.net [129.250.4.126]
15 209 ms 210 ms 209 ms ae-0.a00.londen12.uk.bb.gin.ntt.net [129.250.2.136]
16 206 ms 206 ms 206 ms 81.25.207.166
17 204 ms 204 ms 203 ms v900.thn-br1.orbital.net [80.88.212.56]
18 194 ms 194 ms 194 ms 203.88.80.arpa.orbital.net [80.88.203.6]
19 * * * Request timed out.
20 * * * Request timed out.
21 276 ms 276 ms 285 ms ei-web03.ash2.squiz.cloud [103.15.170.110]
Trace complete.
So in all cases I'm using the Sistem Kabel Rakyat 1Malaysia (SKR1M) always.
Then on Mainland the infrastructure is extreme bad!
CODE
1 <1 ms <1 ms <1 ms 172.22.64.1
2 31 ms 31 ms 30 ms 58.71.245.62
3 * * * Request timed out.
4 31 ms 31 ms 31 ms 58.71.243.49
5 32 ms 31 ms * 58.71.244.246
6 31 ms 31 ms 62 ms 58.71.241.105
7 * * * Request timed out.
8 41 ms 42 ms 41 ms gi0-2.shtp-pe704.maxis.net.my [202.122.151.198]
Why so many hops? My previous fiber internet providers (yes I had several already in various countries)
I had 1: my own router
2: was already the ISP outbound .. that's it.. hop 2 was already non-ISP internet.
Why 8 hops in Malaysia? Don't know, but very ineffective that's for sure!
Anyway, from there the connection to USA and Paris are using the Asia Pacific Gateway (APG)
Why to Paris the Asia Pacific Gateway (APG)??? Doesn't make sense, total garbage to use that cable to get to Paris
Followed by the Japan-U.S. Cable Network (JUS)
and then if going further than USA to Europe the
FLAG Atlantic-1 (FA-1)
but when I going to London.. MUCH faster and more efficient..
We go from KL to Singapore and then
SeaMeWe-5
followed by a connection I haven't been able to identify.
FThis is faster and more efficient..
But also not optimal!!!
Connections Malaysia to Europe (France, London)
could be done by either:
Asia Africa Europe-1 (AAE-1)
or
FLAG Europe-Asia (FEA)
but both TM and Maxis don't use this.
Although that's a DIRECT CONNECTION
from KL to Europe!!!!!
If I wish I could ask someone at TM or Maxis and pay them 100RM a month
just to get routed over these cables.. my speed would be 100+ Mbps to Europe
A technician friend told me it's contracts they make. They make cheap contracts and use the cheapest solution
and if routing via via is cheaper than direct connection you get the less good connection simply because its cheaper
but large corporations they pay more and get the fast connections.
So I really wish if this were an option for end-consumers as well? Pay more for better connections?
This post has been edited by mrgenie: Sep 7 2019, 12:30 PM