Regarding Lag

CuddlyFriction · Sep 10, 2010

Re: Regarding Lag

Countessa;2066655 said:
Please, do not make anymore threads about lag.

We are aware some of you are experiencing problems.
Currently the server is as it should be.

If you are having lag problems, post a traceroute in this thread.
Most of the time, lag problems are a problem with your ISP, or with an ISP between you and the server that none of us have control over.
Very rarely there is a problem on our ISP's end, and seeing traceroutes can help us bring it to their attention.

To run a traceroute:

Press "Start" in Windows

Press "Run..."

Type "Cmd" and press "OK"

IN the box that pops up type tracert login.uogamers.com

possibly a easiler way is

Windows key+ R then type in that window either Cmd or tracert login.uogamers.com

if you pick to type cmd you taking the long route and it doesnt always work on my machine for somereason maybe cause im running windows 7(solved i was sayying tracer) :tongue_smilie:

I use to for it for shutdowns windows key+R then type shutdown -i (for other computers) or just shutdown /s

Using windows+R key instead of start>run cuts alot of corners another way to cut corners posted below
YouTube - how to write batch files

Mara · Sep 16, 2010

Re: Regarding Lag

I've been having packetloss for the last few days, off and on, about 1-10%. The tracert indicates that it is occuring close to and at the server. Not really much point in posting the traceroute and ping tests at the moment. Will see if it clears up.

WillyDaSquid · Sep 16, 2010

Re: Regarding Lag

Yeah, I'm not one to usually complain. There has been real bad lag for me for the last few days. I am usually sitting pretty low with ping. It has been unplayable for me.

Dany Mortal · Sep 16, 2010

Re: Regarding Lag

it's kinda odd, almost everyone i talk to is talking about lag, but my ping is actually lower..instead of 45-60 im going 30-45 lol

Mara · Sep 16, 2010

Re: Regarding Lag

My ping is about the same, when it actually gets through and comes back. Maybe a couple ms higher than normal at times, but the packetloss is what I think is killing me.

WillyDaSquid · Sep 16, 2010

Re: Regarding Lag

Should the players who are experiencing lag expect a fix? Lots of people are telling me that the staff is saying there isn't a problem. 8/10 I talk to are having lag issues the past few days. I shouldn't be going off hearsay, but I won't ever be able to play again like this.

I'm sure they'd be willing to drop a line in this thread to inform the staff of the issue.

Countessa · Sep 19, 2010

Re: Regarding Lag

Countessa;2066655 said:
Please, do not make anymore threads about lag.

We are aware some of you are experiencing problems.
Currently the server is as it should be.

If you are having lag problems, post a traceroute in this thread.
Most of the time, lag problems are a problem with your ISP, or with an ISP between you and the server that none of us have control over.
Very rarely there is a problem on our ISP's end, and seeing traceroutes can help us bring it to their attention.

To run a traceroute:

Press "Start" in Windows

Press "Run..."

Type "Cmd" and press "OK"

IN the box that pops up type tracert login.uogamers.com

Let the trace run, while it is running, expand the height of the window so that all the results can be seen at once.

Right click on the window's title and go to "Edit" and select "Mark"

Highlight the results of the trace and press ENTER

Create a reply in this thread and paste the results of the trace INSIDE OF [ code] and [/code] tags. The code tags are important because the trace is VERY hard to read without them. Please do not forget the code tags!

Do not expect a response from staff to every post in this thread. We will read the traces, but we do not have time to respond to everyone individually.

Thank you.

.

makeemsayuhh · Sep 19, 2010

Re: Regarding Lag

Tracing route to login.uogamers.com [173.192.237.124]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 91 ms 91 ms 90 ms 173.192.237.124-static.reverse.softlayer.com [17
3.192.237.124]

Trace complete.

is this anything to do with my being stuck at "verifying account" all day?

Mara · Sep 19, 2010

Re: Regarding Lag

This is what has been happening alot during the normal hours M-F 8am-6pm Eastern. Sometimes things are ok, but usually at night, in off-peak hours. Even with a great ping, the packetloss makes the game unsuitable for PVP and PVM.

Pinging login.uogamers.com [173.192.237.124] with 32 bytes of data:

Reply from 173.192.237.124: bytes=32 time=31ms TTL=114
Request timed out.
Reply from 173.192.237.124: bytes=32 time=31ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=41ms TTL=114
Reply from 173.192.237.124: bytes=32 time=30ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Request timed out.
Request timed out.
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=32ms TTL=114
Reply from 173.192.237.124: bytes=32 time=32ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=30ms TTL=114

Ping statistics for 173.192.237.124:
Packets: Sent = 20, Received = 17, Lost = 3 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 41ms, Average = 30ms

Tracing route to login.uogamers.com [173.192.237.124]
over a maximum of 30 hops:

1 14 ms 12 ms 8 ms 68.58.200.1
2 10 ms 12 ms 9 ms te-8-4-ur01.ladson.sc.chrlstn.comcast.net [68.85.123.17]
3 8 ms 9 ms 9 ms te-9-1-ar01.charleston.sc.chrlstn.comcast.net [68.86.144.49]
4 11 ms 14 ms 11 ms pos-1-2-ar01.savannah.ga.savannah.comcast.net [68.86.250.117]
5 16 ms 14 ms 14 ms te-7-4-ar02.augusta.ga.augusta.comcast.net [68.86.164.21]
6 21 ms 19 ms 19 ms pos-0-11-0-0-cr01.charlotte.nc.ibone.comcast.net[68.86.91.237]
7 30 ms 28 ms 28 ms pos-2-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.86.241]
8 29 ms 31 ms 28 ms pos-0-1-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.30]
9 29 ms 28 ms * softlayer-pe01.ashburn.va.ibone.comcast.net [75.149.228.94]
10 28 ms 30 ms 28 ms po1.bbr01.sr01.wdc01.networklayer.com [173.192.18.163]
11 28 ms 28 ms 29 ms po1.cer02.sr01.wdc01.networklayer.com [173.192.18.189]
12 31 ms 30 ms 32 ms po2.fcr02.sr01.wdc01.networklayer.com [208.43.118.151]
13 * * 27 ms 173.192.237.124-static.reverse.softlayer.com [173.192.237.124]

Trace complete.

Brianm360 · Sep 19, 2010

Re: Regarding Lag

Tracing route to login.uogamers.com [173.192.237.124]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 10 ms c-98-214-176-1.hsd1.il.comcast.net [98.214.176.1
]
3 8 ms 11 ms 9 ms ge-1-1-ur01.epeoria.il.chicago.comcast.net [68.8
5.178.121]
4 8 ms 9 ms 9 ms 68.85.176.54
5 15 ms 9 ms 8 ms te-8-1-ur01.pekin.il.chicago.comcast.net [68.85.
177.157]
6 13 ms 13 ms 14 ms te-3-4-ur02.danville.il.chicago.comcast.net [68.
85.177.162]
7 14 ms 13 ms 14 ms te-8-1-ur01.danville.il.chicago.comcast.net [68.
85.177.165]
8 26 ms 25 ms 24 ms te-0-8-0-0-ar01.indianapolis.in.indiana.comcast.
net [68.85.176.18]
9 23 ms 20 ms 21 ms pos-0-14-0-0-ar01.area4.il.chicago.comcast.net [
68.87.231.17]
10 23 ms 23 ms 21 ms pos-1-11-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.95.9]
11 58 ms 58 ms 57 ms pos-2-9-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.86.109]
12 64 ms 64 ms 64 ms pos-0-12-0-0-cr01.ashburn.va.ibone.comcast.net [
68.86.85.29]
13 66 ms 66 ms 64 ms pos-0-2-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.70]
14 89 ms 65 ms 64 ms softlayer-pe01.ashburn.va.ibone.comcast.net [75.
149.228.94]
15 66 ms 67 ms 67 ms po1.bbr01.sr01.wdc01.networklayer.com [173.192.1
8.163]
16 66 ms 66 ms 70 ms po1.cer02.sr01.wdc01.networklayer.com [173.192.1
8.189]
17 67 ms 67 ms 66 ms po2.fcr02.sr01.wdc01.networklayer.com [208.43.11
8.151]
18 122 ms 125 ms 125 ms 173.192.237.124-static.reverse.softlayer.com [17
3.192.237.124]

Trace complete.

C:\Documents and Settings\brian>

Mara · Sep 19, 2010

Re: Regarding Lag

Here's a second run. Sometimes the tracert will show that everything is normal for a given run, but if you run it a few times, you will usually see the problems occuring.

Code:

09/19/2010 – 12:29PM

Pinging login.uogamers.com [173.192.237.124] with 32 bytes of data:

Reply from 173.192.237.124: bytes=32 time=47ms TTL=114
Request timed out.
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Reply from 173.192.237.124: bytes=32 time=30ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Reply from 173.192.237.124: bytes=32 time=32ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Reply from 173.192.237.124: bytes=32 time=44ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=31ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Request timed out.
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=31ms TTL=114
Reply from 173.192.237.124: bytes=32 time=28ms TTL=114
Reply from 173.192.237.124: bytes=32 time=29ms TTL=114

Ping statistics for 173.192.237.124:
    Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 47ms, Average = 30ms

Tracing route to login.uogamers.com [173.192.237.124]
over a maximum of 30 hops:

  1    11 ms     9 ms    23 ms  68.58.200.1
  2    10 ms     9 ms     9 ms  te-8-4-ur01.ladson.sc.chrlstn.comcast.net [68.85.123.17]
  3    10 ms     9 ms     9 ms  te-9-1-ar01.charleston.sc.chrlstn.comcast.net [68.86.144.49]
  4    15 ms    13 ms    11 ms  pos-1-2-ar01.savannah.ga.savannah.comcast.net [68.86.250.117]
  5    13 ms    14 ms    14 ms  te-7-4-ar02.augusta.ga.augusta.comcast.net [68.86.164.21]
  6    21 ms    18 ms    19 ms  pos-0-10-0-0-cr01.charlotte.nc.ibone.comcast.net[68.86.90.189]
  7    29 ms    28 ms    28 ms  pos-2-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.86.241]
  8    31 ms    30 ms    30 ms  pos-0-1-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.30]
  9    27 ms    28 ms    31 ms  softlayer-pe01.ashburn.va.ibone.comcast.net [75.149.228.94]
 10     *       30 ms    28 ms  po1.bbr01.sr01.wdc01.networklayer.com [173.192.18.163]
 11     *       28 ms     *     po1.cer02.sr01.wdc01.networklayer.com [173.192.18.189]
 12    30 ms    30 ms    29 ms  po2.fcr02.sr01.wdc01.networklayer.com [208.43.118.151]
 13    29 ms    28 ms    30 ms  173.192.237.124-static.reverse.softlayer.com [173.192.237.124]

shindig · Sep 19, 2010

Re: Regarding Lag

I don't get it, even if my ping says 105, I freeze for a second every 4-6 tiles when I try to run in a straight line. When I have sallos display ping it goes from 105 to 1510, 500, 240, then back to low 100's....

This has never happened until recently.

EVEN IF IT SAYS IT HAS A GOOD PING IT IS UNPLAYABLE because of the random freezing.........

Mara · Sep 19, 2010

Re: Regarding Lag

Run a ping test from the command prompt shindig and see what you get. You can change the number of iterations by adding the -n command. For example, try...

ping -n 100 login.uogamers.com

And see how much packet loss, if any, you are getting. The ping that you see from razor or sallos should not be used to determine your actual ping to the server, it is a calculation done by the programs to give you an average over a very short period of time (I think). Always use the command prompt info when trying to figure out your actual ping to the server.

shindig · Sep 19, 2010

Re: Regarding Lag

Yep, pretty much what's happening in game:

Mara · Sep 19, 2010

Re: Regarding Lag

Yeah, that's what I thought you might see. I'm having anywhere from 5-15% packet loss during peak hours, and it's making the game unplayable during those times. The tracert doesn't really tell the full story if you get a good run where no problems occur. Looks like the problems are right at or very close to the server.

shindig · Sep 19, 2010

Re: Regarding Lag

Yea yesterday when I ran half a dozen tracert's it was fine until the last 4-5 hops.

If this were a question on the network+ test I'd choose an answer related to the session/transport layer of the OSI model on the server, where we're all looking at the network/datalink/physical layers for problems. There's connectivity, ping works, the addressing works, it's the streaming of packets that's not working as it's dropping 5-10% for me.

WillyDaSquid · Sep 19, 2010

Re: Regarding Lag

shindig;2128454 said:
Yea yesterday when I ran half a dozen tracert's it was fine until the last 4-5 hops.

If this were a question on the network+ test I'd choose an answer related to the session/transport layer of the OSI model on the server, where we're all looking at the network/datalink/physical layers for problems. There's connectivity, ping works, the addressing works, it's the streaming of packets that's not working as it's dropping 5-10% for me.

Your right, its only one side of the story.

Code Blue · Sep 19, 2010

Re: Regarding Lag

Code:

Tracing route to login.uogamers.com [173.192.237.124]
over a maximum of 30 hops:

  1    27 ms     9 ms    10 ms  10.131.0.1
  2    15 ms    11 ms    22 ms  csw01euclwi-gbe-4-6.eucl.wi.charter.com [96.34.2
2.94]
  3    10 ms    11 ms     9 ms  96-34-16-231.static.unas.wi.charter.com [96.34.1
6.231]
  4     9 ms    13 ms    11 ms  crr02euclwi-gbe-6-0-0.eucl.wi.charter.com [96.34
.16.233]
  5    13 ms    11 ms    10 ms  bbr02euclwi-tge-0-0-0-0.eucl.wi.charter.com [96.
34.2.6]
  6    23 ms    19 ms    19 ms  bbr01chcgil-tge-0-0-0-4.chcg.il.charter.com [96.
34.0.9]
  7    17 ms    17 ms    17 ms  prr01chcgil-tge-1-1.chcg.il.charter.com [96.34.3
.9]
  8    18 ms    21 ms    20 ms  96-34-152-14.static.unas.mo.charter.com [96.34.1
52.14]
  9    21 ms    20 ms    19 ms  tex-x.bbr01.eq01.chi01.networklayer.com [66.109.
11.106]
 10    42 ms    40 ms    41 ms  po3.bbr01.eq01.wdc01.networklayer.com [173.192.1
8.154]
 11    42 ms    49 ms    43 ms  po3.bbr01.sr01.wdc01.networklayer.com [173.192.1
8.195]
 12     *       44 ms    41 ms  po1.cer01.sr01.wdc01.networklayer.com [173.192.1
8.187]
 13    45 ms    49 ms    44 ms  po1.fcr02.sr01.wdc01.networklayer.com [208.43.11
8.149]
 14    47 ms    45 ms    41 ms  173.192.237.124-static.reverse.softlayer.com [17
3.192.237.124]

Trace complete.

What a coincedince me and shin dig have the same problem

It must be our ISP that makes 100 mil plus a year in revenue and not the "fix" they made for uog

Mara · Sep 19, 2010

Re: Regarding Lag

I started keeping a record of when the problems and packet loss is occuring to help figure out the problem. It is pretty sporadic, but during times when there is significant packet loss it is very difficult to PVP or PVM without getting a lot of rubber-banding and intermittent drop-outs. Hope this helped a little.

09/19/2010 - 15:43 Eastern Time - No Problems. Tests Sat.
09/19/2010 - 16:15 Eastern Time - Problem reoccuring. 15% packet loss.
09/19/2010 - 18:22 Eastern Time - No Problems. Tests Sat.
09/20/2010 - 01:08 Eastern Time - Problem reoccuring, but to a lesser extent, 3% packet loss.
09/20/2010 - 11:00 Eastern Time - No Problems. Tests Sat.
09/21/2010 - 14:02 Eastern Time - Problem reoccuring. 6% packet loss.
09/21/2010 - 16:10 Eastern Time - Problem reoccuring. 6% packet loss.
09/21/2010 - 17:30 Eastern Time - No Problems. Tests Sat.
09/21/2010 - 23:10 Eastern Time - Problem reoccuring. 6% packet loss.
09/22/2010 - 04:00 Eastern Time - No Problems. Tests Sat.
09/22/2010 - 18:05 Eastern Time - No Problems. Tests Sat.
09/22/2010 - 18:12 Eastern Time - Problem reoccuring, but to a lesser extent, 2% packet loss.
09/23/2010 - 09:20 Eastern Time - No Problems. Tests Sat.
09/23/2010 - 09:57 Eastern Time - Problem reoccuring. 16% packet loss.
09/23/2010 - 14:19 Eastern Time - Problem reoccuring, but to a lesser extent, 4% packet loss.
09/24/2010 - 08:45 Eastern Time - No Problems. Tests Sat.
09/24/2010 - 14:30 Eastern Time - Problem reoccuring. 5% packet loss.
09/25/2010 - 09:47 Eastern Time - Problem reoccuring. 8% packet loss. 791 users online.
09/25/2010 - 14:10 Eastern Time - No Problems. Tests Sat. 829 users online.
09/25/2010 - 15:30 Eastern Time - Problem reoccuring. 8% packet loss.
No longer keeping a record of problems.

co co · Sep 19, 2010

Re: Regarding Lag

No lag on my end at all..

Regarding Lag

Wanderer

Knight

Sorceror

Knight

Knight

Sorceror

Knight

Wanderer

Knight

Sorceror

Knight

Sorceror

Attachments

Knight

Sorceror

Attachments

Knight

Sorceror

Sorceror

Knight

Knight

Page