Major Lag Issues

[TheRudeX]

In the past few weeks every night from about 6pm to 12am I have been having such bad lag issues that I have not even been able to play. I'm talking like pure freezes ranging any where from 30 seconds to 2minutes and even more. I thought of course it was something with my conn so after doing some trouble shooting and being on the phone with both my ISP and my Router company it is nothing on mine or their end. There is some where I am getting routed though in LA that every night makes the lag so bad I just want to close my 3 accounts because I cant even play. I have 4 or 5 guildies that live within 30 mintues of where I live and they are expierencing the exact same problem. I was wondering if anybody else has had the same problem and if they were able to do any thing?

 

[cazador]

They will look into it soon....thank god for the cloud..

Same lag issues on the east coast guys, hopefully it's fixed "soon".

 

[gunneroforgin]

In the past few weeks every night from about 6pm to 12am I have been having such bad lag issues that I have not even been able to play. I'm talking like pure freezes ranging any where from 30 seconds to 2minutes and even more. I thought of course it was something with my conn so after doing some trouble shooting and being on the phone with both my ISP and my Router company it is nothing on mine or their end. There is some where I am getting routed though in LA that every night makes the lag so bad I just want to close my 3 accounts because I cant even play. I have 4 or 5 guildies that live within 30 mintues of where I live and they are expierencing the exact same problem. I was wondering if anybody else has had the same problem and if they were able to do any thing?

I actually lag so bad I get disconnected . sometimes the connection will be fine all day and other times it will disconnect me every 2 minutes rebooting the computer, modem, and router helps sometimes.

 

[virtualhabitat]

Great Lakes is completely unplayable for me at the moment

 

[Orgional Farimir]

Great Lakes is completely unplayable for me at the moment

Even though I live in the midwest I get better ping to ATL and west coast shards than I do GL.

But they did say a month ago they will look into it soon so I don't know why everyone is so pushy..... It isn't like we pay for this game or anything.

 

[Obsidian]

I live just north of Los Angles and my ping to all west coast servers has been unbearable the last week during prime time. But my connection to the East Coast has been great. There appears to be a connection issue affecting traffic through the LA area.

 

[Emil Ispep]

Yea, still no relief in sight. I have the same lag problems.. trying to connect to Pacific from Chicago. Its usually no prob, and lag free.. then came the dark cloud. Ever since about 2 or 3 weeks ago, i get the same problem everyone is describing.. lag for 15 seconds-2 minutes.

Has there been any word on this from a dev at all? Is anyone looking into this at all? If this is going to be the new UO, think im done.

Another great move by the NBAs at EA. Take a bow.

 

[TheRudeX]

Yeah I really do hope they fix it. I played all day for about 6 solid hours now its prime time about 6:30 pac time and once again I cant even move......

 

[TheRudeX]

I just now checked Atl and even in the middle of luna zero lag. So it has to be something with one of EA's servers. I hope it gets fixed. I really dont want to move house and home just for a silly laggy issue that is EA's problem...

 

[Obsidian]

There is acknowledgement by Bleak in this thread: http://stratics.com/community/index.php?threads/Some-Serious-Lag-on-Napa-Lately.294679/

 

[Bleak]

Those having issues can you please provide exact information on what shard is having the issue, what time lag occurred, duration of lag period, traceroute to the server during the time period, and any other useful information.

Thanks for you help in advance.

 

[Leira of Asrai]

support@ultimaonline is a joke. I emailed them about this issue about 2 weeks ago and I have only received 1 reply saying they are elevating the issue to a higher level... If this has been a known issue for several months, you would think they could be quicker in notifying me... Leave it to the player base to come with the information we rely on...

anyway I play Pacific almost exclusively and have been having the issue for about 3-4 weeks.
Details are:
Enhanced Client (haven't tested CC)
Typically no issues during the day (off peak periods)
Shards I have tested and have lag: Pacific, Baja, Napa Valley and Origin
Shards I have tested and have NO lag: Atlantic, Chesapeake, Great Lakes, Lake Superior and Seige Perilous.
I connect from home in Denver, CO.
Log in latency screen will sometimes not populate with latency, sometimes will show adequate latency (50-70) and sometimes show massive latency (3000+)

*Minor Lag begins around 3-4pm PST and includes occaisonal character freezing for 1 second and maybe increased rubberbanding.
[game is playable, but annoying]
*Major Lag occurs during 4-7pm PST and includes frequent character freezing for 1 second and occiasonal character freezing of 2-6 seconds. I freeze about every 10 paces. Bags take longer to open; houses take longer to load; Chat windows/Journal windows delay with updating recent comments; upon logging in, character on screen will not appear dressed; upon logging in, pet health bars will have border, but no name.
[game is playable only if you don't open containers, run too far or engage in combat.]
*Extreme lag occurs during 7-... PST and includes frequent character freezing about every 3 paces and freezing for about 10 seconds-2 minutes. I experienced occaisonal freezes of about 5-8 minutes. Bags will take 2+minutes to open. It only releases to catch up and re-freezes.
[game is completely unplayable and encourages me to demand my monthly fees reimbursed]

Hopefully they will identify the issue and resolve it quickly before I quit UO (again).

 

[Eric Ravenwind]

Those having issues can you please provide exact information on what shard is having the issue, what time lag occurred, duration of lag period, traceroute to the server during the time period, and any other useful information.

Thanks for you help in advance.

How do you traceroute?

 

[TheRudeX]

This is a freaking joke!! ... Once again had a day off played all day and about 6 o'clock pac time rolls around, and oh wow lagg!!! its time to go watch tv, I guess.

I have to edit this a little and say thanks to bleak for responding and showing some concern and intrest. Hope you can fix it.

 

[TheRudeX]

How do you traceroute?

open the command prompt and type: tracert (shardname).owo.com
for example for pacific it would be: tracert pacific.owo.com

 

[NuSair]

Had several 20+ second lag issues today.... one was so bad that corpses at a champ spawn disappeared before I could try to loot them. That is, I killed them, the lag hit, they disappeared before I could loot the bodies.

 

[TheRudeX]

Those having issues can you please provide exact information on what shard is having the issue, what time lag occurred, duration of lag period, traceroute to the server during the time period, and any other useful information.

Thanks for you help in advance.

Pacific shard every night from about 5pm till 1am local time
the second I hit edge01.eqx-sjc.ea.com i get nothing but requests time outs

 

[Eric Ravenwind]

Greatlakes traceroute said it had 30 hops, butt-load of timeouts then it just shut off. How do you copy the trace info. to this post?

 

[TheRudeX]

Greatlakes traceroute said it had 30 hops, butt-load of timeouts then it just shut off. How do you copy the trace info. to this post?

You're able to do a right click and select all from there then you have to a ctrl+c then come here and ctrl+v it and from there you can edit out any personal info likename on the comp ect.

 

[Eric Ravenwind]

You're able to do a right click and select all from there then you have to a ctrl+c then come here and ctrl+v it and from there you can edit out any personal info likename on the comp ect.

unable to right-click and select all. Ctrl+C closes the commandline

Also, the trace wants 30 hops, but it shuts down around 14 hops

 

[Love them Redheads]

I'm in the same area as the OP.

Comcast internet.

Pacific shard.

Don't know what it's like during the day or in the middle of the night as I go to work to earn money to pay you for this laggy game. From 6pm to midnight MST it's a joke and has been long before this latest problem.

Cloud + ALTERNET = End of UO.

Trace I just ran using cmd prompt and tracert 65.216.123.25


6 21 ms 57 ms 21 ms xe-5-0-2-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.82.202]
7 21 ms 21 ms 25 ms 173.167.58.162
8 48 ms 96 ms 51 ms if-4-0-1-0.tcore1.CT8-Chicago.as6453.net [209.58.57.130]
9 61 ms 59 ms 59 ms 64.86.78.30
10 75 ms 131 ms 102 ms 0.xe-2-0-0.XT1.LAX7.ALTER.NET [152.63.1.209]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 so-0-0-0.ur1.lax11.web.wcom.net [208.222.8.22] reports: Destination net unreachable.
Yep....really looks awesome huh

 

[Love them Redheads]

unable to right-click and select all. Ctrl+C closes the commandline

You're running the trace from the Run command.

Instead open that run command and type cmd

Then run the trace

 

[Eric Ravenwind]

Shard: Great Lakes
Provider: Verizon

Lag got bad for me around 6:30pm - 7:00pm EST.

How's mine look?

Tracing route to greatlakes.owo.com [#####]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter [#####]
2 34 ms 34 ms 33 ms 10.25.3.1
3 34 ms 34 ms 35 ms at-2-3-0-1712.BING-CORE-RTR1.verizon-gni.net [13
0.81.194.64]
4 36 ms 37 ms 37 ms ge-2-1-1-0.BING-CORE-RTR2.verizon-gni.net [130.8
1.18.164]
5 51 ms 51 ms 50 ms so-7-2-1-0.NY5030-BB-RTR2.verizon-gni.net [130.8
1.20.98]
6 127 ms 127 ms 130 ms 0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237]
7 * * * Request timed out.
8 131 ms 131 ms 131 ms dca2-edge-01.inet.qwest.net [67.14.36.10]
9 182 ms 155 ms 154 ms 72.165.86.74
10 168 ms 177 ms 167 ms 72.21.220.127
11 155 ms 155 ms 157 ms 205.251.245.53
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 145 ms 143 ms 146 ms ec2-107-21-7-214.compute-1.amazonaws.com [107.21
.7.214]
Trace complete.

 

[virtualhabitat]

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

C:\Users\>tracert greatlakes.owo.com

Tracing route to greatlakes.owo.com [107.21.7.214]
over a maximum of 30 hops:

1 * * * Request timed out.
2 10 ms 25 ms 9 ms ##-##-##-###.static.grandenetworks.net [##.##.#
##.##]
3 12 ms 12 ms 15 ms ge-5-1-0-0.SNANTXCW.core01.gf01.dllstx.grandecom
.net [24.155.121.90]
4 49 ms 47 ms 48 ms equinix02-iad2.amazon.com [206.126.236.35]
5 95 ms 55 ms 54 ms 72.21.220.47
6 52 ms 51 ms 50 ms 205.251.245.55
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 50 ms 50 ms 51 ms ec2-107-21-7-214.compute-1.amazonaws.com [107.21
.7.214]

Trace complete.

C:\

 

[claudia-fjp]

There were also threads about this in October and December. It's been happening for months and has only gotten worse. Each time the problem seems to point to a constant packet loss during the west coast prime time in the LAX7.ALTER.NET server. The move to the cloud seems to have only made it worse with new weird stuff happening. I've been watching with the old UO Trace Utility Program for months doing a trace route to the server then polling to find the % packet loss, most nights it was 5-10%. Tonight I can't get the trace to go through like the others.

http://stratics.com/community/threa...-or-the-rest-of-the-area.289223/#post-2206696

http://stratics.com/community/threa...0-ur1-lax11-web-wcom-net.285939/#post-2186524

http://stratics.com/community/threads/im-done.287323/#post-2195118

plus a half dozen more threads...

 

[Obsidian]

I've had very bad lag during primetime on Origin and Napa Valley, but no problem at all while on Atlantic. Comcast is my ISP and I am on the West Coast. Here is a tracert to Origin with a few lines removed for my local IP and router.

C:\Users\>tracert origin.owo.com

Tracing route to central-aw6.owo.com [159.153.209.66]
over a maximum of 30 hops:

  4    14 ms    18 ms    10 ms  te-7-4-ur01.santamaria.ca.sfba.comcast.net [68.8
7.196.137]
  5    17 ms    18 ms    21 ms  te-1-2-0-5-ar01.sfsutro.ca.sfba.comcast.net [68.
85.154.2]
  6    31 ms    24 ms    23 ms  he-3-8-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.94.85]
  7    26 ms    23 ms    23 ms  pos-0-3-0-0-pe01.11greatoaks.ca.ibone.comcast.ne
t [68.86.87.18]
  8    36 ms    20 ms    21 ms  as1239.11greatoaks.ca.ibone.comcast.net [173.167
.56.254]
  9    20 ms    21 ms    20 ms  sl-st21-sj-2-0-0.sprintlink.net [144.232.0.205]

 10    22 ms    21 ms    22 ms  144.223.242.22
 11   233 ms   193 ms   221 ms  edge01.eqx-sjc.ea.com [159.153.192.234]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 

[Tina Small]

Info on how to run a trace route and what are, hopefully, the most current server addresses are here on Stratics: http://uo2.stratics.com/technical-information/server-ip-addresses . I know Lord Obsidian tracked down a new IP address in December for the Atlantic server and posted it in early December. The address he posted then is the one that is on the above-mentioned Stratics page, which was last updated February 1, 2013. Maybe when Bleak gets back to work in the morning (it's about 12:30 early morning for him now), he can confirm that those addresses are indeed the right ones to use.

Edited to add: In case you miss it on the Stratics page, if you're just skimming it, the first paragraph states that "the 'shard.owo.com' DNS names are now redundant, though still in existence. Any application using those will return false and irrelevant results."

 

[Lord Obsidian]

Info on how to run a trace route and what are, hopefully, the most current server addresses are here on Stratics: http://uo2.stratics.com/technical-information/server-ip-addresses .

I verified all IPs again today, so those should be the most current addresses. I continually try to keep this list updated.

Edited to add: In case you miss it on the Stratics page, if you're just skimming it, the first paragraph states that "the 'shard.owo.com' DNS names are now redundant, though still in existence. Any application using those will return false and irrelevant results."

This information is out of an earlier version of my list where all .owo.com addresses resolved to wrong IPs. Lately, a few of them have been updated, but I would still recommend using the raw IPs.

Other Useful information: This trace was done to the Pacific shard at 54.241.133.251 which was obtained by netstat -a.

While "netstat -a" will give you the IP you are actually connected to, you can only trace it down to the second last hop. You will get no answer from the server itself because ICMP Ping is disabled on those IPs.


I started a new char on Pacific some days ago and experienced the same issues there (lag, up to complete freezes). I will try to give more details on that as soon as I find the time to play again.

*Minor Lag begins around 3-4pm PST ...
*Major Lag occurs during 4-7pm PST ...
*Extreme lag occurs during 7-...

fixed to keep it in the usual ingame naming:
*Legendary lag occurs...

 

[Bleak]

Info on how to run a trace route and what are, hopefully, the most current server addresses are here on Stratics: http://uo2.stratics.com/technical-information/server-ip-addresses . I know Lord Obsidian tracked down a new IP address in December for the Atlantic server and posted it in early December. The address he posted then is the one that is on the above-mentioned Stratics page, which was last updated February 1, 2013. Maybe when Bleak gets back to work in the morning (it's about 12:30 early morning for him now), he can confirm that those addresses are indeed the right ones to use.

Edited to add: In case you miss it on the Stratics page, if you're just skimming it, the first paragraph states that "the 'shard.owo.com' DNS names are now redundant, though still in existence. Any application using those will return false and irrelevant results."

Yes, please use the ip addresses listed on the Stratics page above for the traceroutes.

 

[Arrgh]

Those having issues can you please provide exact information on what shard is having the issue, what time lag occurred, duration of lag period, traceroute to the server during the time period, and any other useful information.

Thanks for you help in advance.

First trace is for Atlantic server @11:46 am CST; second trace is for Lake Austin @roughly 11:48 CST

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

Atlantic Server.

C:>tracert 107.23.95.234

Tracing route to ec2-107-23-95-234.compute-1.amazonaws.com [107.23.95.234]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 10 ms 15 ms 15 ms
3 9 ms 13 ms 11 ms
4 11 ms 11 ms 13 ms
5 15 ms 16 ms 12 ms h117.118.190.173.static.ip.windstream.net [173.1
90.118.117]
6 46 ms 61 ms 45 ms h211.222.90.75.static.ip.windstream.net [75.90.2
22.211]
7 15 ms 18 ms 30 ms h176.255.90.75.dynamic.ip.windstream.net [75.90.
255.176]
8 44 ms 42 ms 48 ms te4-2.lenxks02la1.nw.nuvox.net [173.221.1.181]
9 47 ms 48 ms 62 ms te9-2d3000.lenxks02la2.nw.nuvox.net [173.221.1.2
41]
10 50 ms 53 ms 47 ms 173.221.1.174.nw.nuvox.net [173.221.1.174]
11 46 ms 50 ms 47 ms h128.254.213.151.static.ip.windstream.net [151.2
13.254.128]
12 43 ms 47 ms 93 ms xe-8-3-0.edge3.Dallas1.Level3.net [4.71.198.25]

13 73 ms 140 ms 74 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
14 76 ms 73 ms 82 ms ae-93-93.ebr3.Dallas1.Level3.net [4.69.151.170]

15 83 ms 83 ms 79 ms ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
16 76 ms 87 ms 88 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

17 80 ms 82 ms 79 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.1
34]
18 76 ms 79 ms 77 ms ae-2-70.edge2.Washington1.Level3.net [4.69.149.7
8]
19 62 ms 61 ms 60 ms AMAZON.COM.edge2.Washington1.Level3.net [4.79.22
.86]
20 61 ms 63 ms 64 ms 72.21.220.151
21 63 ms 63 ms 61 ms 72.21.222.157
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 63 ms 59 ms 60 ms ec2-107-23-95-234.compute-1.amazonaws.com [107.2
3.95.234]

Trace complete.

LAKE AUSTIN BELOW.

C:>tracert 54.241.143.226

Tracing route to ec2-54-241-143-226.us-west-1.compute.amazonaws.com [54.241.143.
226]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 12 ms 11 ms
3 14 ms 11 ms 31 ms
4 33 ms 14 ms 10 ms
5 12 ms 14 ms 14 ms h117.118.190.173.static.ip.windstream.net [173.1
90.118.117]
6 43 ms 45 ms 81 ms h211.222.90.75.static.ip.windstream.net [75.90.2
22.211]
7 19 ms 16 ms 20 ms h176.255.90.75.dynamic.ip.windstream.net [75.90.
255.176]
8 46 ms 56 ms 44 ms te4-2.lenxks02la1.nw.nuvox.net [173.221.1.181]
9 50 ms 47 ms 50 ms te9-2d3000.lenxks02la2.nw.nuvox.net [173.221.1.2
41]
10 57 ms 49 ms 52 ms 173.221.1.174.nw.nuvox.net [173.221.1.174]
11 67 ms 64 ms 46 ms h128.254.213.151.static.ip.windstream.net [151.2
13.254.128]
12 42 ms 44 ms 45 ms xe-8-3-0.edge3.Dallas1.Level3.net [4.71.198.25]

13 90 ms 91 ms 87 ms vlan70.csw2.Dallas1.Level3.net [4.69.145.126]
14 95 ms 91 ms 91 ms ae-73-73.ebr3.Dallas1.Level3.net [4.69.151.146]

15 85 ms 86 ms 88 ms ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]

16 87 ms 92 ms 83 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
17 92 ms 89 ms 91 ms ae-2-2.ebr2.SanJose1.Level3.net [4.69.148.142]
18 84 ms 98 ms 85 ms ae-62-62.csw1.SanJose1.Level3.net [4.69.153.18]

19 84 ms 83 ms 85 ms ae-22-60.car2.SanJose2.Level3.net [4.69.152.12]

20 88 ms 92 ms 85 ms AMAZON.COM.car2.SanJose2.Level3.net [4.59.4.10]

21 89 ms 87 ms 88 ms 205.251.229.40
22 87 ms 88 ms 92 ms 205.251.229.106
23 89 ms 88 ms 94 ms ec2-54-241-143-226.us-west-1.compute.amazonaws.c
om [54.241.143.226]

Trace complete.

Will do them again later tonight, as the lag gets worse. Thanks for looking into this Bleak!

 

[Emil Ispep]

Can we get a server revert? Like can you take the servers off of the cloud?

 

[Arrgh]

Those having issues can you please provide exact information on what shard is having the issue, what time lag occurred, duration of lag period, traceroute to the server during the time period, and any other useful information.

Thanks for you help in advance.

11:53PM CST

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



C:\>tracert 107.23.95.234

Tracing route to ec2-107-23-95-234.compute-1.amazonaws.com [107.23.95.234]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 12 ms 12 ms 17 ms
3 13 ms 25 ms 12 ms
4 13 ms 11 ms 15 ms
5 16 ms 12 ms 13 ms h117.118.190.173.static.ip.windstream.net [173.1
90.118.117]
6 46 ms 57 ms 87 ms h211.222.90.75.static.ip.windstream.net [75.90.2
22.211]
7 18 ms 16 ms 20 ms h176.255.90.75.dynamic.ip.windstream.net [75.90.
255.176]
8 47 ms 47 ms 46 ms te4-2.lenxks02la1.nw.nuvox.net [173.221.1.181]
9 51 ms 49 ms 55 ms te9-2d3000.lenxks02la2.nw.nuvox.net [173.221.1.2
41]
10 50 ms 49 ms 48 ms 173.221.1.174.nw.nuvox.net [173.221.1.174]
11 46 ms 48 ms 52 ms h128.254.213.151.static.ip.windstream.net [151.2
13.254.128]
12 44 ms 47 ms 43 ms xe-8-3-0.edge3.Dallas1.Level3.net [4.71.198.25]

13 95 ms 74 ms 75 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
14 76 ms 80 ms 76 ms ae-93-93.ebr3.Dallas1.Level3.net [4.69.151.170]

15 82 ms 81 ms 107 ms ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
16 74 ms 71 ms 74 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

17 80 ms 82 ms 78 ms ae-71-71.csw2.Washington1.Level3.net [4.69.134.1
34]
18 77 ms 78 ms 76 ms ae-2-70.edge2.Washington1.Level3.net [4.69.149.7
8]
19 60 ms 59 ms 60 ms AMAZON.COM.edge2.Washington1.Level3.net [4.79.22
.86]
20 63 ms 60 ms 64 ms 72.21.220.151
21 62 ms 60 ms 65 ms 72.21.222.157
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 60 ms 60 ms 66 ms ec2-107-23-95-234.compute-1.amazonaws.com [107.2
3.95.234]

Trace complete.

C:\>tracert 54.241.143.226

Tracing route to ec2-54-241-143-226.us-west-1.compute.amazonaws.com [54.241.143.
226]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms
2 13 ms 11 ms 17 ms
3 38 ms 12 ms 31 ms
4 10 ms 13 ms 12 ms
5 16 ms 13 ms 14 ms h117.118.190.173.static.ip.windstream.net [173.1
90.118.117]
6 45 ms 44 ms 76 ms h211.222.90.75.static.ip.windstream.net [75.90.2
22.211]
7 18 ms 14 ms 17 ms h176.255.90.75.dynamic.ip.windstream.net [75.90.
255.176]
8 45 ms 44 ms 43 ms te4-2.lenxks02la1.nw.nuvox.net [173.221.1.181]
9 47 ms 49 ms 47 ms te9-2d3000.lenxks02la2.nw.nuvox.net [173.221.1.2
41]
10 53 ms 48 ms 48 ms 173.221.1.174.nw.nuvox.net [173.221.1.174]
11 78 ms 48 ms 51 ms h128.254.213.151.static.ip.windstream.net [151.2
13.254.128]
12 45 ms 46 ms 44 ms xe-8-3-0.edge3.Dallas1.Level3.net [4.71.198.25]

13 91 ms 87 ms 93 ms vlan70.csw2.Dallas1.Level3.net [4.69.145.126]
14 91 ms 88 ms 90 ms ae-73-73.ebr3.Dallas1.Level3.net [4.69.151.146]

15 90 ms 89 ms 85 ms ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]

16 84 ms 85 ms 84 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
17 94 ms 90 ms 92 ms ae-2-2.ebr2.SanJose1.Level3.net [4.69.148.142]
18 87 ms 141 ms 88 ms ae-62-62.csw1.SanJose1.Level3.net [4.69.153.18]

19 88 ms 84 ms 86 ms ae-22-60.car2.SanJose2.Level3.net [4.69.152.12]

20 114 ms 110 ms 87 ms AMAZON.COM.car2.SanJose2.Level3.net [4.59.4.10]

21 89 ms 86 ms 87 ms 205.251.229.40
22 88 ms 85 ms 131 ms 205.251.229.106
23 90 ms 85 ms 89 ms ec2-54-241-143-226.us-west-1.compute.amazonaws.c
om [54.241.143.226]

Trace complete.

C:\>

 

[cdavbar]

Those having issues can you please provide exact information on what shard is having the issue,

Great Lakes

what time lag occurred,

This tracerout was performed within a few minutes after shard came up from mait on 2/23/13 but Great Lakes is having horrible lag throughout the entire day.

duration of lag period,

Lately has been an all day occurance with brief periods of little to no lag here and there.

traceroute to the server during the time period,

Trace route results using UOTrace are below. Trace route was performed using the correct IP listed on teh Stratics page noted in the above posts.

Here are my results to Great Lakes. This was performed a few minutes after the shard opened back up this morning (2/23/13).

Host Name                        IP Address        Hop    Ping Time  Ping Avg  % Loss    Pkts r/s  Ping best/worst
* Unknown Host *                0.0.0.0          1      0ms
ae0-1258.cr02.clmkohpe.midohio.rr184.59.243.125    2      28ms        17ms      0%        21 / 21    9ms / 30ms
network-065-029-001-034.midwest.r65.29.1.34        3      21ms        17ms      0%        21 / 21    11ms / 24ms
ae-9-0.cr0.chi30.tbone.rr.com    107.14.19.16      4      21ms        27ms      0%        21 / 21    21ms / 43ms
ae-0-0.cr0.chi10.tbone.rr.com    66.109.6.20      5      50ms        48ms      0%        21 / 21    39ms / 63ms
* Unknown Host *                107.14.17.192    6      41ms        45ms      0%        21 / 21    37ms / 75ms
chi-bb1-link.telia.net          213.248.66.193    7      39ms        40ms      0%        21 / 21    37ms / 50ms
chi-bb1-link.telia.net          80.91.246.172    8      37ms        41ms      0%        21 / 21    35ms / 69ms
nyk-bb1-link.telia.net          80.91.246.163    9      100ms      52ms      0%        21 / 21    28ms / 108ms
ash-bb3-link.telia.net          213.155.134.149  10    26ms        33ms      0%        21 / 21    22ms / 76ms
ash-bb1-link.telia.net          80.91.248.157    11    42ms        53ms      0%        21 / 21    35ms / 113ms
vadata-ic-157230-ash-bb1.c.telia.213.248.94.50    12    49ms                  100%      0 / 20
* Unknown Host *                72.21.220.39      13    82ms                  100%      0 / 20
* Unknown Host *                205.251.245.55    14    38ms                  100%      0 / 20
* Unknown Host *                0.0.0.0          15    0ms
* Unknown Host *                0.0.0.0          16    0ms
* Unknown Host *                0.0.0.0          17    0ms
ec2-107-21-7-214.compute-1.amazon107.21.7.214      18    38ms        40ms      0%        20 / 20    38ms / 52ms

 

[Bleak]

We have made some adjustments to our west coast servers as of this morning. Please let us know if you are still experiencing bad lag issues on those shards.

 

[cdavbar]

We have made some adjustments to our west coast servers as of this morning. Please let us know if you are still experiencing bad lag issues on those shards.

When are East Coast servers going to get some love?

 

[Eric Ravenwind]

Another report.

Shard: Great Lakes
Provider: Verizon
Time: 9:30pm EST

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\#####>tracert greatlakes.owo.com
Tracing route to greatlakes.owo.com [#######]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter [192.168.1.1]
2 34 ms 33 ms 35 ms 10.25.3.1
3 35 ms 35 ms 34 ms at-2-3-0-1713.BING-CORE-RTR2.verizon-gni.net [13
0.81.194.66]
4 51 ms 50 ms 51 ms so-7-2-1-0.NY5030-BB-RTR2.verizon-gni.net [130.8
1.20.98]
5 127 ms 127 ms 127 ms 0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237]
6 * 129 ms * 63-235-40-53.dia.static.qwest.net [63.235.40.53]
7 130 ms * 131 ms dca2-edge-01.inet.qwest.net [67.14.36.10]
8 185 ms 145 ms 142 ms 72.165.86.74
9 136 ms 135 ms 135 ms 72.21.220.127
10 151 ms 154 ms 152 ms 205.251.245.53
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 153 ms 152 ms 154 ms ec2-107-21-7-214.compute-1.amazonaws.com [107.21
.7.214]
Trace complete.
C:\Users\#####>

 

[TheRudeX]

7:30 EST on Napa and running smooth. I'll give an update from Baja in a few hours.

edit: almost 8:00 EST and Napa slowing down a bit.

edit2: 8:35 EST and Napa is lagging up quite hard. Don't think the fix did much/anything.

edit3: 8:50 EST Baja unplayable.

edit4: 10:05 EST Baja, Napa, LA, etc. all west coast servers unplayable.

That about sums up my expierences as well tonight.

 

[cutty]

We have made some adjustments to our west coast servers as of this morning. Please let us know if you are still experiencing bad lag issues on those shards.

Still pretty bad for me at least:
Napa Valley Shard 2-23-13 10:00pm PST

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

C:\Users\Jim>tracert 54.241.138.28

Tracing route to ec2-54-241-138-28.us-west-1.compute.amazonaws.com [54.241.138.2
8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms L100.LSANCA-VFTTP-111.verizon-gni.net [98.119.15
5.1]
3 17 ms 11 ms 19 ms G0-10-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.
138.64]
4 9 ms 9 ms 8 ms ae2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.209.
254]
5 26 ms 22 ms 31 ms 0.so-2-2-0.XL4.LAX15.ALTER.NET [152.63.10.121]
6 21 ms 25 ms 18 ms TenGigE0-5-4-0.GW4.LAX15.ALTER.NET [152.63.115.2
46]
7 16 ms 9 ms 18 ms teliasonera-gw.customer.alter.net [152.179.21.42
]
8 27 ms 29 ms 27 ms sjo-bb1-link.telia.net [213.155.135.189]
9 36 ms 21 ms 28 ms a100us-ic-151265-sjo-bb1.c.telia.net [80.239.128
.134]
10 30 ms 28 ms 28 ms 205.251.229.163
11 160 ms 151 ms 147 ms 205.251.229.233
12 149 ms 148 ms 154 ms ec2-54-241-138-28.us-west-1.compute.amazonaws.co
m [54.241.138.28]

Trace complete.

 

[mcnubbins]

Nasty shardwide lag spikes on Catskills tonight. I'm in Pittsburgh, PA.

 

[Eric Ravenwind]

Shard: Great Lakes
Provider: Verizon
Time: 11:45am EST

Multiple Crashes and horrible lag.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\#####>tracert greatlakes.owo.com
Tracing route to greatlakes.owo.com [##############]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter [192.168.1.1]
2 34 ms 33 ms 35 ms 10.25.3.1
3 35 ms 35 ms 34 ms at-2-3-0-1713.BING-CORE-RTR2.verizon-gni.net [13
0.81.194.66]
4 51 ms 50 ms 51 ms so-7-2-1-0.NY5030-BB-RTR2.verizon-gni.net [130.8
1.20.98]
5 127 ms 127 ms 127 ms 0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237]
6 * 129 ms * 63-235-40-53.dia.static.qwest.net [63.235.40.53]
7 130 ms * 131 ms dca2-edge-01.inet.qwest.net [67.14.36.10]
8 185 ms 145 ms 142 ms 72.165.86.74
9 136 ms 135 ms 135 ms 72.21.220.127
10 151 ms 154 ms 152 ms 205.251.245.53
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 153 ms 152 ms 154 ms ec2-107-21-7-214.compute-1.amazonaws.com [107.21
.7.214]
Trace complete.
C:\Users\############>

 

[cdavbar]

Bleak_Mythic,

I think this takes precedence over Pub 81. As excited as I am for some of the changes, it all needs to be put on the back-burner until we can actually have playable servers.

 

[Eric Ravenwind]

It's 6:15pm EST - I've locked up and disconnected a total of 17 times since 4pm. On Great Lakes.

 

[cdavbar]

I am positive that it is currently being worked on.

Judging by the replies in this thread vs replies in Pub 81 threads by devs, Pub 81 seems to be more of a priority. No one will care what is in the publish if we can't play. We should also not have to invest in a VPN just to play without lag spikes/disconnects.

 

[Tina Small]

Getting bad lag, freezing, etc., while trying to play on Sakura for a bit this evening.

Host Name                                         IP Address        Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst

he-3-9-0-0-cr01.denver.co.ibone.comcast.net       68.86.92.21       4      25ms        76ms       0%        68 / 68    15ms / 732ms
* Unknown Host *                                  4.79.82.57        5      20ms        67ms       0%        67 / 67    12ms / 912ms
vlan51.ebr1.Denver1.Level3.net                    4.69.147.94       6      16ms        69ms       0%        67 / 67    13ms / 571ms
ae-3-3.ebr2.SanJose1.Level3.net                   4.69.132.57       7      401ms       113ms      0%        67 / 67    54ms / 691ms
ae-92-92.csw4.SanJose1.Level3.net                 4.69.153.30       8      792ms       121ms      0%        67 / 67    58ms / 792ms
ae-4-90.edge1.SanJose2.Level3.net                 4.69.152.199      9      819ms       129ms      1%        66 / 67    57ms / 819ms
KDDI-AMERIC.edge1.SanJose2.Level3.net             4.28.172.22       10     367ms       127ms      0%        67 / 67    39ms / 917ms
pajbb001.int-gw.kddi.ne.jp                        111.87.3.41       11     542ms       139ms      0%        67 / 67    50ms / 926ms
otejbb205.int-gw.kddi.ne.jp                       203.181.100.1     12     525ms       216ms      0%        67 / 67    144ms / 857ms
sjkBBAC05.bb.kddi.ne.jp                           118.152.210.102   13     584ms       228ms      0%        67 / 67    157ms / 924ms
* Unknown Host *                                  118.152.254.74    14     1009ms      228ms      0%        66 / 66    155ms / 1009ms
cm-sjk215.kddnet.ad.jp                            113.157.224.34    15     604ms       203ms      0%        66 / 66    146ms / 744ms
* Unknown Host *                                  125.29.24.146     16     410ms       204ms      0%        66 / 66    137ms / 724ms
* Unknown Host *                                  159.153.172.62    17     626ms       215ms      0%        66 / 66    156ms / 860ms
* Unknown Host *                                  159.153.169.71    18     483ms       200ms      0%        65 / 65    149ms / 685ms

 

[cdavbar]

Petra, can this get stickied, even if only temporary while the devs work on this? This will make it much easier for them to get the traces they are looking for and easier for them to respond to use about the issue.

 

[cdavbar]

Any news yet devs?

This is getting entirely ridiculous. Last night on Great Lakes Mesanna was on during our event to "check into the lag" but did not take our invitation to the actual event so she could see how unbearable it was. Then later on while some of us were trying to refresh our focus at West Brit Bank, we kept locking up every thirty seconds, the lockups lasted anywhere from a few seconds to at one point over a 2 minutes (once we recalled away from the city the lag got better).

This lag and lock-up across all shards is not just ruining normal game-play, but it is also destroying events. Take last nights event for example, only 15 event items dropped. This would normally be fine but with everyone lagging and locking up, how in the heck is anyone supposed to compete? Instead of top attackers, it is becoming lowest packet losers get the drops. I normally wouldn't complain about an item, but people are not able to even compete anymore due to the lock ups and lag.

Please fix this issue fast!

Please sticky this or a new thread so that the devs have a central place to continue discussion on this matter!

 

[Emil Ispep]

Still no relief in sight for me on Pacific. Best bet is for me to play in the early morning hours. Unfort i can only do that on weekends. Otherwise the lag is totally ruining EM and guild events during peak-hours.

 

[Emil Ispep]

Tues night... lag is still here. Any updates from anyone? I saw some "Hardware Improvement" posts... but no help here =/.

Getting ready to throw in the towel. Im paying 30/month for this scake?

 

[Leira of Asrai]

There must be a major communication disconnect between the UO Producers, software engineers and online email support staff. This game has become completely unplayable.

Jan 18 Mesanna announces in a letter "...we are moving off the old servers onto the Cloud. With a game as old as UO it has been challenging but we are working hard to iron out the kinks."

I immediately notice Major lag on west coast shards, connecting from the mid-west. I update my drivers and contact my ISP... nope, it's not on my side.

Feb 12 I email [email protected] to report the major lag and my efforts to rule out my system. I'm told they will review the information.

Feb 14 I receive a canned reply to my email "I'm going to escalate this issue to the higher department..." (english not your primary language?)

Feb 20 I find this post in the UHall forums where other players confirm the lag issue and software engineers confirm it is a known issue.

Feb 22 I paged a GM to find out further information. They don't respond very quickly.

Feb 25 The GM finally responds in game and confirms it is a known issue and that he doesn't know what work is being done. He suggests checking The Herald uo.com for updates.

Feb 26 Mesanna posts on The Herald that they are working on the lag issues.

Feb 27 Baja and Great Lakes get 'Hardware Improvements', but the lag issue remains.

Feb 28 Napa Valley gets the 'Hardware Improvement', but still no change in the lag.

Feb 28 I receive a reply to my original email (16 days later). Their reply states "We have investigated this matter and cannot locate the cause for these disruptions." Huh? really? They have no idea what's causing my lag issues, so they close out the ticket with "you're SOL"!

Since the beginning of the lag issue I have payed 2 monthly subscriptions on two accounts, and I'm still unable to play on my primary shard except on weekend mornings.

Please someone at UO fix this issue, quickly!

 

[Cetric]

none of this lag has been fixed from what i can figure out.