12-06-2020 08:05 PM
Account: Unlimited UltraFast HFC Max in Chrsitchurch.
Populated Battlefield 4, Battlefield 1, and Battlefield V servers in the Oceania region are very few if any in the morning and early afternoon, so it is good to NOT to be limited to Austrailian servers which have less than <160ms ping. My friend has an account with MyRepublicin Christchurch.
His ping rates using MyRepublic:
Oceania 38ms
Hong Kong 151ms
U.S. 203ms.
My ping rates using Vodafone
Oceania 49ms
U.S. 205ms
Hong Kong 301ms
Ping times are ultra important when playing multiplayer first person shooters, and the more playable servers there are, the better. Why the huge desparity? I thought data was going through the same pipe from NZ to other countries. Can this be rectified? I sure wouldn't mind joining Hong Kong Battlfield servers in times when there's none active in Oceania.
13-06-2020 06:51 PM
Do you have a ip address or even better a traceroute to these servers in HK
14-06-2020 11:10 AM - edited 14-06-2020 11:11 AM
I managed to find one and the tracert produces the expected results.
From my friend who uses a MyRepublic account.
1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 16 ms 16 ms 15 ms 101-100-136-2.myrepublic.co.nz [101.100.136.2]
3 16 ms 16 ms 16 ms ten-1-2-0-399.bdr01.akl05.akl.vocus.net.nz [175.45.93.173]
4 151 ms 151 ms 151 ms te0-7-0-5.cor01.akl05.akl.nz.vocus.network [114.31.202.40]
5 151 ms 151 ms 151 ms be202.cor01.syd11.nsw.vocus.network [114.31.202.55]
6 151 ms 151 ms 151 ms be102.bdr02.hkg01.hkg.vocus.network [119.161.84.35]
7 151 ms 151 ms 151 ms 49544.hkg.equinix.com [36.255.56.159]
8 151 ms 151 ms 151 ms hosted-by.i3d.net [43.239.136.240]
And mine.
Tracing route to hosted-by.i3d.net [43.239.136.240]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Linksys08250 [192.168.1.1]
2 9 ms 26 ms 9 ms 203-173-191-254.dsl.dyn.ihug.co.nz [203.173.191.254]
3 9 ms 10 ms 9 ms 10.200.12.29
4 145 ms 147 ms 147 ms vodafone-nz-ltd.10gigabitethernet6-11.core1.lax2.he.net [216.218.236.102]
5 145 ms 144 ms 146 ms v106.core1.lax2.he.net [216.218.236.101]
6 299 ms 300 ms 300 ms 100ge10-1.core1.hkg1.he.net [184.105.64.126]
7 301 ms 301 ms 300 ms 103.247.139.38
8 301 ms 300 ms 300 ms hosted-by.i3d.net [43.239.136.240]
Trace complete.
15-06-2020 11:34 AM
Hi
Will see if there can be any changes made to this route. Interesting that the MyRepublic test is 151 ms to Auckland, and remain 151ms to HK. Very longtime to AK, and then from AK to HK is 0ms............
4 151 ms 151 ms 151 ms te0-7-0-5.cor01.akl05.akl.nz.vocus.network [114.31.202.40]
5 151 ms 151 ms 151 ms be202.cor01.syd11.nsw.vocus.network [114.31.202.55]
6 151 ms 151 ms 151 ms be102.bdr02.hkg01.hkg.vocus.network [119.161.84.35]
7 151 ms 151 ms 151 ms 49544.hkg.equinix.com [36.255.56.159]
8 151 ms 151 ms 151 ms hosted-by.i3d.net [43.239.136.240]
As below just tested and can see 279ms from VF
20-06-2020 06:10 PM
Five days have elapsed so would I be correct in thinking that no changes to the routing can or will be made?
07-08-2020 09:59 PM
The routing problem is solved. After 18 years with Vodafone I went to another ISP.
Copyright © Vodafone New Zealand Ltd