suggest optimized network Singapore to China

AoAp

Hi,I want to buy Singapore nat vps,then website tips Singapore ip have been blocked China.
However,I test ping nat vps ip Singapore 103.216.223.11 from China,I find this ip have not beed blocked Chian now.

but,I find ping delay is very long,delay is about 300ms+
thus,can you optimized Singapore ip to China network delay?and I can help test delay after optimized in this.
If optimized,I will purchase Singapore vps.
thanks!

root@aml:~# ping 103.216.223.11
PING 103.216.223.11 (103.216.223.11) 56(84) bytes of data.
64 bytes from 103.216.223.11: icmp_seq=1 ttl=50 time=364 ms
64 bytes from 103.216.223.11: icmp_seq=2 ttl=50 time=389 ms
64 bytes from 103.216.223.11: icmp_seq=3 ttl=50 time=390 ms
64 bytes from 103.216.223.11: icmp_seq=5 ttl=50 time=369 ms
64 bytes from 103.216.223.11: icmp_seq=6 ttl=50 time=360 ms
64 bytes from 103.216.223.11: icmp_seq=7 ttl=50 time=364 ms
64 bytes from 103.216.223.11: icmp_seq=8 ttl=50 time=369 ms
64 bytes from 103.216.223.11: icmp_seq=9 ttl=50 time=388 ms
64 bytes from 103.216.223.11: icmp_seq=10 ttl=50 time=389 ms

AoAp

Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.11.1 10.7% 28 1.0 0.9 0.5 1.1 0.0
2. ************ 0.0% 28 6.5 7.7 3.9 51.6 9.2
3. ************ 96.3% 28 24899 24899 24899 24899 0.0
4. ************ 0.0% 28 4.3 3.8 2.5 5.3 0.7
5. ************ 0.0% 28 3.4 7.4 3.3 12.5 2.7
6. ************ 0.0% 28 9.8 8.6 4.0 13.0 2.4
7. ************ 0.0% 28 12.7 8.1 3.8 16.0 2.9
8. 219.158.3.138 0.0% 28 9.8 9.5 4.2 13.7 2.6
9. 219.158.103.6 0.0% 28 155.3 154.8 151.9 157.2 1.3
10. 62.115.33.229 14.3% 28 169.5 165.5 151.7 180.7 6.3
11. 62.115.136.46 11.1% 28 167.8 164.1 152.3 170.3 6.0
12. 62.115.134.42 11.1% 28 326.4 331.2 320.0 339.6 4.2
13. 80.239.128.127 14.8% 28 334.3 329.5 317.5 337.4 5.5
14. 103.97.54.11 0.0% 28 316.5 317.1 315.5 319.8 0.9
15. 103.216.223.11 14.8% 27 333.8 327.9 317.1 333.8 5.8

AoAp

traceroute to 103.216.223.11 (103.216.223.11), 30 hops max, 60 byte packets
1 192.168.11.1 0.83 ms * LAN Address
192.168.11.1 0.75 ms * LAN Address
192.168.11.1 0.86 ms * LAN Address
2 ************ 7.72 ms AS4808 China Beijing ChinaUnicom
************ 5.77 ms AS4808 China Beijing ChinaUnicom
************ 12.68 ms AS4808 China Beijing ChinaUnicom
3 *
*
*
4 ************ 5.15 ms AS4808 China Beijing ChinaUnicom
************ 6.67 ms AS4808 China Beijing ChinaUnicom
************ 4.38 ms AS4808 China Beijing ChinaUnicom
5 ************ 10.20 ms AS4808 China Beijing ChinaUnicom
************ 7.69 ms AS4808 China Beijing ChinaUnicom
************ 11.89 ms AS4808 China Beijing ChinaUnicom
6 ************ 7.37 ms AS4808 China Beijing ChinaUnicom
************ 5.32 ms AS4808 China Beijing ChinaUnicom
************ 9.10 ms AS4808 China Beijing ChinaUnicom
7 ************ 7.68 ms AS4837 China Beijing ChinaUnicom
************ 12.58 ms AS4837 China Beijing ChinaUnicom
************ 9.56 ms AS4837 China Beijing ChinaUnicom
8 219.158.3.138 8.36 ms AS4837 China Beijing ChinaUnicom
219.158.3.138 13.22 ms AS4837 China Beijing ChinaUnicom
219.158.3.138 10.35 ms AS4837 China Beijing ChinaUnicom
9 219.158.103.6 155.76 ms AS4837 United States California Los Angeles ChinaUnicom
219.158.103.6 154.98 ms AS4837 United States California Los Angeles ChinaUnicom
219.158.103.6 156.04 ms AS4837 United States California Los Angeles ChinaUnicom
10 las-bb1-link.telia.net (62.115.33.229) 169.36 ms AS1299 United States California Los Angeles telia.com
las-bb1-link.telia.net (62.115.33.229) 174.63 ms AS1299 United States California Los Angeles telia.com
las-bb1-link.telia.net (62.115.33.229) 173.42 ms AS1299 United States California Los Angeles telia.com
11 las-b21-link.telia.net (62.115.136.46) 164.18 ms AS1299 United States California Los Angeles telia.com
las-b21-link.telia.net (62.115.136.46) 169.48 ms AS1299 United States California Los Angeles telia.com
*
12 snge-b1-link.telia.net (62.115.134.42) 328.67 ms AS1299 TELIA.COM BACKBONE telia.com
snge-b1-link.telia.net (62.115.134.42) 335.85 ms AS1299 TELIA.COM BACKBONE telia.com
snge-b1-link.telia.net (62.115.134.42) 334.17 ms AS1299 TELIA.COM BACKBONE telia.com
13 80.239.128.127 334.90 ms AS1299 TELIA.COM BACKBONE telia.com
telia.sg3.sg.coloau.net.au (80.239.128.127) 332.89 ms AS1299 TELIA.COM BACKBONE telia.com
80.239.128.127 322.24 ms AS1299 TELIA.COM BACKBONE telia.com
14 as136557.cr1.sg3.sg.coloau.net.au (103.97.54.11) 318.58 ms AS63956 Singapore coloau.com.au
103.97.54.11 317.47 ms AS63956 Singapore coloau.com.au
as136557.cr1.sg3.sg.coloau.net.au (103.97.54.11) 317.22 ms AS63956 Singapore coloau.com.au
15 103.216.223.11 317.82 ms AS136557 Singapore hostuniversal.com.au
103.216.223.11 333.80 ms AS136557 Singapore hostuniversal.com.au
103.216.223.11 332.56 ms AS136557 Singapore hostuniversal.com.au

yoursunny

Bandwidth aren't born equal. Singapore routes that can reach China directly cost more than routes without China peering.

tetech

@AoAp said: can you optimized Singapore ip to China network delay?

Who is "you"? @mikho looks like your test IP.

Anyway, because the test IP is not blocked doesn't mean the VPS IP is not blocked.

seriesn

You won’t be able to get premium Asian bandwidth for LE price. Bandwidth is filthy expensive on that part of the world and that with meh peering.

FAT32

@AoAp said:
I find this ip have not beed blocked China now.

I don't think you can get premium / optimised bandwidth at low end price. If you happen to get it, a lot of people will start ordering it, and I am pretty sure it will be blocked in a few days.

poisson

@FAT32 said:

@AoAp said:
I find this ip have not beed blocked China now.

I don't think you can get premium / optimised bandwidth at low end price. If you happen to get it, a lot of people will start ordering it, and I am pretty sure it will be blocked in a few days.

Exactly. These people seriously don't know how to keep it quiet.

uptime

Hello @AoAp - I don't know anything about China or Singapore connectivity but I am sure you will get some useful sdvice on how to learn more here.

If I might make one suggestion regarding posting traceroutes including the endpoint IP addresses - it is generally advisable to obscure the exact address when posting to a public forum, so as to help protect your privacy.

For example, one might write 103.216.xxx.xxx rather than the entire destination IP address. The intermediate addresses probably wouldn't be an issue to leave as is though.

(And when troubleshooting in a private support ticket with a provider, it is preferable to use the exact addresses).

tetech

@uptime said: If I might make one suggestion regarding posting traceroutes including the endpoint IP addresses - it is generally advisable to obscure the exact address when posting to a public forum, so as to help protect your privacy.

It is Mikho's looking glass IP, so probably no privacy issue at least with that IP.