Latency

[Doubleplay]

Anyone having latency problems tonight? Suddenly every shard except tc shows 300+ latency. Was wondering if the problem is at the other end and shared by all, or on my end, a new phenomenon for me.

 

[Dermott of LS]

...

Showing all clean on my connection... all <100ms

 

[Ezekiel Zane]

I've been moving around noticeably less zippy tonight. I even logged into the CC to see if it was the same. It was. Noticeably more latency and jerky movement.

 

[temu]

I have been lagging for 2 weeks.

Comcast internet - Bellingham WA. UO is not playable. I hate life.

http://oi41.***********/21dopqh.jpg

 

[Ezekiel Zane]

Looking thru all the shards in both clients, I seen that the lowest latency was 207ms. I have many that are 300ms and higher.

 

[Ezekiel Zane]

Oo, that packet loss is bad.

 

[Storm]

do a trace route and see where its losing at

 

[Ezekiel Zane]

Weird, Yamato is now showing 167ms latency while my home shard Pacific is at 237ms.

I'm also experiencing 17% to 33% packet loss according the the CC.

 

[Dermott of LS]

...

I've never seen the client ping result be very accurate in either client. Always use an outside program such as UOTrace or PingPlotter or the like to get the full route.

 

[Ezekiel Zane]

I have been lagging for 2 weeks.

Comcast internet - Bellingham WA.

I see a trend here. At the moment, I'm in Spokane, WA and I'm also on Comcast. A traceroute shows me being routed thru Comcast's Seattle based routers.

 

[Dermott of LS]

...

Sarasota, FL here, RoadRunner Cable... basically the opposite corner of the country.

 

[Ezekiel Zane]

Ok I can't find my bookmark of the new server addresses. Anyone have it handy?

 

[Dermott of LS]

...

UO Stratics *New* | Server IP Addresses

 

[Ezekiel Zane]

Thanks Dermott.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\GAMER>ping 65.216.123.33

Pinging 65.216.123.33 with 32 bytes of data:
Reply from 65.216.123.33: bytes=32 time=248ms TTL=49
Reply from 65.216.123.33: bytes=32 time=250ms TTL=49
Reply from 65.216.123.33: bytes=32 time=264ms TTL=49
Reply from 65.216.123.33: bytes=32 time=256ms TTL=49

Ping statistics for 65.216.123.33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 248ms, Maximum = 264ms, Average = 254ms

C:\Users\GAMER>tracert 65.216.123.33

Tracing route to 65.216.123.33 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 10 ms 8 ms 73.100.96.1
3 8 ms 7 ms 7 ms te-3-4-ur01.spokane.wa.seattle.comcast.net [68.87.160.209]
4 18 ms 16 ms 18 ms te-0-10-0-5-ar01.seattle.wa.seattle.comcast.net [68.86.177.153]
5 16 ms 14 ms 18 ms ae-1-0-ar03.seattle.wa.seattle.comcast.net [68.85.240.70]
6 15 ms 15 ms 15 ms pos-1-14-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.85]
7 16 ms 17 ms 17 ms pos-0-1-0-0-pe01.seattle.wa.ibone.comcast.net [68.86.85.38]
8 23 ms 17 ms 20 ms if-4-0-0.core2.S00-Seattle.as6453.net [66.110.64.1]
9 59 ms 60 ms 57 ms if-5-2-1-0.tcore1.PDI-PaloAlto.as6453.net [66.198.127.65]
10 59 ms 61 ms 59 ms if-2-2.tcore2.PDI-PaloAlto.as6453.net [66.198.127.2]
11 67 ms 71 ms * Vlan3254.icore1.SQN-SanJose.as6453.net [66.198.144.6]
12 59 ms 58 ms 58 ms Vlan513.icore1.SQN-SanJose.as6453.net [209.58.116.114]
13 60 ms 58 ms 58 ms 0.ae3.XL4.SJC7.ALTER.NET [152.63.50.10]
14 195 ms 191 ms 193 ms 0.so-6-1-0.XT2.LAX7.ALTER.NET [152.63.0.65]
15 157 ms 158 ms 147 ms so-0-0-0.ur2.lax11.web.wcom.net [208.222.8.26]
16 199 ms 198 ms 205 ms 208.254.48.22
17 209 ms 208 ms 199 ms 208.254.48.1
18 257 ms 282 ms 256 ms 208.254.48.10
19 255 ms 243 ms 253 ms 65.245.224.33
20 268 ms 270 ms 262 ms 65.216.123.33

Trace complete.

 

[soze]

ok....thought it was just me

sonoma is at 300+

 

[enderz]

I have comcast, michigan here.

Latency making game unplayable for me tonight

Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 73.35.14.1 2 12ms
ge-2-39-ur01.lawton.mi.michigan.c69.139.240.213 3 11ms
te-0-3-0-3-ar01.taylor.mi.michiga68.85.222.10 4 28ms
pos-0-6-0-0-ar01.pontiac.mi.michi68.85.222.38 5 20ms
pos-3-3-0-0-cr01.chicago.il.ibone68.86.90.109 6 64ms
pos-1-12-0-0-cr01.350ecermak.il.i68.86.88.90 7 31ms
pos-1-8-0-0-pe01.350ecermak.il.ib68.86.87.166 8 31ms
ix-0-2-1-0.tcore2.CT8-Chicago.as6206.82.141.81 9 49ms
* Unknown Host * 64.86.79.2 10 45ms
* Unknown Host * 206.82.141.134 11 58ms
0.ae3.XL4.CHI13.ALTER.NET 152.63.66.77 12 37ms
0.so-6-1-0.XT2.DCA5.ALTER.NET 152.63.42.189 13 184ms
0.so-6-0-0.UR2.MTC4.ALTER.NET 152.63.38.242 14 56ms
* Unknown Host * 206.112.176.58 15 185ms
* Unknown Host * 206.112.184.37 16 58ms
host136.ea.com 63.117.27.136 17 185ms

 

[Tina Small]

Comcast here, in Denver. Latency looks like Temu's, with Atlantic (ugh) having the lowest, followed by the Japanese and Korean shards. It seems very strange that the overseas shards look better in terms of latency than the North American shards (with the exception of Atlantic). Just slogging through best I can.

 

[Dermott of LS]

...

Am I the only one NOT on Comcast? Seems like that's been the common theme so far.

 

[Storm]

shhhhh my comcast is actually working well now I was having 200 plus pings and called them out and it was loose wire in the box outside

 

[BeaIank]

I had the same problem yesterday night. Most american shards had a latency at around 1000 ms and package loss around 30%.
I am in South America, and usually have a latency of 156 ms and next to no package loss to all the shards.

 

[Doubleplay]

Just an update on my Comcast Latency. California here. Last night all American shards were 300-400 ms. This morning I am back to normal 50-60 American and 120 or so to Asian. Wonder if Comcast will ever come clean on what is going on?

 

[Lord Frodo]

It looks more like an Alter.net / EA problem from the traces shown.

 

[Ezekiel Zane]

Pinging 62ms this morning. Seems it's fixed.