IPv6 discussions

Mach3.2

Great Supremacy Member
Joined
Apr 8, 2011
Messages
72,403
Reaction score
2,459
Oh that's certainly new, but makes sense considering the level of load that 5G users would put on the CGNAT gateways. Is it only enabled on 5G? Or does it still work if you force it down to 4/3 etc?
When are the apn settings? do they differ from older plans?
same APN name, user name and password as far as i can tell.

After toggling between 4G, 5G NSA and 5G SA, I think IPv6 is only available on the 5G SA network, which could explain why sometimes I get no IPv6 address/connectivity.


The problem you're seeing is because in dual stack mode the iphone won't keep retrying to connect once it has any (legacy *or* v6 connection), so if you go to a location with marginal signal you might find that the legacy negotiation succeeded and the v6 did not. It's likely that you're using dual stack, or dual stack is still offered as a fallback. V6-only negotiation can also happen, but only if the network has NAT64/DNS64.
Yeah I get that, I was checking the cellular interface and it doesn't receive IPv6 addresses on occasions, probably due to the reasons I mentioned above.
 
Last edited:

bert64

Senior Member
Joined
Jan 20, 2020
Messages
1,026
Reaction score
536
First off thanks for the long detailed reply. Many points are what i've already read aand known about and agree with. My exp trying out singtel on ipv6 probabyl left much to be desired (slower overall speed, latancy and responsiveness) but hearing the postiive feedback gonna give it another go when my home switches over to SH. Overall honestly i expected it to have been picked up much faster tbh, but i guess i underestimated how willing msot of our ISPs are in the move to IPv6 many years back.
Yeah singtel until recently only had a tunnel, which is always going to give a poor service as such tunnels were only really intended for very early experimentation.
For point of comparison, starhub also offered an ipv6 tunnel on their old cable network (their fibre network has always had native v6), British Telecom also offered a tunnel service back in 2000.
 

bert64

Senior Member
Joined
Jan 20, 2020
Messages
1,026
Reaction score
536
same APN name, user name and password as far as i can tell.

After toggling between 4G, 5G NSA and 5G SA, I think IPv6 is only available on the 5G SA network, which could explain why sometimes I get no IPv6 address/connectivity.
Newer equipment, and 5G SA requires v6 for voice. While it's possible they could limit it to voice-only, that would be a pretty stupid thing to do and would only increase costs for them.

It would appear then based on the apnic stats, that roughly 3% of users are on 5G SA.

In France the telecoms regulator mandated v6 as a requirement for a 5G license.
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,626
Reaction score
8,491
same APN name, user name and password as far as i can tell.
After toggling between 4G, 5G NSA and 5G SA, I think IPv6 is only available on the 5G SA network, which could explain why sometimes I get no IPv6 address/connectivity.
Yeah I get that, I was checking the cellular interface and it doesn't receive IPv6 addresses on occasions, probably due to the reasons I mentioned above.

For our next SingTel SIM Only Plus recontract, we should be able to get 5G without paying more. And from the reports, Singtel 5G SA coverage has improved by quite a bit.
 

Mach3.2

Great Supremacy Member
Joined
Apr 8, 2011
Messages
72,403
Reaction score
2,459
For our next SingTel SIM Only Plus recontract, we should be able to get 5G without paying more. And from the reports, Singtel 5G SA coverage has improved by quite a bit.
Yeah hopefully they give it to everyone as standard soon. It's a little like the early days of 4G, where they charge you a hamburger every month just to have it. 🤣
 

hwzlite

Master Member
Joined
Jan 27, 2007
Messages
3,018
Reaction score
3,118
Just like our gov now push into 10Gbps i sincerely hope they have ipv6 as a requirement not just pure speed.

Our IMDA had last year PR piece touting digital blueprint for next 5/10years....

imda-digital-connectivity-blueprint-dcb.jpeg


Not even a single mention on IPv6 in their Digital Connectivity Blueprint Report :s22:
 

bert64

Senior Member
Joined
Jan 20, 2020
Messages
1,026
Reaction score
536
First off thanks for the long detailed reply. Many points are what i've already read aand known about and agree with. My exp trying out singtel on ipv6 probabyl left much to be desired (slower overall speed, latancy and responsiveness) but hearing the postiive feedback gonna give it another go when my home switches over to SH. Overall honestly i expected it to have been picked up much faster tbh, but i guess i underestimated how willing msot of our ISPs are in the move to IPv6 many years back.
The other thing to consider is that IPv4 is now actively harmful and is stifling development, and anyone not using IPv6 is contributing towards this.

Go back 20 years and if you set up an ISP you could get enough IPv4 for your customers + growth room, then simply route the addresses to customers. Set up an ISP today and you'l get put on a waiting list (possibly waiting a year or more) for a maximum of 256 addresses. This is not enough for any serious number of customers so you're faced with:
  • Buying more addresses at auction, high cost and you're bidding against giants like Microsoft and Amazon.
  • Use address sharing mechanisms like CGNAT, but then you:
    • Need NAT equipment in addition to the routers (cost+++), NAT in either hardware or software is necessarily much more complex than routing (ie you need to lookup every packet against a state table, store the table in quickly accessible memory etc) so for the same level of throughput you have higher complexity, higher cost and higher energy consumption.
    • Provide an inferior service, which leads to customers being unable to do things which are taken for granted on existing services in developed countries, causing your service to be viewed as second class.
    • CGNAT also increases costs in other ways, for instance forcing traffic to transit (expensive) international links instead of doing local p2p.
  • Most do a combination of both, reserving dedicated addresses for higher paying business customers.
This makes it MUCH more costly to set up an ISP, while still providing an inferior service than incumbent suppliers.
  • In a developing country this means your costs are higher, while your potential revenue is lower because the potential customers have less disposable income. Generally corners are cut in order to meet a price point the local market will take, so you end up with equipment intended for gigabit fibre being used to provide services that are capped to 10mbps so as not to overload the limited NAT capacity etc.
  • In a developed country your service finds it harder to compete because it's seen as inferior and your margins are thinner than incumbents. The incumbents can always force you out of the market by lowering their prices below your cost threshold.
The more things move to IPv6, the less of a harmful impact this has until eventually it goes away entirely - resulting in faster development in developing countries, and increased competition in developed countries.
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,626
Reaction score
8,491
One potential issue with IPv6, maybe this is specific to Singtel that IPv6 routing may be worst than IPv4. One example is to M1 OOkla SpeedTest server which @Mach3.2 already analyzed.

I was revisting the latency to various public DNS servers with filtering and then I can see that IPv6 latency is much worst than IPv4 in some cases. The reason is probably the same as above.
https://forums.hardwarezone.com.sg/...ated-offering-dns-for-security.6938654/page-2

1) One example for Singtel is with family.freedns.controld.com and p4.freedns.controld.com.

@Mach3.2
Please help to test on M1 side to see if you have such issues or not. Thanks.

@firesong
If you got the time, please help to test on Starhub side to see if you have such issues or not. Thanks.

Note: Windows will default to IPv6 when it is available.
Bash:
PS C:\work\speedtest> ping family.freedns.controld.com

Pinging family.freedns.controld.com [2606:1a40::11] with 32 bytes of data:
Reply from 2606:1a40::11: time=179ms
Reply from 2606:1a40::11: time=286ms
Reply from 2606:1a40::11: time=176ms
Reply from 2606:1a40::11: time=191ms

Ping statistics for 2606:1a40::11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 176ms, Maximum = 286ms, Average = 208ms
PS C:\work\speedtest> ping -4 family.freedns.controld.com

Pinging family.freedns.controld.com [76.76.2.11] with 32 bytes of data:
Reply from 76.76.2.11: bytes=32 time=3ms TTL=51
Reply from 76.76.2.11: bytes=32 time=6ms TTL=51
Reply from 76.76.2.11: bytes=32 time=6ms TTL=51
Reply from 76.76.2.11: bytes=32 time=4ms TTL=51

Ping statistics for 76.76.2.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 6ms, Average = 4ms

PS C:\work\speedtest> ping p4.freedns.controld.com

Pinging p4.freedns.controld.com [2606:1a40::11] with 32 bytes of data:
Reply from 2606:1a40::11: time=189ms
Request timed out.
Reply from 2606:1a40::11: time=175ms
Reply from 2606:1a40::11: time=175ms

Ping statistics for 2606:1a40::11:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 175ms, Maximum = 189ms, Average = 179ms
PS C:\work\speedtest> ping -4 p4.freedns.controld.com

Pinging p4.freedns.controld.com [76.76.2.11] with 32 bytes of data:
Reply from 76.76.2.11: bytes=32 time=3ms TTL=51
Reply from 76.76.2.11: bytes=32 time=6ms TTL=51
Reply from 76.76.2.11: bytes=32 time=6ms TTL=51
Reply from 76.76.2.11: bytes=32 time=6ms TTL=51

Ping statistics for 76.76.2.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 6ms, Average = 5ms

2) For Singtel, IPv6 is also much worse with Cloudflare family DNS.
M1 has no such issues based on the test from Mach3.2.
https://forums.hardwarezone.com.sg/...ns-for-security.6938654/page-2#post-152653883

Bash:
PS C:\work\speedtest> ping -6 family.cloudflare-dns.com

Pinging family.cloudflare-dns.com [2606:4700:4700::1113] with 32 bytes of data:
Reply from 2606:4700:4700::1113: time=193ms
Reply from 2606:4700:4700::1113: time=261ms
Reply from 2606:4700:4700::1113: time=268ms
Request timed out.

Ping statistics for 2606:4700:4700::1113:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 193ms, Maximum = 268ms, Average = 240ms

PS C:\work\speedtest> ping -4 family.cloudflare-dns.com

Pinging family.cloudflare-dns.com [1.0.0.3] with 32 bytes of data:
Reply from 1.0.0.3: bytes=32 time=4ms TTL=54
Reply from 1.0.0.3: bytes=32 time=6ms TTL=54
Reply from 1.0.0.3: bytes=32 time=6ms TTL=54
Reply from 1.0.0.3: bytes=32 time=6ms TTL=54

Ping statistics for 1.0.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 6ms, Average = 5ms
 
Last edited:

Mach3.2

Great Supremacy Member
Joined
Apr 8, 2011
Messages
72,403
Reaction score
2,459
No diff for both

Bash:
                                                 My traceroute  [v0.95]
atlas2 (10.80.30.11) -> family.freedns.controld.com (76.76.2.11)                               2024-06-29T16:57:06+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. _gateway                                                                  0.0%    21    0.1   0.1   0.1   0.3   0.1
 2. 1.192.199.112.unknown.m1.com.sg                                           0.0%    21    2.1   2.5   2.0   2.9   0.3
 3. 204.246.65.202.unknown.m1.com.sg                                          0.0%    21    2.8   2.6   2.2   3.1   0.2
 4. 205.246.65.202.unknown.m1.com.sg                                          0.0%    21    2.7   2.9   1.6  12.5   2.2
 5. 37.246.65.202.unknown.m1.com.sg                                           0.0%    21    3.0   3.7   2.7   5.7   0.7
 6. 221.246.65.202.unknown.m1.com.sg                                          0.0%    20    4.0   3.7   3.4   4.1   0.2
 7. (waiting for reply)
 8. (waiting for reply)
 9. controld-edge1-sin.anycast.net                                            0.0%    20    4.2   3.6   2.7   4.2   0.3
10. freedns.controld.com                                                      0.0%    20    4.1   4.1   3.8   4.5   0.2

                                                 My traceroute  [v0.95]
atlas2 (2401:7400:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx) -> family.freedns.controld.com (2606:1a40::11)2024-06-29T16:56:06+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    33    0.2   0.2   0.1   0.4   0.1
 2. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    32    2.0   2.8   2.0   6.6   0.8
 3. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    32    2.4   2.6   1.9   3.3   0.3
 4. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    32    3.1   4.0   2.4  16.4   2.5
 5. 2401:7400:0:1::a                                                          0.0%    32    2.8   3.2   2.3   7.1   0.8
 6. 2401:7400:0:1::                                                           0.0%    32    2.2   4.6   2.2  24.9   5.1
 7. 2401:7400:0:1::d                                                          0.0%    32    3.9   4.9   3.3  37.1   5.9
 8. 36236.sgw.equinix.com                                                     0.0%    32    4.4   6.0   3.6  38.4   7.0
 9. 2403:2500:300:1::5                                                        0.0%    32   28.9  13.8   4.5 128.1  21.4
10. controld-edge1-sin.anycast.net                                            0.0%    32    4.4   4.5   3.7   5.7   0.4
11. freedns.controld.com                                                      0.0%    32    4.5   4.5   4.0   4.8   0.2

                                                 My traceroute  [v0.95]
atlas2 (10.80.30.11) -> p4.freedns.controld.com (76.76.2.11)                                   2024-06-29T16:58:06+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. _gateway                                                                  0.0%    31    0.2   0.2   0.1   0.4   0.1
 2. 1.192.199.112.unknown.m1.com.sg                                           0.0%    31    2.4   2.6   2.1   3.3   0.2
 3. 204.246.65.202.unknown.m1.com.sg                                          0.0%    31    2.5   3.3   2.1  11.5   2.2
 4. 205.246.65.202.unknown.m1.com.sg                                          0.0%    31    2.5   3.1   1.9  20.0   3.1
 5. 37.246.65.202.unknown.m1.com.sg                                           0.0%    31    2.6   5.3   2.6  19.2   4.1
 6. 221.246.65.202.unknown.m1.com.sg                                          0.0%    31    3.8   3.7   2.9   4.2   0.3
 7. (waiting for reply)
 8. (waiting for reply)
 9. controld-edge1-sin.anycast.net                                            0.0%    30    3.1   3.6   2.9   3.9   0.2
10. freedns.controld.com                                                      0.0%    30    4.2   4.0   3.3   6.1   0.5

                                                 My traceroute  [v0.95]
atlas2 (2401:7400:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx) -> p4.freedns.controld.com (2606:1a40::11)    2024-06-29T16:59:33+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    31    0.3   0.2   0.1   0.3   0.1
 2. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    30    2.5   2.6   1.9   3.3   0.3
 3. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    30    2.7   2.5   1.7   4.4   0.5
 4. 0.0.4.7.1.0.4.2.ip6.arpa                                                  0.0%    30    2.9   3.2   2.2   5.6   0.6
 5. 2401:7400:0:1::a                                                          0.0%    30    3.2   4.2   2.5  25.2   4.1
 6. 2401:7400:0:1::                                                           0.0%    30    3.3   3.8   2.3  14.4   2.6
 7. 2401:7400:0:1::d                                                          0.0%    30    3.6   4.1   3.1  11.2   1.4
 8. 36236.sgw.equinix.com                                                     0.0%    30    4.4   5.1   3.5  22.0   3.4
 9. 2403:2500:300:1::5                                                        0.0%    30   10.4  14.7   4.5  95.8  21.8
10. controld-edge1-sin.anycast.net                                            0.0%    30    4.2   4.6   3.9   7.7   0.7
11. freedns.controld.com                                                      0.0%    30    4.6   4.5   3.9   4.8   0.2

Not saying M1 doesn't experience different routing for IPv4/IPv6 traffic because I most certainly do on occasions.
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,626
Reaction score
8,491

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,626
Reaction score
8,491
MTR to Cloudflare 1.1.1.1 DNS server
Singtel native IPv6 vs IPv4, from my Asus RT-AX86U router.

Bash:
/tmp/home/root# mtr 2606:4700:4700::1111
                                                 My traceroute  [v0.95]
RT-AX86U-2D40 (2400:d802:xxxx::xxxx) -> 2606:4700:4700::1111 (2606:4700:4700::1111)            2024-06-30T12:16:18+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2400:d802:1:606::                                                         0.0%    34    3.4   7.0   2.8  59.9  11.2
 2. 2001:c20:3c00::6                                                          0.0%    34   15.3  12.4   2.6  36.5  10.9
 3. 2001:c20:3c00::7                                                          0.0%    34    2.2   6.0   2.1  47.6  10.9
 4. 2001:c20:0:3::35                                                          0.0%    34   10.7   6.8   2.2  30.4   7.6
 5. 2001:c20:0:3::a                                                           0.0%    34    2.4   2.3   2.0   2.9   0.2
 6. 2001:cb0:2103:2:15::1                                                    93.8%    33   73.1  55.1  37.2  73.1  25.4
 7. 2403:e800:508:300::a2                                                    72.7%    33  197.3 195.9 181.8 241.5  18.4
 8. 2400:cb00:35:3::                                                         53.1%    33  205.5 198.5 190.7 209.0   6.3
 9. one.one.one.one                                                           0.0%    33  201.3 193.8 180.9 218.9   9.8

/tmp/home/root# mtr 1.1.1.1
                                                 My traceroute  [v0.95]
RT-AX86U-2D40 (121.6.xx.xxx) -> 1.1.1.1 (1.1.1.1)                                              2024-06-30T12:18:19+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. bb121-6-xx-254.singnet.com.sg                                             0.0%    17    3.0   4.5   2.9  15.7   3.5
 2. 165.21.193.22                                                             0.0%    17    9.2  10.5   2.1  32.4  11.4
 3. 165.21.193.21                                                             0.0%    17    3.9   2.5   1.6   6.8   1.3
 4. 165.21.138.245                                                           17.6%    17    2.1   3.3   1.9  15.9   3.6
 5. SN-SINQT1-BO403-ae1.singnet.com.sg                                        0.0%    17    2.3   5.0   2.0  20.6   5.6
 6. ip-202-147-32-136.asianetcom.net                                          0.0%    17    2.5   4.8   2.3  34.7   7.7
 7. unknown.telstraglobal.net                                                40.0%    16    3.0   4.2   2.6  13.7   3.6
 8. 162.158.160.149                                                           0.0%    16    3.2   5.7   2.4  35.6   8.1
 9. one.one.one.one                                                           0.0%    16    2.6   2.6   2.3   3.0   0.2
 
Last edited:

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,626
Reaction score
8,491
MTR to ControlD public DNS server ( family.freedns.controld.com)
Singtel native IPv6 vs IPv4, from my Asus RT-AX86U router.

Bash:
/tmp/home/root# mtr 2606:1a40::11
                                                 My traceroute  [v0.95]
RT-AX86U-2D40 (2400:d802:xxxx::xxxx) -> 2606:1a40::11 (2606:1a40::11)                          2024-06-30T12:22:21+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2400:d802:1:606::                                                         0.0%    49    2.9   6.2   2.7  52.8   8.7
 2. 2001:c20:3c00::6                                                          0.0%    49    2.4   2.9   2.2   9.2   1.6
 3. 2001:c20:3c00::7                                                          0.0%    49    4.0   4.1   2.2  42.3   7.0
 4. 2001:c20:0:3::35                                                          0.0%    49    2.8  15.7   2.3  61.1  15.8
 5. 2001:c20:0:3::a                                                           0.0%    49    2.1   2.2   1.9   2.5   0.1
 6. 2001:c10:80:2::a21                                                        0.0%    49    2.4   3.9   2.4  41.7   6.2
 7. 2001:c10:80:2::915                                                        0.0%    49   20.9   7.3   2.7  44.1   8.8
 8. 2001:c10:80:1::37a                                                        0.0%    49  187.8 182.4 176.7 193.1   5.5
 9. (waiting for reply)
10. (waiting for reply)
11. (waiting for reply)
12. 2607:fc50:5000::1:2                                                       0.0%    48  190.9 194.5 181.6 269.4  15.2
13. 2607:fc50:5000::9                                                         2.1%    48  193.2 187.2 181.5 197.3   5.1
14. controld-edge1-lax.anycast.net                                            2.1%    48  172.9 179.1 172.0 187.8   6.2
15. freedns.controld.com                                                      0.0%    48  177.2 182.3 176.5 192.5   5.8

/tmp/home/root# mtr 76.76.2.11
                                                 My traceroute  [v0.95]
RT-AX86U-2D40 (121.6.xx.xxx) -> 76.76.2.11 (76.76.2.11)                                        2024-06-30T12:23:59+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. bb121-6-xx-254.singnet.com.sg                                             0.0%    36    3.0   9.3   2.7  44.6  10.3
 2. 165.21.193.22                                                            31.4%    36    2.3   2.3   2.0   3.0   0.2
 3. 165.21.193.21                                                             0.0%    36   24.2  11.6   1.8  93.4  18.4
 4. 165.21.138.245                                                            8.3%    36   20.0   3.5   2.0  20.0   3.4
 5. SN-SINQT1-BO403-ae1.singnet.com.sg                                        0.0%    36    2.0   2.1   1.7   2.4   0.2
 6. ix-hge-0-0-0-14.ecore3.svq-singapore.as6453.net                          11.1%    36    2.3   2.3   2.1   2.7   0.1
 7. if-be-23-2.ecore2.svq-singapore.as6453.net                               13.9%    36    2.4   2.3   2.1   2.8   0.1
 8. if-bundle-22-2.qcore2.esin4-singapore.as6453.net                          2.9%    35    2.5   2.6   2.1   3.3   0.4
 9. if-bundle-2-2.qcore1.esin4-singapore.as6453.net                          64.7%    35    2.6   2.5   1.9   3.1   0.4
10. ae-0.a03.sngpsi07.sg.bb.gin.ntt.net                                       0.0%    35    2.6   3.3   2.4  20.0   3.0
11. (waiting for reply)
12. (waiting for reply)
13. controld-edge1-sin.anycast.net                                            0.0%    35    2.3   2.2   2.0   2.8   0.1
14. freedns.controld.com                                                      0.0%    35    2.3   2.4   2.2   2.7   0.1
 

seowbin

Great Supremacy Member
Joined
Oct 10, 2001
Messages
72,594
Reaction score
1,438
Not bad. Seems like there's improvement from singtel to cloudflare ? Last time must go via HK?
 

xiaofan

High Supremacy Member
Joined
Sep 16, 2018
Messages
30,626
Reaction score
8,491
Not bad. Seems like there's improvement from singtel to cloudflare ? Last time must go via HK?

Yes, Singtel IPv4 to Cloudflare is now quite good, last time it was like 30ms to 40ms, now down to about 3ms.

IPv4 ping tests to Google DNS, Cloudflare DNS, Quad9 DNS vs SIngtel's own DNS servers

Bash:
ASUSWRT-Merlin RT-AX86U 3004.388.7_0 Fri Apr 26 18:22:46 UTC 2024

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=3.06 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=3.08 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=2.98 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=3.27 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.979/3.097/3.271/0.107 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 1.1.1.1 -c 4
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=2.67 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=2.53 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=2.72 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=2.72 ms

--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.531/2.661/2.722/0.077 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 9.9.9.9 -c 4
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=55 time=2.00 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=55 time=2.29 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=55 time=2.06 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=55 time=2.08 ms

--- 9.9.9.9 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 1.998/2.106/2.289/0.109 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 165.21.83.88 -c 4
PING 165.21.83.88 (165.21.83.88) 56(84) bytes of data.
64 bytes from 165.21.83.88: icmp_seq=1 ttl=250 time=2.06 ms
64 bytes from 165.21.83.88: icmp_seq=2 ttl=250 time=2.14 ms
64 bytes from 165.21.83.88: icmp_seq=3 ttl=250 time=2.23 ms
64 bytes from 165.21.83.88: icmp_seq=4 ttl=250 time=2.30 ms

--- 165.21.83.88 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 2.056/2.179/2.302/0.092 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 165.21.100.88 -c 4
PING 165.21.100.88 (165.21.100.88) 56(84) bytes of data.
64 bytes from 165.21.100.88: icmp_seq=1 ttl=250 time=2.82 ms
64 bytes from 165.21.100.88: icmp_seq=2 ttl=250 time=2.70 ms
64 bytes from 165.21.100.88: icmp_seq=3 ttl=250 time=2.52 ms
64 bytes from 165.21.100.88: icmp_seq=4 ttl=250 time=2.78 ms

--- 165.21.100.88 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.518/2.706/2.821/0.116 ms
 
Last edited:

Mach3.2

Great Supremacy Member
Joined
Apr 8, 2011
Messages
72,403
Reaction score
2,459
Not bad. Seems like there's improvement from singtel to cloudflare ? Last time must go via HK?
Not all probes getting better latency to Cloudflare, but was better as compared to half a month ago.


AS3758: https://atlas.ripe.net/measurements/74591934/results
AS9506: https://atlas.ripe.net/measurements/74591979/results

Half a mth ago:
https://atlas.ripe.net/measurements/71332243/results

Aslo interesting that there are probes on AS3758. Doesn't singtel fibre customers get allocated an IP under AS9506?

Edit: AS3758 is likely to be biz internet.
 
Last edited:

joeltng

Member
Joined
Dec 29, 2010
Messages
369
Reaction score
25
Yes, Singtel IPv4 to Cloudflare is now quite good, last time it was like 30ms to 40ms, now down to about 3ms.

IPv4 ping tests to Google DNS, Cloudflare DNS, Quad9 DNS vs SIngtel's own DNS servers

Bash:
ASUSWRT-Merlin RT-AX86U 3004.388.7_0 Fri Apr 26 18:22:46 UTC 2024

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=3.06 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=3.08 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=2.98 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=3.27 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.979/3.097/3.271/0.107 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 1.1.1.1 -c 4
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=2.67 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=2.53 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=2.72 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=2.72 ms

--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.531/2.661/2.722/0.077 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 9.9.9.9 -c 4
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=55 time=2.00 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=55 time=2.29 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=55 time=2.06 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=55 time=2.08 ms

--- 9.9.9.9 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 1.998/2.106/2.289/0.109 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 165.21.83.88 -c 4
PING 165.21.83.88 (165.21.83.88) 56(84) bytes of data.
64 bytes from 165.21.83.88: icmp_seq=1 ttl=250 time=2.06 ms
64 bytes from 165.21.83.88: icmp_seq=2 ttl=250 time=2.14 ms
64 bytes from 165.21.83.88: icmp_seq=3 ttl=250 time=2.23 ms
64 bytes from 165.21.83.88: icmp_seq=4 ttl=250 time=2.30 ms

--- 165.21.83.88 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 2.056/2.179/2.302/0.092 ms

xiaofan@RT-AX86U-2D40:/tmp/home/root# ping 165.21.100.88 -c 4
PING 165.21.100.88 (165.21.100.88) 56(84) bytes of data.
64 bytes from 165.21.100.88: icmp_seq=1 ttl=250 time=2.82 ms
64 bytes from 165.21.100.88: icmp_seq=2 ttl=250 time=2.70 ms
64 bytes from 165.21.100.88: icmp_seq=3 ttl=250 time=2.52 ms
64 bytes from 165.21.100.88: icmp_seq=4 ttl=250 time=2.78 ms

--- 165.21.100.88 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.518/2.706/2.821/0.116 ms
my ping to cloud flare still 30-40ms. With no real solid evidence (just my own ep, It feels like Singtel has different routing for each of their different public IPs for whatever reason. Own (admitedly not scientific or controlled) exp was that I used to have lower ms pings to cloud flare, but ever since I got a new IP its mbeen 30-40ms and routing to certian Local game server (namely Apex Legends SG server) has been severely affected. (talking about 200ms ping or ping spikes randomly up to 200ms)
 
Last edited:

bert64

Senior Member
Joined
Jan 20, 2020
Messages
1,026
Reaction score
536
MTR to ControlD public DNS server ( family.freedns.controld.com)
Singtel native IPv6 vs IPv4, from my Asus RT-AX86U router.

Bash:
/tmp/home/root# mtr 2606:1a40::11
                                                 My traceroute  [v0.95]
RT-AX86U-2D40 (2400:d802:xxxx::xxxx) -> 2606:1a40::11 (2606:1a40::11)                          2024-06-30T12:22:21+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 2400:d802:1:606::                                                         0.0%    49    2.9   6.2   2.7  52.8   8.7
 2. 2001:c20:3c00::6                                                          0.0%    49    2.4   2.9   2.2   9.2   1.6
 3. 2001:c20:3c00::7                                                          0.0%    49    4.0   4.1   2.2  42.3   7.0
 4. 2001:c20:0:3::35                                                          0.0%    49    2.8  15.7   2.3  61.1  15.8
 5. 2001:c20:0:3::a                                                           0.0%    49    2.1   2.2   1.9   2.5   0.1
 6. 2001:c10:80:2::a21                                                        0.0%    49    2.4   3.9   2.4  41.7   6.2
 7. 2001:c10:80:2::915                                                        0.0%    49   20.9   7.3   2.7  44.1   8.8
 8. 2001:c10:80:1::37a                                                        0.0%    49  187.8 182.4 176.7 193.1   5.5
 9. (waiting for reply)
10. (waiting for reply)
11. (waiting for reply)
12. 2607:fc50:5000::1:2                                                       0.0%    48  190.9 194.5 181.6 269.4  15.2
13. 2607:fc50:5000::9                                                         2.1%    48  193.2 187.2 181.5 197.3   5.1
14. controld-edge1-lax.anycast.net                                            2.1%    48  172.9 179.1 172.0 187.8   6.2
15. freedns.controld.com                                                      0.0%    48  177.2 182.3 176.5 192.5   5.8

/tmp/home/root# mtr 76.76.2.11
                                                 My traceroute  [v0.95]
RT-AX86U-2D40 (121.6.xx.xxx) -> 76.76.2.11 (76.76.2.11)                                        2024-06-30T12:23:59+0800
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. bb121-6-xx-254.singnet.com.sg                                             0.0%    36    3.0   9.3   2.7  44.6  10.3
 2. 165.21.193.22                                                            31.4%    36    2.3   2.3   2.0   3.0   0.2
 3. 165.21.193.21                                                             0.0%    36   24.2  11.6   1.8  93.4  18.4
 4. 165.21.138.245                                                            8.3%    36   20.0   3.5   2.0  20.0   3.4
 5. SN-SINQT1-BO403-ae1.singnet.com.sg                                        0.0%    36    2.0   2.1   1.7   2.4   0.2
 6. ix-hge-0-0-0-14.ecore3.svq-singapore.as6453.net                          11.1%    36    2.3   2.3   2.1   2.7   0.1
 7. if-be-23-2.ecore2.svq-singapore.as6453.net                               13.9%    36    2.4   2.3   2.1   2.8   0.1
 8. if-bundle-22-2.qcore2.esin4-singapore.as6453.net                          2.9%    35    2.5   2.6   2.1   3.3   0.4
 9. if-bundle-2-2.qcore1.esin4-singapore.as6453.net                          64.7%    35    2.6   2.5   1.9   3.1   0.4
10. ae-0.a03.sngpsi07.sg.bb.gin.ntt.net                                       0.0%    35    2.6   3.3   2.4  20.0   3.0
11. (waiting for reply)
12. (waiting for reply)
13. controld-edge1-sin.anycast.net                                            0.0%    35    2.3   2.2   2.0   2.8   0.1
14. freedns.controld.com                                                      0.0%    35    2.3   2.4   2.2   2.7   0.1

In the case of high latency like this, the happy eyeballs algorithm would automatically downgrade to legacy ip.
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ. Forum members and moderators are responsible for their own posts.

Please refer to our Community Guidelines and Standards, Terms of Service and Member T&Cs for more information.
Top