Help! Getting latency on routing from CHCH to a HK server. (43.163.178.228)

Forums › Voyager › Help! Getting latency on routing from CHCH to a HK server. (43.163.178.228)

1 | 2

Nikana

7 posts

Wannabe Geek

#3495867 27-May-2026 14:45

Good replies.
If 20ms dosent bother you, it dosent bother you.
I do see 20ms+ sometimes. Rare.

Wouldnt post here if I plan to pick the lowest possible solution without cost concerns. :)

MaxineN

Max
2114 posts

Uber Geek
+1 received by user: 1734

ID Verified

Trusted

Subscriber

#3495893 27-May-2026 15:50

yitz:

One NZ and Mercury (it looks like they possibly collaborate purchasing bandwidth into Asia) have dual paths between Sydney and Singapore.

Unfortunately that doesn't translate into real world.

I imagine there's probably a much better path to take to get to this IP in HK... @taneb1 just an FYI to put across your friends' desk :~)

Ramblings from a mysterious lady who's into tech. Warning I may often create zingers.

Want broadband cheap and made for tech enthusiasts? Go look over at Quic. Use R177510EBNVXP for free setup at check out.

taneb1

553 posts

Ultimate Geek
+1 received by user: 231

ID Verified

Trusted

Mercury

#3495906 27-May-2026 16:09

MaxineN:

I imagine there's probably a much better path to take to get to this IP in HK... @taneb1 just an FYI to put across your friends' desk :~)

Does seem a little odd, have raised a ticket internally to have the team take a look (No promises) - Thanks @michaelmurfy for the RIPE data as well, quite helpful!

Any comments made are my personal views and does not represent those of my employer

Linux

12369 posts

Uber Geek
+1 received by user: 8663

Trusted

Lifetime subscriber

#3495907 27-May-2026 16:10

Nikana:

not much. but you would do the same research then pick the lowest.

@Nikana Not at all I go for reliability not lowest latency by 5 - 10ms

mikesmac

18 posts

Geek
+1 received by user: 9

#3496228 28-May-2026 14:12

this is now fixed on the Mercury network..

Ping times from Tauranga..

PING 43.163.178.228 (43.163.178.228) 56(84) bytes of data.
64 bytes from 43.163.178.228: icmp_seq=1 ttl=50 time=140 ms
64 bytes from 43.163.178.228: icmp_seq=2 ttl=50 time=141 ms
64 bytes from 43.163.178.228: icmp_seq=3 ttl=50 time=141 ms
64 bytes from 43.163.178.228: icmp_seq=4 ttl=50 time=141 ms
64 bytes from 43.163.178.228: icmp_seq=5 ttl=50 time=141 ms
q64 bytes from 43.163.178.228: icmp_seq=6 ttl=50 time=141 ms
64 bytes from 43.163.178.228: icmp_seq=7 ttl=50 time=141 ms
64 bytes from 43.163.178.228: icmp_seq=8 ttl=50 time=141 ms
^C
--- 43.163.178.228 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7011ms
rtt min/avg/max/mdev = 140.474/140.550/140.600/0.035 ms

taneb1

553 posts

Ultimate Geek
+1 received by user: 231

ID Verified

Trusted

Mercury

#3496256 28-May-2026 16:24

MaxineN:

I imagine there's probably a much better path to take to get to this IP in HK... @taneb1 just an FYI to put across your friends' desk :~)

As mentioned above, routing issue on Mercury has been resolved - https://atlas.ripe.net/measurements/175280248/results

Thanks Maxine for nudging me about it :)

Any comments made are my personal views and does not represent those of my employer

1 | 2