Threads about lag...

Zippy · Oct 7, 2007

Threads about lag...

Please, do not make anymore threads about lag. If you are having lag problems, post a traceroute in this thread. 9 out of 10 times people's lag problems are a problem with their ISP or with an ISP between them 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.

Here is how to run a traceroute in windows XP:

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 to every post in this thread from me or anyone else on staff. We will read the traces, but we do not have time to respond to everyone individually.

Thank you.

Zippy · Oct 7, 2007

Re: Threads about lag...

As an example, here is my tracert to the server:

Code:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     8 ms     8 ms     8 ms  73.139.192.1
  3     6 ms     6 ms     8 ms  ge-1-22-ur01.elkridge.md.bad.comcast.net [68.87.
132.241]
  4     7 ms     7 ms    15 ms  te-9-3-ur02.howardcounty.md.bad.comcast.net [68.
87.128.254]
  5    10 ms     7 ms     7 ms  te-9-3-ur01.howardcounty.md.bad.comcast.net [68.
87.129.93]
  6     9 ms     7 ms     9 ms  te-9-3-ar01.howardcounty.md.bad.comcast.net [68.
87.129.37]
  7    10 ms     9 ms    11 ms  po-10-ar02.whitemarsh.md.bad.comcast.net [68.87.
129.34]
  8    16 ms     *        *     68.86.85.9
  9     *       13 ms    23 ms  COMCAST-IP.edge1.NewYork2.Level3.net [4.78.169.4
6]
 10    15 ms    79 ms    13 ms  xe-10-1-0.edge1.NewYork2.Level3.net [4.78.169.45
]
 11    24 ms    17 ms    17 ms  vlan99.csw4.NewYork1.Level3.net [4.68.16.254]
 12    18 ms    17 ms    18 ms  ae-94-94.ebr4.NewYork1.Level3.net [4.69.134.125]

 13    18 ms    17 ms    17 ms  ae-3.ebr4.Washington1.Level3.net [4.69.132.93]
 14    15 ms    17 ms    15 ms  ae-94-94.csw4.Washington1.Level3.net [4.69.134.1
90]
 15    16 ms    20 ms    16 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.1
41]
 16    35 ms    35 ms    36 ms  ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
 17    55 ms    53 ms    54 ms  ae-7.ebr2.Dallas1.Level3.net [4.69.134.21]
 18    52 ms    51 ms    51 ms  ae-2-54.edge3.Dallas1.Level3.net [4.68.122.114]

 19    50 ms    49 ms    50 ms  te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
 20    71 ms    62 ms    61 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 21    50 ms    50 ms    48 ms  login.uogamers.com [75.126.37.240]

Trace complete.

See hops 8 and 9? I love you, too, comcast!

Keeblar · Oct 7, 2007

Re: Threads about lag...

Code:

  1     1 ms    <1 ms     1 ms  buffalo.setup [192.168.11.1]
  2     *        *        *     Request timed out.
  3     8 ms     7 ms     9 ms  68.85.251.229
  4    10 ms     9 ms     9 ms  68.85.244.145
  5     9 ms     9 ms     9 ms  68.85.244.149
  6     8 ms     9 ms     9 ms  68.85.244.153
  7    13 ms    11 ms     9 ms  te-3-1.car2.Houston1.Level3.net [4.79.90.93]
  8    23 ms    18 ms    17 ms  ae-5-5.ebr1.Dallas1.Level3.net [4.69.132.230]
  9    15 ms    15 ms    15 ms  ae-1-53.edge3.Dallas1.Level3.net [4.68.122.82]
 10    16 ms    15 ms    15 ms  te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
 11    17 ms    16 ms    15 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 12    20 ms    30 ms    17 ms  login.uogamers.com [75.126.37.240]

xjoewhitex · Oct 7, 2007

Re: Threads about lag...

Code:

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

  1     *        *        *     Request timed out.
  2     3 ms     3 ms     3 ms  192.168.0.1
  3    76 ms    75 ms    87 ms  ppp-69-218-219-254.dsl.wotnoh.ameritech.net [69.
218.219.254]
  4    62 ms    61 ms    60 ms  dist1-vlan50.wotnoh.sbcglobal.net [67.36.13.226]

  5    22 ms    21 ms    20 ms  bb2-g8-0.wotnoh.sbcglobal.net [67.36.13.116]
  6    53 ms    50 ms    44 ms  ex1-p0-0.eqchil.sbcglobal.net [151.164.42.147]
  7   110 ms   126 ms   130 ms  asn22822-llnw.eqchil.sbcglobal.net [151.164.251.
90]
  8   102 ms    88 ms    81 ms  ber1-vlan-241.chicago.savvis.net [204.70.196.21]

  9    46 ms    54 ms    51 ms  dcr2-so-4-3-0.Chicago.savvis.net [208.175.10.237
]
 10    64 ms    64 ms    62 ms  dcr2-so-0-0-0.dallas.savvis.net [204.70.192.98]

 11    78 ms    80 ms    78 ms  dcr1-so-6-0-0.dallas.savvis.net [204.70.192.49]

 12    64 ms     *      970 ms  cr1-pos0-3-3-1.dallas.savvis.net [204.70.194.66]

 13    90 ms    85 ms    85 ms  aer1-ge-5-3.dallasequinix.savvis.net [204.70.194
.30]
 14    61 ms    60 ms    61 ms  ge4-17.cer02.dal01.dallas-border.com [208.175.17
5.58]
 15    96 ms   101 ms    84 ms  po52.fcr01.dal01.dallas-datacenter.com [66.228.1
18.158]
 16    74 ms    74 ms    62 ms  login.uogamers.com [75.126.37.240]

Trace complete.

Mark · Oct 7, 2007

Re: Threads about lag...

Keebler, are you actually having lag issues?

Heavy Smoker · Oct 7, 2007

Re: Threads about lag...

Code:

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

  1   178 ms   183 ms   183 ms  ipt-dtce16.dial.aol.com [205.188.70.144]
  2   174 ms   187 ms   181 ms  iptfarme-dr4-sw0-vlan3.conc.aol.com [205.188.12
.158]
  3   172 ms   167 ms   168 ms  wc1-dtc-ae4.net.aol.com [172.18.30.75]
  4   168 ms   167 ms   175 ms  dar1-dtc-GE1-1-0.net.aol.com [172.18.52.65]
  5   182 ms   183 ms   175 ms  pop1-ash-S0-2-0.atdn.net [66.185.141.65]
  6   174 ms   167 ms   183 ms  Level3.atdn.net [66.185.140.254]
  7   182 ms   175 ms   175 ms  vlan69.csw1.Washington1.Level3.net [4.68.17.62]

  8   183 ms   202 ms   195 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.
41]
  9   199 ms   191 ms   200 ms  ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
 10   222 ms   216 ms   222 ms  ae-7.ebr2.Dallas1.Level3.net [4.69.134.21]
 11   221 ms   206 ms   232 ms  ae-2-54.edge3.Dallas1.Level3.net [4.68.122.114]

 12   208 ms   216 ms   222 ms  te7-2.cer01.dal01.dallas-border.com [4.71.198.1
]
 13   211 ms   208 ms   207 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.
18.150]
 14   205 ms   215 ms   216 ms  login.uogamers.com [75.126.37.240]

Trace complete.

JesseJane · Oct 7, 2007

Re: Threads about lag...

Code:

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

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms    <1 ms    <1 ms  192.168.0.1
  3     9 ms     9 ms     9 ms  ppp-70-251-127-254.dsl.rcsntx.swbell.net [70.251
.127.254]
  4    10 ms     9 ms     9 ms  dist2-vlan130.rcsntx.sbcglobal.net [151.164.162.
131]
  5    10 ms     9 ms     9 ms  151.164.93.190
  6     9 ms     9 ms    10 ms  ex1-p2-1.eqdltx.sbcglobal.net [151.164.92.243]
  7    11 ms    10 ms     9 ms  151.164.249.222
  8    11 ms    11 ms    10 ms  ge4-17.cer02.dal01.dallas-border.com [208.175.17
5.58]
  9   222 ms    30 ms   147 ms  po52.fcr01.dal01.dallas-datacenter.com [66.228.1
18.158]
 10    10 ms    10 ms    10 ms  login.uogamers.com [75.126.37.240]

Trace complete.

Tedward · Oct 7, 2007

Re: Threads about lag...

Code:

  1     8 ms     8 ms     8 ms  katy-adsl-66-170-207-254.consolidated.net [66.17
0.207.254]
  2     7 ms     7 ms     8 ms  katy-adsl-66-170-207-254.consolidated.net [66.17
0.207.254]
  3     8 ms     8 ms     7 ms  10.100.1.125
  4     8 ms     8 ms     8 ms  10.100.1.86
  5    10 ms    10 ms    10 ms  64-129-54-25.static.twtelecom.net [64.129.54.25]
  6    19 ms    15 ms    16 ms  peer-01-so-1-0-0-0.dlfw.twtelecom.net [66.192.24
6.53]
  7    20 ms    17 ms    20 ms  ge-2-0-0.r01.dllstx09.us.bb.verio.net [206.223.1
18.12]
  8    20 ms    18 ms    20 ms  po-2.r03.dllstx09.us.bb.gin.ntt.net [129.250.4.3
8]
  9    32 ms    17 ms    20 ms  te7-1.cer01.dal01.dallas-border.com [157.238.228
.10]
 10    17 ms    20 ms    20 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 11    17 ms    20 ms    16 ms  login.uogamers.com [75.126.37.240]

Ryan · Oct 7, 2007

Re: Threads about lag...

Code:

C:\Users\Ryan McAdams>pathping login.uogamers.com
Tracing route to login.uogamers.com [75.126.37.240]
over a maximum of 30 hops:
  0  vesper [10.0.0.180]
  1  10.0.0.1
  2  10.53.128.1
  3  gig2-1.gsbkoh1-ybr1.cinci.rr.com [24.29.1.165]
  4  srp13-0.mtgmoh1-rtr4.cinci.rr.com [24.29.0.175]
  5  srp1-1.libtoh1-ybr1.cinci.rr.com [24.29.2.101]
  6  son0-0-1.ncntoh1-rtr0.neo.rr.com [65.25.128.233]
  7  gig7-3-0.mtgmoh1-rtr0.columbus.rr.com [24.95.81.209]
  8  te-3-3.car1.Cincinnati1.Level3.net [4.78.216.17]
  9  ae-11-11.car2.Cincinnati1.Level3.net [4.69.132.210]
 10  ae-2-2.ebr2.Atlanta2.Level3.net [4.69.132.214]
 11  ae-78.ebr3.Atlanta2.Level3.net [4.69.134.54]
 12  ae-7.ebr2.Dallas1.Level3.net [4.69.134.21]
 13  ae-2-54.edge3.Dallas1.Level3.net [4.68.122.114]
 14  te7-2.cer01.dal01.dallas-border.com [4.71.198.18]
 15  po51.fcr01.dal01.dallas-datacenter.com [66.228.118.150]
 16  login.uogamers.com [75.126.37.240]
Computing statistics for 400 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           vesper [10.0.0.180]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.0.0.1
                                0/ 100 =  0%   |
  2    7ms     0/ 100 =  0%     0/ 100 =  0%  10.53.128.1
                                0/ 100 =  0%   |
  3    7ms     0/ 100 =  0%     0/ 100 =  0%  gig2-1.gsbkoh1-ybr1.cinci.rr.com [24.29.1.165]
                                0/ 100 =  0%   |
  4    8ms     0/ 100 =  0%     0/ 100 =  0%  srp13-0.mtgmoh1-rtr4.cinci.rr.com[24.29.0.175]
                                0/ 100 =  0%   |
  5    8ms     0/ 100 =  0%     0/ 100 =  0%  srp1-1.libtoh1-ybr1.cinci.rr.com [24.29.2.101]
                                0/ 100 =  0%   |
  6   18ms     0/ 100 =  0%     0/ 100 =  0%  son0-0-1.ncntoh1-rtr0.neo.rr.com [65.25.128.233]
                                0/ 100 =  0%   |
  7   29ms     0/ 100 =  0%     0/ 100 =  0%  gig7-3-0.mtgmoh1-rtr0.columbus.rr.com [24.95.81.209]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%   100/ 100 =100%  te-3-3.car1.Cincinnati1.Level3.net [4.78.216.17]
                                0/ 100 =  0%   |
  9   42ms     0/ 100 =  0%     0/ 100 =  0%  ae-11-11.car2.Cincinnati1.Level3.net [4.69.132.210]
                                0/ 100 =  0%   |
 10   45ms     0/ 100 =  0%     0/ 100 =  0%  ae-2-2.ebr2.Atlanta2.Level3.net [4.69.132.214]
                                0/ 100 =  0%   |
 11   45ms     0/ 100 =  0%     0/ 100 =  0%  ae-78.ebr3.Atlanta2.Level3.net [4.69.134.54]
                                0/ 100 =  0%   |
 12   65ms     0/ 100 =  0%     0/ 100 =  0%  ae-7.ebr2.Dallas1.Level3.net [4.69.134.21]
                                0/ 100 =  0%   |
 13  ---     100/ 100 =100%   100/ 100 =100%  ae-2-54.edge3.Dallas1.Level3.net [4.68.122.114]
                                0/ 100 =  0%   |
 14   67ms     0/ 100 =  0%     0/ 100 =  0%  te7-2.cer01.dal01.dallas-border.com [4.71.198.18]
                                0/ 100 =  0%   |
 15  ---     100/ 100 =100%   100/ 100 =100%  po51.fcr01.dal01.dallas-datacenter.com [66.228.118.150]
                                0/ 100 =  0%   |
 16   62ms     0/ 100 =  0%     0/ 100 =  0%  login.uogamers.com [75.126.37.240]

Trace complete.
C:\Users\Ryan McAdams>

Doomherald · Oct 7, 2007

Re: Threads about lag...

H:\Documents and Settings\Nate>tracert login.uogamers.com

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

1 <1 ms <1 ms <1 ms 192.168.1.2
2 7 ms 7 ms 9 ms 10.213.64.1
3 10 ms 12 ms 11 ms 49.229.95.24.cfl.res.rr.com [24.95.229.49]
4 14 ms 14 ms 13 ms 161.228.95.24.cfl.res.rr.com [24.95.228.161]
5 15 ms 17 ms 14 ms 198.228.95.24.cfl.res.rr.com [24.95.228.198]
6 14 ms 13 ms 14 ms te-3-3.car1.Orlando1.Level3.net [4.79.116.145]
7 14 ms 13 ms 14 ms ae-11-11.car2.Orlando1.Level3.net [4.69.133.74]

8 57 ms 53 ms 53 ms ae-9-9.ebr1.Dallas1.Level3.net [4.69.133.70]
9 48 ms 47 ms 48 ms ae-1-55.edge3.Dallas1.Level3.net [4.68.122.146]

10 250 ms 212 ms 222 ms te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
11 114 ms 231 ms 85 ms po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
12 49 ms 49 ms 48 ms login.uogamers.com [75.126.37.240]

MrBrightside · Oct 7, 2007

Re: Threads about lag...

Code:

  1     *        *        *     Request timed out.
  2     7 ms     *        *     GE-1-3-ur01.everett.wa.seattle.comcast.net [68.8
6.98.185]
  3     *        *       11 ms  te-9-1-ar01.burien.wa.seattle.comcast.net [68.86
.96.177]
  4    12 ms    10 ms    11 ms  te-9-1-ar02.burien.wa.seattle.comcast.net [68.86
.96.170]
  5     9 ms     8 ms     8 ms  te-8-1-ar02.seattle.wa.seattle.comcast.net [68.8
6.96.134]
  6    10 ms    11 ms    13 ms  COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.11
0]
  7    10 ms     9 ms     9 ms  te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
  8    18 ms    15 ms    13 ms  ae-32-54.ebr2.Seattle1.Level3.net [4.68.105.126]

  9    45 ms    38 ms    45 ms  ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
 10    49 ms    36 ms    38 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
 11    52 ms    50 ms    54 ms  ae-2.ebr1.Dallas1.Level3.net [4.69.132.106]
 12    53 ms    53 ms    52 ms  ae-1-53.edge3.Dallas1.Level3.net [4.68.122.82]
 13   148 ms    52 ms    51 ms  te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
 14    51 ms    53 ms    52 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 15    52 ms    57 ms    52 ms  login.uogamers.com [75.126.37.240]

FLICK-hybrid · Oct 7, 2007

Re: Threads about lag...

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Union Go>tracert login.uogamers.com

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

  1     1 ms     1 ms     1 ms  192.168.100.100
  2     1 ms     1 ms     1 ms  192.168.100.1
  3     4 ms     4 ms    32 ms  172.16.45.1
  4   575 ms    70 ms    20 ms  rtr-62-i2.winchester.wireless.ssi-pci.net [65.22
1.64.62]
  5   226 ms   202 ms   296 ms  192.168.99.1
  6   602 ms   368 ms   302 ms  208.195.225.133
  7    17 ms    16 ms    16 ms  10.0.0.30
  8    62 ms    22 ms    37 ms  208.195.225.97
  9    63 ms    79 ms    25 ms  parlorcity-gw.parlorcity.com [206.137.30.1]
 10    48 ms    35 ms    32 ms  202.GigabitEthernet5-1.GW1.IND6.ALTER.NET [157.1
30.102.141]
 11   136 ms    65 ms    36 ms  0.so-1-0-1.XL1.IND6.ALTER.NET [152.63.68.170]
 12    34 ms    37 ms    32 ms  0.ge-5-0-0.XT1.CHI2.ALTER.NET [152.63.0.89]
 13    35 ms    33 ms    29 ms  0.so-6-0-0.BR6.CHI2.ALTER.NET [152.63.71.98]
 14    57 ms    73 ms    38 ms  p16-1-2-3.r20.chcgil09.us.bb.gin.ntt.net [129.25
0.9.25]
 15    41 ms    38 ms    60 ms  ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.9
8]
 16    65 ms    61 ms    66 ms  p64-2-2-0.r21.dllstx09.us.bb.gin.ntt.net [129.25
0.2.22]
 17   102 ms   225 ms   428 ms  po-3.r03.dllstx09.us.bb.gin.ntt.net [129.250.4.1
82]
 18   290 ms   313 ms   314 ms  te7-1.cer01.dal01.dallas-border.com [157.238.228
.10]
 19   513 ms  1047 ms   821 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 20   220 ms    74 ms     *     login.uogamers.com [75.126.37.240]
 21   404 ms   113 ms   795 ms  login.uogamers.com [75.126.37.240]

Trace complete.

C:\Documents and Settings\Union Go>

the net is being shit tonight

but on nights where it is fast as fuck on the net and load up pages in no time i still lagg while playing uo

Quenson · Oct 8, 2007

Re: Threads about lag...

Code:

Tracing route to login.uogamers.com [75.126.37.240]

over a maximum of 30 hops:



  1     *        *        *     Request timed out.

  2     *       16 ms     9 ms  ge-1-42-ur01.mchenry.il.chicago.comcast.net [68.86.115.149] 

  3    10 ms     *        8 ms  te-3-2-ur02.algonquin.il.chicago.comcast.net [68.87.231.237] 

  4     7 ms     *        8 ms  te-8-4-ur01.algonquin.il.chicago.comcast.net [68.87.231.233] 

  5    11 ms    13 ms     9 ms  68.87.230.254 

  6    10 ms    11 ms    11 ms  68.86.90.178 

  7    12 ms    11 ms    11 ms  COMCAST-IP.car2.Chicago1.Level3.net [4.71.182.34] 

  8     *        *       12 ms  te-4-2.car2.Chicago1.Level3.net [4.71.182.33] 

  9    12 ms    16 ms    17 ms  ae-31-53.ebr1.Chicago1.Level3.net [4.68.101.94] 

 10    23 ms    17 ms    18 ms  ae-68.ebr3.Chicago1.Level3.net [4.69.134.58] 

 11    45 ms    36 ms    35 ms  ae-3.ebr2.Denver1.Level3.net [4.69.132.61] 

 12    45 ms    35 ms    36 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 

 13    52 ms    54 ms    55 ms  ae-2.ebr1.Dallas1.Level3.net [4.69.132.106] 

 14    58 ms    52 ms    52 ms  ae-1-51.edge3.Dallas1.Level3.net [4.68.122.18] 

 15    43 ms    45 ms    43 ms  te7-2.cer01.dal01.dallas-border.com [4.71.198.18] 

 16    45 ms    45 ms    74 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.118.150] 

 17    43 ms    42 ms    43 ms  login.uogamers.com [75.126.37.240] 



Trace complete.

By posting this, what is accomplished? I am hoping someone can help me with this issue...but so far no GM has done anything but tell me that either A.) the problem is being resolved or B.) there is no problem. Obviously there is if there has to be a thread dedicated to solving the problem. I'm not trying to be an asshole, I just want to be able to play, and I havent been able to. So hopefully someone here CAN help me. If so, it would be greatly appreciated.

P.S. Everyone, and I mean EVERYONE I play with also has lag issues. I also play on a Europe shard with more hops than this, and I have absolutely ZERO lag. So if I get a response to this telling me to contact my ISP, im going to have to tell you to shove it, because thats not the problem. Or at least explain to me how contacting my ISP can possibly solve the problem (will they even care that I can't play a game, yet every other internet activity has no problems). Also, better yet, could someone explain to me why i'm getting so much lag if it does have to do with how many hops im making.

Thank you.

P.P.S I'm sorry if i'm sounding bitchy. I just want to play!

awbs · Oct 8, 2007

Re: Threads about lag...

By posting this, you are helping providing them with the troubleshooting information they need to determine what is causing the lag.. There is nothing anybody can do about the problem its known what the cause is.

Code:

traceroute to login.uogamers.com (75.126.37.240), 30 hops max, 40 byte packets
 1  vlan250.lon-service6.Melbourne.telstra.net (203.50.2.177)  0.239 ms  0.218 ms  0.241 ms
 2  * * *
 3  Bundle-Pos1.ken-core4.Sydney.telstra.net (203.50.6.21)  15.099 ms  14.642 ms  13.835 ms
 4  Port-Channel1.pad-gw2.Sydney.telstra.net (203.50.6.29)  13.06 ms  13.069 ms  13.106 ms
 5  10GigabitEthernet2-0.sydp-core02.Sydney.reach.com (203.50.13.50)  13.208 ms *  13.251 ms
 6  i-13-0.wil-core02.net.reach.com (202.84.141.109)  172.501 ms  172.616 ms  172.51 ms
 7  i-0-0.paix-core02.net.reach.com (202.84.143.62)  181.488 ms  181.419 ms  181.426 ms
 8  static.net.reach.com (202.84.251.66)  176.039 ms  176.1 ms  176.245 ms
 9  GBLX.peer.paix05.net.reach.com (134.159.62.98)  176.153 ms  176.102 ms  176.162 ms
10  te7-2.cer02.dal01.dallas-border.com (64.215.81.2)  222.689 ms  222.608 ms  222.91 ms
11  po52.fcr01.dal01.dallas-datacenter.com (66.228.118.158)  223.01 ms  222.974 ms  222.873 ms
12  login.uogamers.com (75.126.37.240)  222.761 ms  222.782 ms  222.937 ms

Mashenka · Oct 8, 2007

Re: Threads about lag...

Code:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\>tracert login.uogamers.com

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

  1    11 ms    11 ms    11 ms  10.150.128.1
  2    12 ms    11 ms    11 ms  cdm-66-76-226-17.tyrd.suddenlink.net [66.76.226.17]
  3    15 ms    15 ms    15 ms  cdm-66-76-226-5.tyrd.suddenlink.net [66.76.226.5]
  4    44 ms    45 ms    45 ms  cdm-66-76-168-13.bssr.suddenlink.net [66.76.168.13]
  5    40 ms    41 ms    41 ms  ge-6-19.car3.Washington1.Level3.net [4.79.168.29]
  6    49 ms    53 ms    40 ms  vlan99.csw4.Washington1.Level3.net [4.68.17.254]

  7    45 ms    53 ms    53 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.141]
  8    60 ms    58 ms    67 ms  ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
  9    83 ms    89 ms    89 ms  ae-7.ebr2.Dallas1.Level3.net [4.69.134.21]
 10    84 ms    85 ms    83 ms  ae-2-56.edge3.Dallas1.Level3.net [4.68.122.178]

 11    84 ms    85 ms    85 ms  te7-2.cer01.dal01.dallas-border.com [4.71.198.18]
 12    85 ms    84 ms    85 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.118.150]
 13    88 ms    88 ms    88 ms  login.uogamers.com [75.126.37.240]

Trace complete.

C:\>

i get lag problems when running full speed mounted

noowbie · Oct 8, 2007

Re: Threads about lag...

Code:

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

  1     1 ms     2 ms    <1 ms  xxx
  2    31 ms    16 ms    18 ms xxx
  3    50 ms    11 ms    11 ms  xxx
  4    19 ms    13 ms    22 ms  cnrosysc02-f1-0-3.conrtx.tl.suddenlink.net [208.
180.120.5]
  5    61 ms    28 ms    33 ms  n208-180-120-41.tylrtx.tl.sta.suddenlink.net [20
8.180.120.41]
  6    45 ms    58 ms    29 ms  cdm-66-76-45-205.tyrd.suddenlink.net [66.76.45.2
05]
  7    32 ms    30 ms    31 ms  tyrm-crs02.tylrtx.suddenlink.net [66.76.30.2]
  8     *       50 ms     *     te-7-3.car4.Dallas1.Level3.net [4.71.122.13]
  9    53 ms    37 ms    31 ms  ae-1-55.edge3.Dallas1.Level3.net [4.68.122.146]

 10   227 ms   217 ms    50 ms  te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
 11    42 ms    46 ms    89 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 12    42 ms    43 ms     *     login.uogamers.com [75.126.37.240]
 13    50 ms    40 ms    37 ms  login.uogamers.com [75.126.37.240]

hmm...it looks like many people who replied have "ping problems" here:

te7-2.cer01.dal01.dallas-border.com
po51.fcr01.dal01.dallas-datacenter.com

FLICK-hybrid · Oct 8, 2007

Re: Threads about lag...

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Union Go>tracert login.uogamers.com

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

  1     1 ms     1 ms     1 ms  192.168.100.100
  2     1 ms     1 ms     1 ms  192.168.100.1
  3     3 ms     3 ms     3 ms  172.16.45.1
  4     5 ms     5 ms     6 ms  rtr-62-i2.winchester.wireless.ssi-pci.net [65.22
1.64.62]
  5     7 ms     6 ms     6 ms  192.168.99.1
  6    12 ms     8 ms     8 ms  208.195.225.133
  7    11 ms    11 ms    10 ms  10.0.0.30
  8    14 ms    18 ms    12 ms  208.195.225.97
  9    12 ms    13 ms    12 ms  parlorcity-gw.parlorcity.com [206.137.30.1]
 10    24 ms    21 ms    23 ms  202.GigabitEthernet5-1.GW1.IND6.ALTER.NET [157.1
30.102.141]
 11    20 ms    22 ms    39 ms  0.so-1-0-1.XL1.IND6.ALTER.NET [152.63.68.170]
 12    27 ms    28 ms    36 ms  0.ge-5-0-0.XT1.CHI2.ALTER.NET [152.63.0.89]
 13    26 ms    30 ms    28 ms  0.so-6-0-0.BR6.CHI2.ALTER.NET [152.63.71.98]
 14    28 ms    27 ms    32 ms  p16-1-2-3.r20.chcgil09.us.bb.gin.ntt.net [129.25
0.9.25]
 15    29 ms    27 ms    30 ms  ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.9
8]
 16    51 ms    58 ms    57 ms  p64-2-2-0.r21.dllstx09.us.bb.gin.ntt.net [129.25
0.2.22]
 17    51 ms    50 ms    53 ms  po-3.r03.dllstx09.us.bb.gin.ntt.net [129.250.4.1
82]
 18    52 ms    52 ms    51 ms  te7-1.cer01.dal01.dallas-border.com [157.238.228
.10]
 19    80 ms    59 ms    54 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 20    52 ms    57 ms    49 ms  login.uogamers.com [75.126.37.240]

Trace complete.

C:\Documents and Settings\Union Go>

posted another cause my net isnt being gay

Milisani · Oct 8, 2007

Re: Threads about lag...

Code:

C:\Documents and Settings\Kerry>tracert login.uogamers.com

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

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     9 ms     9 ms    11 ms  10.125.152.1
  3    15 ms     9 ms    21 ms  62-31-64-41.cable.ubr06.brad.blueyonder.co.uk [6
2.31.64.41]
  4    22 ms    25 ms    23 ms  pc-62-30-251-18-ro.blueyonder.co.uk [62.30.251.1
8]
  5   172 ms   203 ms   211 ms  194.117.136.209
  6    29 ms    24 ms    31 ms  194.117.136.178
  7    26 ms    32 ms    33 ms  tele1-know-rab.telewest.net [194.117.136.158]
  8    34 ms    23 ms    23 ms  194.117.136.146
  9    69 ms    62 ms    61 ms  ge3-0.pr1.lhr1.uk.above.net [195.66.224.76]
 10   146 ms   147 ms   146 ms  so-4-0-0.cr1.dca2.us.above.net [64.125.27.57]
 11   153 ms   144 ms   152 ms  so-1-0-0.mpr2.atl6.us.above.net [64.125.28.230]

 12   231 ms   204 ms   204 ms  so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
 13   167 ms   151 ms   140 ms  so-1-2-1.mpr4.iah1.us.above.net [64.125.29.62]
 14   164 ms   175 ms   187 ms  so-0-0-0.mpr3.iah1.us.above.net [64.125.26.13]
 15   179 ms   186 ms   170 ms  so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

 16   134 ms   132 ms   131 ms  ge4-13.cer01.dal01.dallas-border.com [64.124.79.
202]
 17   163 ms   153 ms   133 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 18   247 ms   203 ms   204 ms  login.uogamers.com [75.126.37.240]

Trace complete.

Neppg · Oct 8, 2007

Re: Threads about lag...

Code:

  1     7 ms     6 ms     7 ms  a91-152-224-1.elisa-laajakaista.fi [91.152.224.1
]
  2     7 ms     6 ms     7 ms  a91-152-224-1.elisa-laajakaista.fi [91.152.224.1
]
  3     6 ms     6 ms     7 ms  139.97.11.218
  4     8 ms     8 ms     9 ms  ae1.heltli-gw1.fi.elisa.net [139.97.6.238]
  5     *        8 ms     8 ms  ae1-10.bbr2.hel1.fi.eunetip.net [213.192.191.49]

  6     *       15 ms    15 ms  as0-0.bbr1.sto1.se.eunetip.net [213.192.191.210]

  7    47 ms    47 ms    47 ms  so1-0-0-0.bbr1.ams1.nl.eunetip.net [213.192.191.
226]
  8    54 ms    54 ms    54 ms  so0-0-0-0.bbr1.ldn1.uk.eunetip.net [213.192.191.
178]
  9    56 ms    56 ms    56 ms  ge3-0.pr1.lhr1.uk.above.net [195.66.224.76]
 10   128 ms   128 ms   128 ms  so-4-0-0.cr1.dca2.us.above.net [64.125.27.57]
 11   136 ms   136 ms   136 ms  so-1-0-0.mpr2.atl6.us.above.net [64.125.28.230]

 12   141 ms   142 ms   141 ms  so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
 13   150 ms   150 ms   150 ms  so-1-2-1.mpr4.iah1.us.above.net [64.125.29.62]
 14   154 ms   154 ms   155 ms  so-0-0-0.mpr3.iah1.us.above.net [64.125.26.13]
 15   155 ms   155 ms   155 ms  so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

 16   151 ms   151 ms   151 ms  ge4-13.cer01.dal01.dallas-border.com [64.124.79.
202]
 17   150 ms   151 ms   151 ms  po51.fcr01.dal01.dallas-datacenter.com [66.228.1
18.150]
 18   151 ms   150 ms   151 ms  login.uogamers.com [75.126.37.240]

Ryan · Oct 8, 2007

Re: Threads about lag...

Quenson;1562862 said:
By posting this, what is accomplished? I am hoping someone can help me with this issue...but so far no GM has done anything but tell me that either A.) the problem is being resolved or B.) there is no problem. Obviously there is if there has to be a thread dedicated to solving the problem. I'm not trying to be an asshole, I just want to be able to play, and I havent been able to. So hopefully someone here CAN help me. If so, it would be greatly appreciated.

P.S. Everyone, and I mean EVERYONE I play with also has lag issues. I also play on a Europe shard with more hops than this, and I have absolutely ZERO lag. So if I get a response to this telling me to contact my ISP, im going to have to tell you to shove it, because thats not the problem. Or at least explain to me how contacting my ISP can possibly solve the problem (will they even care that I can't play a game, yet every other internet activity has no problems). Also, better yet, could someone explain to me why i'm getting so much lag if it does have to do with how many hops im making.

Thank you.

P.P.S I'm sorry if i'm sounding bitchy. I just want to play!

Apologizing in advance is in poor taste. You're post is out of line and you need to rethink future posts of this nature. Our Game Masters are not able to discern if there's a network issue unless its impacting them. Not everyone is having latency issues it's apparently limited to a couple of different routes.

If we post here asking you to provide diagnostic information such as a traceroute it means we are aware of the issue and are looking for information to possibly alleviate this issue. We do not control every aspect of the network unfortunately.

We are actively working on this... we're not just sitting on our asses with our thumb in our mouth wondering what to do. No one is telling you to contact your ISP.... and if we did we'd tell you why you should contact them. The bottom line is that the route between your network and ours is out of our control but the problems we are seeing are in our network and we are trying to fix them.

The best thing you can do is be patient... we always resolve these kinds of issues.

Thanks,
Ryan

Threads about lag...

Razor Creator

Razor Creator

Sorceror

Wanderer

Knight

Knight

Lord

Wanderer

UOGamers Founder

Sorceror

Knight

Knight

Wanderer

Knight

Wanderer

Wanderer

Knight

Wanderer

Sorceror

UOGamers Founder