![]() ![]() ![]() |
|
Orcon gigabit chch
Pinging wotna3.login.wargaming.net [92.223.56.14] with 32 bytes of data:
Reply from 92.223.56.14: bytes=32 time=201ms TTL=53
Reply from 92.223.56.14: bytes=32 time=196ms TTL=53
Reply from 92.223.56.14: bytes=32 time=202ms TTL=53
Reply from 92.223.56.14: bytes=32 time=198ms TTL=53
Ping statistics for 92.223.56.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 196ms, Maximum = 202ms, Average = 199ms
The thing to remember about latency is it's always due to change.
You never know when a routing deal will change, a fibre link will get damaged, provider adds alternative paths due to growing demand etc.
The best option is the larger RSP's, Vodafone, Spark, Bigpipe/Skinny by proxy of being under sparks routing, Voyager.
2D are an interesting one to go with as they are doing alot of work in their routing.
Overall 2D routing is starting to look quite nice from their own core. but i'd expect it more likely to see changes in their routing compared to say, Spark.
Spark (VDSL - G.INP)
1 * * *
2 * * *
3 ae8-10.akbr6.global-gateway.net.nz (122.56.116.5) 8.490 ms 8.879 ms 9.512 ms
4 ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 8.418 ms 8.279 ms 8.460 ms
5 ae10-10.tkbr12.global-gateway.net.nz (202.50.232.29) 8.769 ms 8.176 ms 8.828 ms
6 xe2-3-1.lebr7.global-gateway.net.nz (122.56.127.22) 133.851 ms 132.980 ms 133.373 ms
7 ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25) 137.767 ms 136.978 ms 141.309 ms
8 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 141.767 ms 142.794 ms 141.626 ms
9 palo-b1-link.telia.net (62.115.145.204) 138.143 ms 138.016 ms 138.213 ms
10 kanc-b1-link.telia.net (62.115.125.184) 172.950 ms 172.369 ms 172.324 ms
11 chi-b21-link.telia.net (213.155.130.176) 184.718 ms 184.962 ms 184.300 ms
12 * * *
13 92.223.56.14 (92.223.56.14) 187.700 ms 188.292 ms 187.990 ms
Vodafone (ADSL - No Interleaving)
1 254.183.252.27.dyn.cust.vf.net.nz (27.252.183.254) 9.265 ms 7.916 ms 7.901 ms
2 unknown.telstraglobal.net (134.159.174.42) 9.741 ms 9.434 ms 10.120 ms
3 unknown.telstraglobal.net (134.159.174.41) 11.247 ms 11.558 ms 9.776 ms
4 i-0-1-0-1.hptw-core02.telstraglobal.net (202.84.223.46) 12.081 ms 10.925 ms 12.056 ms
5 i-0-0-0-0.tauc-core02.telstraglobal.net (202.84.142.146) 10.646 ms 10.449 ms 12.026 ms
6 i-10520.tlot-core02.telstraglobal.net (202.84.138.82) 134.980 ms 135.946 ms 134.148 ms
7 i-91.tlot02.telstraglobal.net (202.40.149.177) 133.992 ms 136.248 ms 134.635 ms
8 eqix-dc3.gcore.lu (206.126.237.22) 188.733 ms 189.507 ms 188.720 ms
9 10.255.3.137 (10.255.3.137) 208.554 ms 208.439 ms 208.631 ms
10 92.223.56.14 (92.223.56.14) 208.998 ms 209.013 ms 208.561 ms
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
2degrees also have low latency routes to the US which they route over depending on the type of traffic and larger capacity pipes for bulk traffic. I suspect for gaming you'll go over the lower latency routes. This is why a Tracroute isn't actually the best way to determine how a service is going to work with a provider without testing that service.
Be interesting to see how it compares regardless.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
michaelmurfy:
2degrees also have low latency routes to the US which they route over depending on the type of traffic and larger capacity pipes for bulk traffic. I suspect for gaming you'll go over the lower latency routes. This is why a Tracroute isn't actually the best way to determine how a service is going to work with a provider without testing that service.
Be interesting to see how it compares regardless.
Yup exactly. there are so many variables to it.
As i said, 2D do alot of interesting things with their routing. which may introduce a bit of variance, but also make them a great option.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
To throw my 2c in, it can and does change without notice and it's a totally frustrating.
The route from here to the US west coast is unchanged, but reason I cannot fathom I've gone from 170-180ms on Blizzard servers to 220-230ms.
It slams into the west coast just peachy until it hits Blizzard and adds 50ms. This did not exist last month and due to the way Blizz run their support services, I don't see any way of them actually acknowledging a fault.
So yeah, latency can change and it can be absolutely outside of your and your ISPs control
Painted Minis | Steam Profile | PSN Profile
Currently Playing: Heroes of the Storm (PC) | Half-Life 2 (PC)
|
![]() ![]() ![]() |