[klever]

well, i couldn't do the tracert at home since my router blocked it so i did it in college =) hope it get fixed

---PING---
Pinging server.reignonline.net [74.52.57.101] with 32 bytes of data:

Reply from 74.52.57.101: bytes=32 time=364ms TTL=48
Reply from 74.52.57.101: bytes=32 time=437ms TTL=48
Reply from 74.52.57.101: bytes=32 time=308ms TTL=49
Reply from 74.52.57.101: bytes=32 time=273ms TTL=54

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

---TRACERT---
Tracing route to server.reignonline.net [74.52.57.101]
over a maximum of 30 hops:

1 12 ms <1 ms <1 ms local router
2 3 ms 2 ms 2 ms (still local router)
3 48 ms 60 ms 55 ms 202.188.225.177
4 82 ms 53 ms 69 ms 219.93.177.227
5 58 ms 59 ms * 58.27.103.113
6 * * * Request timed out.
7 * * * Request timed out.

well, due to security purposes, i decided to change the first 2 since it tells where it sends from.

[luzz]

I looked into this a bit more. Warning: this is an extremely technical explanation.

I will only post relevant lines from various traceroutes to the last known IP on your own traceroute in Malaysia (58.27.103.113).

From game server in TX, USA:
10 TELEKOM-MAL.car3.LosAngeles1.Level3.net (4.71.140.14) 39.487 ms 39.519 ms 39.479 ms [in CA, USA]
11 58.27.106.229 (58.27.106.229) 225.117 ms 224.831 ms 224.538 ms [in Malaysia]

From web server in GA, USA:
9 12.118.124.102 (12.118.124.102) 62.391 ms 62.200 ms 61.920 ms [in CA, USA]
10 58.27.105.61 (58.27.105.61) 279.197 ms 279.285 ms 279.185 ms [in Malaysia]

From HE.net datacenter in CA, USA:
3 10gigabitethernet1-1.core1.pao1.he.net 12.112 ms 11.858 ms 11.522 ms [in CA, USA]
4 ge-2-2-1.paix.pao1.tm.net.my (198.32.176.26) 281.894 ms 281.853 ms 281.893 ms [in Malaysia]

From test machine in NY, USA:
6 tm-usa-gw.customer.alter.net (208.214.136.58 ) 113.362 ms 103.300 ms 102.873 ms [in CA, USA]
7 58.27.103.113 (58.27.103.113) 333.256 ms 366.352 ms 321.562 ms [in Malaysia]


What is all this? These are 4 separate traceroutes to the last viewable IP on your traceroute to the server. In all four of these cases, we see that regardless of where we start out from in the US, all traffic to Malaysia has to be routed through one of the many routers in California, USA.

These tests show a latency of roughly 200ms from California to Malaysia, regardless of which route is used in the USA side, or the Malaysian side.

This means that it takes at least 200ms to transfer data from anywhere in the USA to Malaysia. I decided to research whether or not this is normal. Latency from the east coast to the west coast of the USA is about 60ms. This is about 4000km. Distance from the east coast of the USA to Malaysia is about 14000km, or roughly 3 times the distance from the east coast to the west coast, In theory, this means 3x the latency, or 3 x 60ms -roughly 200ms.


What does this mean?

This means that there will be higher latency to Malaysia due to physics and the structure of the internet. It appears that the least amount of latency you could possibly have would be around 220ms.

This also means that there is nothing we can do about this. It is simply a distance issue.

I guess the only thing you can do is make sure nothing else is being downloaded as you play, and that you have no other programs running to minimize your latency as much as possible.

On that note, it appears as if Malaysian Internet Service Providers suck. I see much lower latency to other Asian countries.
_________________
Support Reign Online by voting!

[klever]