Real International speed tests

What ISP are you testing on?

  • Total voters
    64
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
lobukong said:
Thank you for the info. If Singtel also like that then there's no reason for me to switch. :D
Yes, latency for game(jp, us servers) actually quite good with MyRepublic.
Click to expand...

Yes that is right.

In order to have good latency to China servers, it seems to me China VPN (or using some other VPS as the intermediate) is needed.

I have subscription to AJS China VPN for contents comsumption (720p or 1080p) and it also helps to reduce latency. But usually I do not use it for WeChat call -- nowadays we just use Wechat Voice call more often and only use Wechat Video call occassionally (sometimes it is okay, sometimes it is not okay).

Good thing about Singtel is probably Taobao mobile app (not using Taobao website though), we never really have much issues with that -- quite some reports of issues by MyRepublic and Viewquest users, but I think they tend to use Taobao website (s.taobao.com can be a problem).

Code: 
PS C:\Users\xiaof> ping s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.88] with 32 bytes of data:
Reply from 59.82.9.88: bytes=32 time=174ms TTL=82
Reply from 59.82.9.88: bytes=32 time=175ms TTL=82
Reply from 59.82.9.88: bytes=32 time=273ms TTL=82
Reply from 59.82.9.88: bytes=32 time=182ms TTL=82

Ping statistics for 59.82.9.88:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 174ms, Maximum = 273ms, Average = 201ms
PS C:\Users\xiaof> ping www.taobao.com

Pinging www.taobao.com.danuoyi.tbcache.com [163.181.36.225] with 32 bytes of data:
Reply from 163.181.36.225: bytes=32 time=10ms TTL=54
Reply from 163.181.36.225: bytes=32 time=6ms TTL=54
Reply from 163.181.36.225: bytes=32 time=6ms TTL=54
Reply from 163.181.36.225: bytes=32 time=7ms TTL=54

Ping statistics for 163.181.36.225:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 10ms, Average = 7ms
 
Mach3.2

Mach3.2

Great Supremacy Member
HWZ Insider
Joined
Apr 8, 2011
Messages
72,405
Reaction score
2,466
xiaofan said:
Yes that is right.

In order to have good latency to China servers, it seems to me China VPN (or using some other VPS as the intermediate) is needed.

I have subscription to AJS China VPN for contents comsumption (720p or 1080p) and it also helps to reduce latency. But usually I do not use it for WeChat call -- nowadays we just use Wechat Voice call more often and only use Wechat Video call occassionally (sometimes it is okay, sometimes it is not okay).

Good thing about Singtel is probably Taobao mobile app (not using Taobao website though), we never really have much issues with that -- quite some reports of issues by MyRepublic and Viewquest users, but I think they tend to use Taobao website (s.taobao.com can be a problem).

Code: 
PS C:\Users\xiaof> ping s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.88] with 32 bytes of data:
Reply from 59.82.9.88: bytes=32 time=174ms TTL=82
Reply from 59.82.9.88: bytes=32 time=175ms TTL=82
Reply from 59.82.9.88: bytes=32 time=273ms TTL=82
Reply from 59.82.9.88: bytes=32 time=182ms TTL=82

Ping statistics for 59.82.9.88:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 174ms, Maximum = 273ms, Average = 201ms
PS C:\Users\xiaof> ping www.taobao.com

Pinging www.taobao.com.danuoyi.tbcache.com [163.181.36.225] with 32 bytes of data:
Reply from 163.181.36.225: bytes=32 time=10ms TTL=54
Reply from 163.181.36.225: bytes=32 time=6ms TTL=54
Reply from 163.181.36.225: bytes=32 time=6ms TTL=54
Reply from 163.181.36.225: bytes=32 time=7ms TTL=54

Ping statistics for 163.181.36.225:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 10ms, Average = 7ms
Click to expand...
M1 :s22: :s22:
Bash: 
C:\Users\M>ping -4 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.90] with 32 bytes of data:
Reply from 59.82.9.90: bytes=32 time=392ms TTL=82
Reply from 59.82.9.90: bytes=32 time=391ms TTL=82
Reply from 59.82.9.90: bytes=32 time=392ms TTL=82
Reply from 59.82.9.90: bytes=32 time=392ms TTL=82

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

C:\Users\M>ping -6 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [2401:b180:2000:10::2d] with 32 bytes of data:
Reply from 2401:b180:2000:10::2d: time=404ms
Reply from 2401:b180:2000:10::2d: time=403ms
Reply from 2401:b180:2000:10::2d: time=404ms
Reply from 2401:b180:2000:10::2d: time=404ms

Ping statistics for 2401:b180:2000:10::2d:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 403ms, Maximum = 404ms, Average = 403ms

Over Cloudflare Warp
Bash: 
C:\Users\M>ping -4 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.86] with 32 bytes of data:
Reply from 59.82.9.86: bytes=32 time=243ms TTL=84
Reply from 59.82.9.86: bytes=32 time=243ms TTL=84
Reply from 59.82.9.86: bytes=32 time=243ms TTL=84
Reply from 59.82.9.86: bytes=32 time=246ms TTL=84

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

C:\Users\M>ping -6 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [2401:b180:2000:10::2d] with 32 bytes of data:
Request timed out.
Reply from 2401:b180:2000:10::2d: time=324ms
Reply from 2401:b180:2000:10::2d: time=311ms
Reply from 2401:b180:2000:10::2d: time=306ms

Ping statistics for 2401:b180:2000:10::2d:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 306ms, Maximum = 324ms, Average = 313ms

over HE IPv6 TunnelBroker
Bash: 
C:\Users\M>ping -6 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [2401:b180:2000:10::2d] with 32 bytes of data:
Reply from 2401:b180:2000:10::2d: time=395ms
Reply from 2401:b180:2000:10::2d: time=399ms
Reply from 2401:b180:2000:10::2d: time=399ms
Reply from 2401:b180:2000:10::2d: time=397ms

Ping statistics for 2401:b180:2000:10::2d:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 395ms, Maximum = 399ms, Average = 397ms
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
Mach3.2 said:
M1 :s22: :s22:
Bash: 
C:\Users\M>ping -4 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.90] with 32 bytes of data:
Reply from 59.82.9.90: bytes=32 time=392ms TTL=82
Reply from 59.82.9.90: bytes=32 time=391ms TTL=82
Reply from 59.82.9.90: bytes=32 time=392ms TTL=82
Reply from 59.82.9.90: bytes=32 time=392ms TTL=82

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

C:\Users\M>ping -6 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [2401:b180:2000:10::2d] with 32 bytes of data:
Reply from 2401:b180:2000:10::2d: time=404ms
Reply from 2401:b180:2000:10::2d: time=403ms
Reply from 2401:b180:2000:10::2d: time=404ms
Reply from 2401:b180:2000:10::2d: time=404ms

Ping statistics for 2401:b180:2000:10::2d:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 403ms, Maximum = 404ms, Average = 403ms

Over Cloudflare Warp
Bash: 
C:\Users\M>ping -4 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.86] with 32 bytes of data:
Reply from 59.82.9.86: bytes=32 time=243ms TTL=84
Reply from 59.82.9.86: bytes=32 time=243ms TTL=84
Reply from 59.82.9.86: bytes=32 time=243ms TTL=84
Reply from 59.82.9.86: bytes=32 time=246ms TTL=84

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

C:\Users\M>ping -6 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [2401:b180:2000:10::2d] with 32 bytes of data:
Request timed out.
Reply from 2401:b180:2000:10::2d: time=324ms
Reply from 2401:b180:2000:10::2d: time=311ms
Reply from 2401:b180:2000:10::2d: time=306ms

Ping statistics for 2401:b180:2000:10::2d:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 306ms, Maximum = 324ms, Average = 313ms

over HE IPv6 TunnelBroker
Bash: 
C:\Users\M>ping -6 s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [2401:b180:2000:10::2d] with 32 bytes of data:
Reply from 2401:b180:2000:10::2d: time=395ms
Reply from 2401:b180:2000:10::2d: time=399ms
Reply from 2401:b180:2000:10::2d: time=399ms
Reply from 2401:b180:2000:10::2d: time=397ms

Ping statistics for 2401:b180:2000:10::2d:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 395ms, Maximum = 399ms, Average = 397ms
Click to expand...

Looks like M1 is also quite a bit worse than Singtel when it comes to "s.taobao.com". IPv6 does not help either in this case.
 
L

lobukong

Member
Joined
Jun 16, 2011
Messages
361
Reaction score
196
tried to ping s.taobao.com
ping s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.84] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

ping s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.84] with 32 bytes of data:
Reply from 59.82.9.84: bytes=32 time=231ms TTL=83
Reply from 59.82.9.84: bytes=32 time=232ms TTL=83
Reply from 59.82.9.84: bytes=32 time=231ms TTL=83
Reply from 59.82.9.84: bytes=32 time=232ms TTL=83

ping s.taobao.com

ping -t s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.9.88] with 32 bytes of data:
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Request timed out.
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=234ms TTL=83
Reply from 59.82.9.88: bytes=32 time=234ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=230ms TTL=83
Reply from 59.82.9.88: bytes=32 time=230ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=234ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=232ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83
Reply from 59.82.9.88: bytes=32 time=233ms TTL=83

ping s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [106.11.15.99] with 32 bytes of data:
Reply from 106.11.15.99: bytes=32 time=90ms TTL=30
Reply from 106.11.15.99: bytes=32 time=86ms TTL=30
Reply from 106.11.15.99: bytes=32 time=87ms TTL=30
Reply from 106.11.15.99: bytes=32 time=87ms TTL=30

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

ping s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [106.11.15.99] with 32 bytes of data:
Reply from 106.11.15.99: bytes=32 time=86ms TTL=30
Reply from 106.11.15.99: bytes=32 time=86ms TTL=30
Reply from 106.11.15.99: bytes=32 time=93ms TTL=30
Reply from 106.11.15.99: bytes=32 time=87ms TTL=30

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

ping 106.11.15.99

Pinging 106.11.15.99 with 32 bytes of data:
Reply from 106.11.15.99: bytes=32 time=87ms TTL=30
Request timed out.
Reply from 106.11.15.99: bytes=32 time=87ms TTL=30
Reply from 106.11.15.99: bytes=32 time=87ms TTL=30

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

but very seldom will it resolve to 106.11.15.99, probably need to setup something like smartdns?
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
lobukong said:
tried to ping s.taobao.com
59.82.9.84 some packet loss
59.82.9.88 some packet loss
106.11.15.99, 87ms ping also packet loss

but very seldom will it resolve to 106.11.15.99, probably need to setup something like smartdns?
Click to expand...

You can probably try to use local DNS solutions like to set up the hosts file.

For Singtel it seems to me 106.11.15.99 is not good, only 69.82.9.88 is a bit better. The default should be 59.82.9.84 as per nslookup.

Code: 
> nslookup s.taobao.com
Server:  UnKnown
Address:  1.1.1.3

Non-authoritative answer:
Name:    v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com
Addresses:  2401:b180:2000:20::29
          2401:b180:2000:10::2d
          59.82.9.88
Aliases:  s.taobao.com
          v6-sh-sz-zb.wagbridge.alibaba.taobao.com

> ping s.taobao.com

Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [106.11.15.99] with 32 bytes of data:
Reply from 106.11.15.99: bytes=32 time=398ms TTL=86
Reply from 106.11.15.99: bytes=32 time=304ms TTL=86
Reply from 106.11.15.99: bytes=32 time=319ms TTL=86
Reply from 106.11.15.99: bytes=32 time=331ms TTL=86

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

> ping 59.82.9.84

Pinging 59.82.9.84 with 32 bytes of data:
Reply from 59.82.9.84: bytes=32 time=269ms TTL=82
Reply from 59.82.9.84: bytes=32 time=336ms TTL=82
Reply from 59.82.9.84: bytes=32 time=339ms TTL=82
Reply from 59.82.9.84: bytes=32 time=353ms TTL=82

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

> ping 59.82.9.88

Pinging 59.82.9.88 with 32 bytes of data:
Reply from 59.82.9.88: bytes=32 time=188ms TTL=82
Reply from 59.82.9.88: bytes=32 time=189ms TTL=82
Reply from 59.82.9.88: bytes=32 time=196ms TTL=82
Reply from 59.82.9.88: bytes=32 time=200ms TTL=82

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

> ping 59.82.9.86

Pinging 59.82.9.86 with 32 bytes of data:
Reply from 59.82.9.86: bytes=32 time=296ms TTL=82
Reply from 59.82.9.86: bytes=32 time=303ms TTL=82
Reply from 59.82.9.86: bytes=32 time=260ms TTL=82
Reply from 59.82.9.86: bytes=32 time=323ms TTL=82

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

> ping 59.82.9.90

Pinging 59.82.9.90 with 32 bytes of data:
Reply from 59.82.9.90: bytes=32 time=346ms TTL=80
Reply from 59.82.9.90: bytes=32 time=258ms TTL=80
Reply from 59.82.9.90: bytes=32 time=261ms TTL=80
Reply from 59.82.9.90: bytes=32 time=268ms TTL=80

Ping statistics for 59.82.9.90:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 258ms, Maximum = 346ms, Average = 283ms
 
firesong

firesong

Supremacy Member
Deluxe Member
Joined
Jan 17, 2001
Messages
8,650
Reaction score
4,658
Since moving to StarHub. I probably need to update some servers since they have dropped out.

ServerLatencyDownloadUploadLoss
Singtel - Singapore (id = 13623)3.31ms (Jitter = 0.31ms)939.87Mbps (data used: 6.8GB)907.54Mbps (data used: 7.5GB)0.00%
ViewQwest - Singapore (id = 2054)3.67ms (Jitter = 1.ms)912.82Mbps (data used: 8.1GB)905.95Mbps (data used: 13.3GB)0.00%
PT FirstMedia - Singapore (id = 7556)3.78ms (Jitter = 0.1ms)900.9Mbps (data used: 6.6GB)917.87Mbps (data used: 7.0GB)0.00%
Comcast - Sacramento, CA (id = 9436)189.41ms (Jitter = 0.17ms)584.43Mbps (data used: 7.0GB)476.06Mbps (data used: 5.0GB)0.00%
Spectrum - Los Angeles, CA (id = 16974)183.55ms (Jitter = 0.08ms)605.25Mbps (data used: 6.8GB)478.82Mbps (data used: 4.9GB)0.00%
University of Texas, Austin - Austin, TX (id = 16089)215.66ms (Jitter = 0.16ms)297.85Mbps (data used: 3.8GB)457.54Mbps (data used: 4.8GB)0.00%
Optus - Melbourne (id = 30932)309.28ms (Jitter = 0.33ms)497.56Mbps (data used: 6.0GB)418.72Mbps (data used: 5.6GB)0.00%
GLBB Japan - Tokyo (id = 20976)94.75ms (Jitter = 0.41ms)184.44Mbps (data used: 1.8GB)221.28Mbps (data used: 3.0GB)0.00%
SIMPLYCONNECT - Dar es Salaam (id = 13902)258.35ms (Jitter = 0.21ms)7.51Mbps (data used: 0.1GB)5.33Mbps (data used: 0.1GB)0.00%
Celcom Axiata - Kuala Lumpur (id = 4956)13.46ms (Jitter = 0.36ms)827.47Mbps (data used: 7.6GB)823.18Mbps (data used: 9.4GB)N/A
Bell Mobility - Vancouver, BC (id = 17402)154.6ms (Jitter = 0.18ms)780.71Mbps (data used: 9.0GB)577.28Mbps (data used: 7.7GB)0.00%
Telstra International - Hong Kong (id = 44340)42.47ms (Jitter = 0.08ms)831.75Mbps (data used: 11.4GB)774.68Mbps (data used: 11.4GB)0.00%
China Telecom - Shanghai (id = 3633)179.99ms (Jitter = 0.27ms)554.76Mbps (data used: 6.5GB)325.91Mbps (data used: 3.4GB)N/A
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
A bit lazy so using wireless (Singtel 1Gbps plan, Singtel ZTE ONT, Asus RT-AX82U, Acer Windows 11 laptop with Intel AX201 adapter, 3 meters away from router)

Three servers failed. Two servers are significant slower than @firesong's results (Starhub): UT Austin and China Telecom Shanghai.


Server NameServer IDLatencyJitterPacket LossDownload SpeedUpload Speed
Singtel - Singapore136233.45 ms0.15 ms0.00%896.11 Mbps882.04 Mbps
ViewQwest - Singapore20544.33 ms0.54 ms0.00%568.27 Mbps745.0 Mbps
PT FirstMedia - Singapore75563.68 ms0.12 ms0.00%431.79 Mbps871.45 Mbps
Comcast - Sacramento, CA9436185.66 ms27.15 ms0.00%310.77 Mbps374.97 Mbps
Spectrum - Los Angeles, CA16974195.51 ms17.68 ms0.00%267.4 Mbps364.33 Mbps
University of Texas, Austin - Austin, TX16089238.48 ms17.29 ms0.00%96.6 Mbps94.98 Mbps
Optus - Melbourne30932112.44 ms63.16 ms0.00%509.11 Mbps651.78 Mbps
Misaka Network, Inc. - Tokyo4498884.13 ms0.26 ms37.74%663.0 Mbps445.0 Mbps
Celcom Axiata - Kuala Lumpur495678.43 ms0.52 ms0.00%463.46 Mbps633.24 Mbps
Bell Mobility - Vancouver, BC17402306.32 ms51.62 ms0.00%269.21 Mbps118.44 Mbps
Telstra International - Hong Kong4434035.52 ms0.5 ms0.00%365.28 Mbps770.42 Mbps
China Telecom - Shanghai3633334.8 ms56.88 msN/A14.17 Mbps12.65 Mbps
 
firesong

firesong

Supremacy Member
Deluxe Member
Joined
Jan 17, 2001
Messages
8,650
Reaction score
4,658
xiaofan said:
A bit lazy so using wireless (Singtel 1Gbps plan, Singtel ZTE ONT, Asus RT-AX82U, Acer Windows 11 laptop with Intel AX201 adapter, 3 meters away from router)

Three servers failed. Two servers are significant slower than @firesong's results (Starhub): UT Austin and China Telecom Shanghai.
Click to expand...
Interesting results. I was under the impression Singtel had more optimal routes to China. Seems like that's not the case.
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
firesong said:
Interesting results. I was under the impression Singtel had more optimal routes to China. Seems like that's not the case.
Click to expand...

I believe Singtel has better routes to China Mobile, but not necessary China Telecom and China Unicom.

As far as I know, China Mobile has the highest number Internet subscribers in mainland China (cheaper, used to be free with mobile bundle) but often has the lowest performance among the three main telecom providers in terms of Fibre broadband (even though it is the better one in mobile phone). China Telecom is the better on in Southern China and China Unicom is better in Northern China.

Previous test results (but the China Mobile Hangzhou Server ID 4647 is dead now)
https://forums.hardwarezone.com.sg/...nal-speed-tests.6405972/page-9#post-140481611
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
Good China Mobile results

Code: 
PS C:\work\speedtest\ookla-speedtest-1.1.1-win64> .\speedtest -s 4575

   Speedtest by Ookla

     Server: China Mobile Group Sichuan - Chengdu (id = 4575)
        ISP: Singtel Fibre
    Latency:   204.38 ms   (0.54 ms jitter)
   Download:   817.16 Mbps (data used: 1.3 GB )
     Upload:   467.59 Mbps (data used: 788.4 MB )
Packet Loss:     0.0%
 Result URL: https://www.speedtest.net/result/c/17a91949-6c13-47c4-a077-06762a0646a6

PS C:\work\speedtest\ookla-speedtest-1.1.1-win64> .\speedtest -s 15863

   Speedtest by Ookla

     Server: GX ChinaMobile - Nanning (id = 15863)
        ISP: Singtel Fibre
    Latency:    81.60 ms   (1.43 ms jitter)
   Download:   846.67 Mbps (data used: 1.3 GB )
     Upload:   610.69 Mbps (data used: 764.9 MB )
Packet Loss:     0.0%
 Result URL: https://www.speedtest.net/result/c/76dc92c2-5079-4496-93a3-3316a58eef7f

Results from China Telecom and others.

Code: 
PS C:\work\speedtest\ookla-speedtest-1.1.1-win64> .\speedtest -s 35527

   Speedtest by Ookla

     Server: China Broadcasting Network Group Sichuan - Chengdu (id = 35527)
        ISP: Singtel Fibre
    Latency:    89.38 ms   (1.75 ms jitter)
   Download:    12.48 Mbps (data used: 6.6 MB )
     Upload:    25.03 Mbps (data used: 27.9 MB )
Packet Loss: Not available.
 Result URL: https://www.speedtest.net/result/c/6f9635cb-f01a-454c-9691-dc3e1162b587
 
PS C:\work\speedtest\ookla-speedtest-1.1.1-win64> .\speedtest -s 23844

   Speedtest by Ookla

     Server: China Telecom Wuhan Branch - Wuhan (id = 23844)
        ISP: Singtel Fibre
    Latency:   310.91 ms   (47.25 ms jitter)
   Download:     5.92 Mbps (data used: 8.3 MB )
     Upload:     1.23 Mbps (data used: 1.2 MB )
Packet Loss: Not available.
 Result URL: https://www.speedtest.net/result/c/756e287d-9f74-4012-857b-350240638922
 
PS C:\work\speedtest\ookla-speedtest-1.1.1-win64> .\speedtest -s 3633

   Speedtest by Ookla

     Server: China Telecom - Shanghai (id = 3633)
        ISP: Singtel Fibre
    Latency:   404.44 ms   (1.65 ms jitter)
   Download:   104.71 Mbps (data used: 130.6 MB )
     Upload:     1.09 Mbps (data used: 1.9 MB )
Packet Loss: Not available.
 Result URL: https://www.speedtest.net/result/c/054538b2-9e16-45d6-83ac-4df8a3447d26
 
PS C:\work\speedtest\ookla-speedtest-1.1.1-win64> .\speedtest -s 5396

   Speedtest by Ookla

     Server: China Telecom JiangSu 5G - Suzhou (id = 5396)
        ISP: Singtel Fibre
    Latency:   409.33 ms   (0.40 ms jitter)
   Download:   192.83 Mbps (data used: 262.7 MB )
     Upload:   163.93 Mbps (data used: 260.0 MB )
Packet Loss: Not available.
 Result URL: https://www.speedtest.net/result/c/968475e9-0141-47c6-8d3d-d5dafed95317
 
Last edited:
K

ksw2010

Member
Joined
Aug 28, 2010
Messages
298
Reaction score
47
Thanks xiaofan for providing the server details. I follow to retest to confirm my ST line to China. Looks like the speed is acceptable to China for for my home BB line.

C:\Speedtest>speedtest -s 3633

Speedtest by Ookla

Server: China Telecom - Shanghai (id = 3633)
ISP: Singtel Fibre
Latency: 205.25 ms (328.91 ms jitter)
Download: 588.09 Mbps (data used: 942.8 MB )
Upload: 0.67 Mbps (data used: 985.6 kB )
Packet Loss: Not available.
Result URL: https://www.speedtest.net/result/c/77f2b462-ddf6-4922-a64d-351f77efd3b6


C:\Speedtest>speedtest -s 35527

Speedtest by Ookla

Server: China Broadcasting Network Group Sichuan - Chengdu (id = 35527)
ISP: Singtel Fibre
Latency: 106.71 ms (4.30 ms jitter)
Download: 718.44 Mbps (data used: 980.1 MB )
Upload: 9.35 Mbps (data used: 13.4 MB )
Packet Loss: Not available.
Result URL: https://www.speedtest.net/result/c/d78a4252-9c30-47ae-88d4-c5cf8f66ea3a

C:\Speedtest>speedtest -s 23844

Speedtest by Ookla

Server: China Telecom Wuhan Branch - Wuhan (id = 23844)
ISP: Singtel Fibre
Latency: 211.59 ms (0.14 ms jitter)
Download: 138.19 Mbps (data used: 173.1 MB )
Upload: 1.13 Mbps (data used: 1.3 MB )
Packet Loss: Not available.
Result URL: https://www.speedtest.net/result/c/6910b9c9-8427-48f0-9cc5-334ddda12524

C:\Speedtest>speedtest -s 5396

Speedtest by Ookla

Server: China Telecom JiangSu 5G - Suzhou (id = 5396)
ISP: Singtel Fibre
Latency: 345.86 ms (0.28 ms jitter)
Download: 307.73 Mbps (data used: 394.1 MB )
Upload: 8.84 Mbps (data used: 10.8 MB )
Packet Loss: Not available.
Result URL: https://www.speedtest.net/result/c/88e3a854-e4c4-4906-b57b-49cdb0757bf8
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
Intestingly now I get much better results (directly from the Asus RT-AX82U router and not using laptop with wireless). The new version of OOkla Speedtest seems to give more statistics.

Code: 
xiaofan@RT-AX82U:/tmp/home/root# ./speedtest -s 3633

   Speedtest by Ookla

      Server: China Telecom - Shanghai (id: 3633)
         ISP: Singtel Fibre
Idle Latency:   215.24 ms   (jitter: 123.41ms, low: 206.03ms, high: 684.02ms)
    Download:   282.09 Mbps (data used: 413.5 MB)
                308.47 ms   (jitter: 77.66ms, low: 195.04ms, high: 1027.87ms)
      Upload:     9.89 Mbps (data used: 16.2 MB)
                343.49 ms   (jitter: 76.99ms, low: 208.49ms, high: 1104.69ms)
 Packet Loss: Not available.
  Result URL: https://www.speedtest.net/result/c/7459fcfd-927a-4996-91f6-d528c50ebcc3
 
xiaofan@RT-AX82U:/tmp/home/root# ./speedtest -s 35527

   Speedtest by Ookla

      Server: China Broadcasting Network Group Sichuan - Chengdu (id: 35527)
         ISP: Singtel Fibre
Idle Latency:    77.91 ms   (jitter: 0.08ms, low: 77.89ms, high: 78.05ms)
    Download:   424.01 Mbps (data used: 542.2 MB)
                148.23 ms   (jitter: 50.77ms, low: 79.37ms, high: 514.83ms)
      Upload:   528.25 Mbps (data used: 925.3 MB)
                145.24 ms   (jitter: 48.06ms, low: 81.59ms, high: 306.36ms)
 Packet Loss: Not available.
  Result URL: https://www.speedtest.net/result/c/74d8ff59-1302-4142-af11-9a72431343a1
 
xiaofan@RT-AX82U:/tmp/home/root# ./speedtest -s 23844

   Speedtest by Ookla

      Server: China Telecom Wuhan Branch - Wuhan (id: 23844)
         ISP: Singtel Fibre
Idle Latency:   201.23 ms   (jitter: 1.42ms, low: 200.31ms, high: 203.32ms)
    Download:   359.47 Mbps (data used: 527.8 MB)
                315.36 ms   (jitter: 78.69ms, low: 196.75ms, high: 1037.41ms)
      Upload:     9.22 Mbps (data used: 15.0 MB)
                337.51 ms   (jitter: 79.99ms, low: 220.80ms, high: 1124.88ms)
 Packet Loss: Not available.
  Result URL: https://www.speedtest.net/result/c/11c95d7c-de9a-4cb2-9c65-0956de2803dd
 
xiaofan@RT-AX82U:/tmp/home/root# ./speedtest -s 5396

   Speedtest by Ookla

      Server: China Telecom JiangSu 5G - Suzhou (id: 5396)
         ISP: Singtel Fibre
Idle Latency:   338.04 ms   (jitter: 0.04ms, low: 338.02ms, high: 338.10ms)
    Download:   331.22 Mbps (data used: 454.4 MB)
                537.98 ms   (jitter: 89.62ms, low: 354.80ms, high: 769.45ms)
      Upload:    80.24 Mbps (data used: 123.4 MB)
                567.75 ms   (jitter: 89.35ms, low: 338.54ms, high: 835.39ms)
 Packet Loss: Not available.
  Result URL: https://www.speedtest.net/result/c/a2d2878f-63e4-4c2c-a80e-02116dbe0fae
 
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
ksw2010 said:
Thanks xiaofan for providing the server details. I follow to retest to confirm my ST line to China. Looks like the speed is acceptable to China for for my home BB line.
Click to expand...

I think your results are pretty good already, especially the download speed.
 
C

cyberet

Senior Member
Joined
May 28, 2001
Messages
2,484
Reaction score
316
tested on 1gbps VQ around noon via LAN.
contract ending in dec, looking to see which isp has better latency/speeds and possible move.
SH - seems the best, but cs bad?
M1/MR - M1 has the best cs and ipv6, MR has static ipv4

hmm...

Server NameServer IDLatencyJitterPacket LossDownload SpeedUpload Speed
Singtel - Singapore136233.46 ms0.29 ms0.00%945.09 Mbps945.38 Mbps
ViewQwest - Singapore20542.55 ms0.22 ms0.00%872.6 Mbps945.22 Mbps
PT FirstMedia - Singapore75562.41 ms0.24 ms0.00%795.19 Mbps948.97 Mbps
Comcast - Sacramento, CA9436260.95 ms0.87 ms0.00%41.6 Mbps257.03 Mbps
Spectrum - Los Angeles, CA16974180.41 ms0.71 ms0.00%140.32 Mbps511.11 Mbps
Optus - Melbourne30932223.7 ms0.08 ms0.00%479.56 Mbps382.23 Mbps
Misaka Network, Inc. - Tokyo4498876.63 ms0.13 ms0.00%663.53 Mbps706.03 Mbps
SIMPLYCONNECT - Dar es Salaam13902337.45 ms0.16 ms0.00%3.95 Mbps10.92 Mbps
Celcom Axiata - Kuala Lumpur495614.02 ms1.48 ms0.00%596.89 Mbps948.54 Mbps
Bell Mobility - Vancouver, BC17402154.43 ms0.26 ms0.00%173.43 Mbps454.0 Mbps
Telstra International - Hong Kong4434035.04 ms0.17 ms0.00%450.12 Mbps940.95 Mbps
 
Last edited:
X

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
cyberet said:
tested on 1gbps VQ around noon via LAN.
contract ending in dec, looking to see which isp has better latency/speeds and possible move.
SH - seems the best, but cs bad?
M1/MR - M1 has the best cs and ipv6, MR has static ipv4
Click to expand...

I think your VQ results are pretty decent but I can see that you have more dropouts. @fireong is using Starhub ad he has got 13 results (and very good results) from Starhub. I am using Singtel and I have got 12 results and you only have 11 results.

International Latency/Speed will depend on the locations you are interested. This thread is a good one but it may not cover the server locations you are interested.

In terms of latency, M1/Starhub are usually better than Singtel in many locations but could be slower in some cases. MR/VQ are supposed to be even better than M1/Starhub in terms of entertaining requests for better routing. But they may be pretty bad in some cases (one example mentioned before is s.taobo.com).
 
C

cyberet

Senior Member
Joined
May 28, 2001
Messages
2,484
Reaction score
316
VQ 1gbps at 12midnight. results seems better then noon

Server NameServer IDLatencyJitterPacket LossDownload SpeedUpload Speed
Singtel - Singapore136232.95 ms0.16 ms0.00%947.31 Mbps932.03 Mbps
ViewQwest - Singapore20542.92 ms0.06 ms0.00%860.48 Mbps946.99 Mbps
PT FirstMedia - Singapore75562.92 ms0.24 ms0.00%811.03 Mbps949.06 Mbps
Comcast - Sacramento, CA9436229.54 ms124.43 ms0.00%225.2 Mbps274.49 Mbps
Spectrum - Los Angeles, CA16974180.73 ms0.17 ms0.00%249.7 Mbps278.53 Mbps
Optus - Melbourne30932226.37 ms0.12 ms0.00%446.35 Mbps318.66 Mbps
Misaka Network, Inc. - Tokyo4498877.85 ms6.6 ms41.49%698.84 Mbps607.51 Mbps
SIMPLYCONNECT - Dar es Salaam13902312.97 ms0.31 ms0.00%3.79 Mbps7.7 Mbps
Celcom Axiata - Kuala Lumpur495613.47 ms0.09 ms0.00%588.85 Mbps948.29 Mbps
Bell Mobility - Vancouver, BC17402154.74 ms2.38 ms0.00%402.38 Mbps579.88 Mbps
Telstra International - Hong Kong4434034.87 ms0.22 ms0.00%490.82 Mbps948.66 Mbps
 
Last edited:
C

cyberet

Senior Member
Joined
May 28, 2001
Messages
2,484
Reaction score
316
taobao seems alright with VQ.
this is via wifi

Code: 
>nslookup s.taobao.com
Server:  UnKnown
Address:  202.73.51.100


Non-authoritative answer:
Name:    v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com
Addresses:  2401:b180:2000:10::2d
          2401:b180:2000:20::29
          59.82.60.16
Aliases:  s.taobao.com
          v6-sh-sz-zb.wagbridge.alibaba.taobao.com

>ping s.taobao.com


Pinging v6-sh-sz-zb.wagbridge.alibaba.taobao.com.gds.alibabadns.com [59.82.60.16] with 32 bytes of data:
Reply from 59.82.60.16: bytes=32 time=119ms TTL=83
Reply from 59.82.60.16: bytes=32 time=119ms TTL=83
Reply from 59.82.60.16: bytes=32 time=119ms TTL=83
Reply from 59.82.60.16: bytes=32 time=119ms TTL=83


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

>ping www.taobao.com


Pinging www.taobao.com.danuoyi.tbcache.com [163.181.36.225] with 32 bytes of data:
Reply from 163.181.36.225: bytes=32 time=4ms TTL=57
Reply from 163.181.36.225: bytes=32 time=13ms TTL=57
Reply from 163.181.36.225: bytes=32 time=5ms TTL=57
Reply from 163.181.36.225: bytes=32 time=9ms TTL=57


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

xiaofan

High Supremacy Member
HWZ Insider
Joined
Sep 16, 2018
Messages
32,674
Reaction score
10,211
cyberet said:
taobao seems alright with VQ.
this is via wifi
Click to expand...

That was based on old reports. But take note "s.taobao.com" ping result may be quite different from time to time. For example, I have a good result from Singtel now.

Code: 
PS C:\Users\xiaof> ping 59.82.9.84

Pinging 59.82.9.84 with 32 bytes of data:
Reply from 59.82.9.84: bytes=32 time=78ms TTL=81
Reply from 59.82.9.84: bytes=32 time=78ms TTL=81
Reply from 59.82.9.84: bytes=32 time=79ms TTL=81
Reply from 59.82.9.84: bytes=32 time=79ms TTL=81

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

My previous results in June were pretty bad.
https://forums.hardwarezone.com.sg/...al-speed-tests.6405972/page-10#post-142243485
 
Last edited:
C

cyberet

Senior Member
Joined
May 28, 2001
Messages
2,484
Reaction score
316
MR business 400mbps 4pm

Server NameServer IDLatencyJitterPacket LossDownload SpeedUpload Speed
Singtel - Singapore136232.61 ms0.27 ms0.00%301.24 Mbps285.56 Mbps
ViewQwest - Singapore20542.59 ms0.11 ms0.00%302.56 Mbps285.94 Mbps
PT FirstMedia - Singapore75562.33 ms0.16 ms0.00%303.36 Mbps285.93 Mbps
Spectrum - Los Angeles, CA16974246.77 ms0.3 ms0.00%303.04 Mbps28.33 Mbps
University of Texas, Austin - Austin, TX16089216.3 ms6.34 ms0.00%49.69 Mbps18.61 Mbps
Optus - Melbourne30932221.47 ms0.1 ms0.00%297.77 Mbps28.79 Mbps
Misaka Network, Inc. - Tokyo4498887.28 ms4.15 ms0.00%287.5 Mbps19.87 Mbps
SIMPLYCONNECT - Dar es Salaam13902266.28 ms0.62 ms0.00%4.67 Mbps4.87 Mbps
Celcom Axiata - Kuala Lumpur495612.33 ms0.37 ms0.00%301.11 Mbps284.79 Mbps
Telstra International - Hong Kong4434033.07 ms0.21 ms0.00%303.44 Mbps154.31 Mbps
China Telecom - Shanghai3633124.07 ms4.32 msN/A266.56 Mbps4.81 Mbps
 
You must log in or register to reply here.
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 Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top