L
LordSoth
Guest
Lag is back big time again.
Back to unplayable again
Please Fix UO gods
Back to unplayable again
Please Fix UO gods
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 10.243.0.1 1 8ms 100% 0 / 65
vl401.kacz-s-1.ken.bigpond.net.au58.160.12.33 2 14ms 22ms 0% 65 / 65 8ms / 591ms
te6-2.agg2.ken.bigpond.net.au 58.160.15.246 3 14ms 12ms 0% 65 / 65 8ms / 51ms
* Unknown Host * 172.18.239.38 4 9ms 100% 0 / 65
* Unknown Host * 172.18.239.33 5 14ms 100% 0 / 64
Bundle-Ether11.chw48.Sydney.telst203.45.17.21 6 12ms 40ms 0% 64 / 64 8ms / 1027ms
Bundle-Ether6.chw-core2.Sydney.te203.50.6.153 7 13ms 11ms 0% 64 / 64 9ms / 36ms
Bundle-Ether1.oxf-gw2.Sydney.tels203.50.6.90 8 13ms 12ms 0% 64 / 64 9ms / 44ms
TenGigabitEthernet4-0.sydo-core01203.50.13.78 9 15ms 12ms 0% 64 / 64 8ms / 37ms
i-10-0-0.syd-core03.bi.reach.com 202.84.221.85 10 11ms 13ms 0% 64 / 64 9ms / 46ms
i-3-0-0.sjc-core01.bx.reach.com 202.84.141.1 11 171ms 173ms 0% 64 / 64 168ms / 200ms
i-1-1.eqnx02.bi.reach.com 202.84.251.85 12 170ms 241ms 0% 64 / 64 169ms / 1383ms
* Unknown Host * 0.0.0.0 13 0ms
edge02.eqx-sjc.ea.com 159.153.192.5 14 172ms 192ms 0% 64 / 64 169ms / 1423ms
edge01.eqx-sjc.ea.com 159.153.192.234 15 180ms 177ms 0% 64 / 64 167ms / 350ms
central-aw5.owo.com 159.153.209.54 16 178ms 172ms 0% 64 / 64 168ms / 210ms
Tiara, your lag is a distance lag, the latency jumps from 11ms to 171ms as the data travels between hop 10 (sydney) to hop 11 (sjc, saint jose in the usa?).
The lag everyone is talking about in this thread is the lag they are experiencing in Oceania shard (sydney), playing from australia and new zealand, which had been fine until recently (2 months ago?)
Distance lag is expected if you are playing in an overseas shard like pacific, thats why EA/OSI rolled out local shards to accomodate non-us based players.
Not only that, but has anyone done a trace to OC? Just pointing out that people in the US can now ping 50-20 to OC, so yea....I guess you "native" players have a distance problem as well.Tiara's problem starts at hop 12, look at the max ping time there.