Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Information Request: Network Latency Issues

STAR WARS: The Old Republic > English > Customer Service
Information Request: Network Latency Issues
First BioWare Post First BioWare Post

JamesBaldwin's Avatar


JamesBaldwin
01.26.2012 , 10:01 PM | #21 Click here to go to the next staff post in this thread. Next  
Quote: Originally Posted by Ruio View Post
I keep spiking ever since the maintenance in the late afternoon...

I'll post a tracert ina few, but I practically can't play the game anymore.
Please keep in mind that the in game latency meter is not a measure of network latency but a measure of game latency. This latency check measures many things from the client to server and is processed by the server code itself not by the network stack on the server.

While high network latency can negatively impact your play experience, a high in game latency measure is not necessarily indicative of a network issue.

Goodspeed's Avatar


Goodspeed
01.26.2012 , 10:45 PM | #22
Code:
Tracing route to 159.153.92.28 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ***
  2     *        *        *     Request timed out.
  3    11 ms    10 ms    25 ms  ***
  4    17 ms    15 ms    15 ms  ***
  5    36 ms    20 ms    21 ms  pos-1-14-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.85]
  6    17 ms    23 ms    16 ms  be-11-pe03.seattle.wa.ibone.comcast.net [68.86.84.78]
  7    21 ms    17 ms    18 ms  173-167-56-202-static.hfc.comcastbusiness.net [173.167.56.202]
  8    46 ms    16 ms    19 ms  xe-1-0-0.mpr2.sea1.us.above.net [64.125.31.14]
  9    70 ms    69 ms    85 ms  xe-1-2-0.cr2.ord2.us.above.net [64.125.31.2]
 10    92 ms    93 ms    92 ms  xe-2-0-0.cr2.lga5.us.above.net [64.125.24.29]
 11   110 ms    95 ms    97 ms  xe-2-2-0.cr2.dca2.us.above.net [64.125.26.105]
 12    97 ms   105 ms    98 ms  xe-0-0-0.cr1.dca2.us.above.net [64.125.28.241]
 13    97 ms   128 ms   122 ms  xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]
 14    98 ms    99 ms    99 ms  64.125.199.186.t00673-01.above.net [64.125.199.186]
 15    96 ms   102 ms    96 ms  159.153.92.28

Trace complete.

Svache's Avatar


Svache
01.27.2012 , 02:33 AM | #23
Odd.. for days I seemed to have serious problems, and now I am playing and seem to have less problems. Anyways, since I did have it for days, here's my trace route:


Code:
Time of day: 10.30 PM HST (12.30 AM PST/02.30 AM CST)

Tracing route to 159.153.68.252 over a maximum of 30 hops

  1     2 ms     2 ms     1 ms  ***.***.***.***
  2     3 ms     2 ms     2 ms  ***.***.***.***
  3    28 ms    31 ms    28 ms  cpe-***-***-***-***.hawaii.res.rr.com ***.***.***.***

  4    16 ms    14 ms    31 ms  ge0-0-0-10-oahuhimili-rtr2.hawaii.rr.com [24.25.
225.113]
  5    65 ms    66 ms    70 ms  cpe-24-25-225-238.hawaii.rr.com [24.25.225.238]

  6    71 ms    92 ms    72 ms  be6-tustca1-rtr1.socal.rr.com [66.75.161.50]
  7    67 ms    91 ms    85 ms  ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
  8    78 ms    82 ms   112 ms  66.109.9.26
  9    88 ms    73 ms    70 ms  xe-3-2-0.mpr1.lax12.us.above.net [64.125.13.45]

 10    68 ms   132 ms    74 ms  xe-2-3-0.cr1.lax112.us.above.net [64.125.31.190]

 11    91 ms    76 ms    84 ms  xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]
 12   110 ms    98 ms   143 ms  xe-1-1-0.er1.sjc2.us.above.net [64.125.26.198]
 13    92 ms    94 ms    95 ms  209.66.92.106.t00673-04.above.net [209.66.92.106
]
 14    75 ms    82 ms    76 ms  159.153.68.252

Trace complete.
I will do another trace route when I see a huge lag spike again.



edit: Just had a lag spike that resulted in a message that the connection to the server had been lost, and ran a trace route immediately after:

Code:
Time of day: 11.10 PM HST (01.10 AM PST/03.10 AM CST)

Tracing route to 159.153.68.252 over a maximum of 30 hops

  1     1 ms     1 ms     2 ms  ***.***.***.***
  2     3 ms     3 ms     3 ms  ***.***.***.***
  3    77 ms    26 ms    59 ms  cpe-***-***-***-***.hawaii.res.rr.com ***.***.***.***

  4    30 ms    15 ms    15 ms  ge0-0-0-10-oahuhimili-rtr2.hawaii.rr.com [24.25.
225.113]
  5    67 ms    67 ms    66 ms  cpe-24-25-225-238.hawaii.rr.com [24.25.225.238]

  6    97 ms    72 ms    73 ms  be6-tustca1-rtr1.socal.rr.com [66.75.161.50]
  7    69 ms    84 ms   112 ms  ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    77 ms     *       96 ms  ae-3-0.cr0.sjc10.tbone.rr.com [66.109.6.6]
 11     *        *      116 ms  ae-0-0.pr0.sjc10.tbone.rr.com [66.109.6.141]
 12    85 ms   114 ms    76 ms  ae-1-0.cr0.sjc10.tbone.rr.com [66.109.6.140]
 13   174 ms   127 ms   140 ms  ae-2-0.cr0.chi10.tbone.rr.com [66.109.6.15]
 14   137 ms   140 ms   209 ms  xe-1-0-0.cr1.lax112.us.above.net [64.125.30.237]

 15   148 ms   146 ms   156 ms  xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]
 16   191 ms   151 ms   177 ms  xe-4-3-0.er1.sjc2.us.above.net [64.125.28.53]
 17   162 ms   146 ms   147 ms  209.66.92.106.t00673-04.above.net [209.66.92.106
]
 18   145 ms   147 ms   147 ms  159.153.68.252

Trace complete.

Edit2: I logged back into the game and the latency seems to stay a bit higher now (around 500ms), although that is nothing compared to what I've seen the past days, so here's another trace route:

Quote:
Time of day: 11.20 PM HST (01.20 AM PST/03.20 AM CST)

Tracing route to 159.153.68.252 over a maximum of 30 hops

1 1 ms 1 ms 1 ms ***.***.***.***
2 3 ms 2 ms 2 ms ***.***.***.***
3 26 ms 29 ms 49 ms cpe-***-***-***-***.hawaii.res.rr.com ***.***.***.***

4 15 ms 16 ms 15 ms ge0-0-0-10-oahuhimili-rtr2.hawaii.rr.com [24.25.
225.113]
5 65 ms 85 ms 64 ms cpe-24-25-225-238.hawaii.rr.com [24.25.225.238]

6 95 ms 71 ms 72 ms be6-tustca1-rtr1.socal.rr.com [66.75.161.50]
7 67 ms 81 ms 67 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
8 100 ms 114 ms 137 ms ae-7-0.cr0.dfw10.tbone.rr.com [66.109.6.1]
9 100 ms 115 ms 117 ms ae-0-0.ar0.dfw10.tbone.rr.com [66.109.9.105]
10 100 ms 102 ms 134 ms 66.109.11.22
11 121 ms 104 ms 134 ms xe-1-1-0.cr2.dfw2.us.above.net [64.125.26.213]
12 126 ms 106 ms 138 ms xe-4-2-0.cr2.iah1.us.above.net [64.125.31.122]
13 137 ms 137 ms 137 ms xe-2-0-0.cr2.lax112.us.above.net [64.125.25.18]

14 138 ms 137 ms 141 ms xe-1-0-0.cr1.lax112.us.above.net [64.125.30.237]

15 162 ms 146 ms 153 ms xe-0-2-0.cr1.sjc2.us.above.net [64.125.26.26]
16 162 ms 146 ms 172 ms xe-4-3-0.er1.sjc2.us.above.net [64.125.28.53]
17 152 ms 154 ms 148 ms 209.66.92.106.t00673-04.above.net [209.66.92.106
]
18 192 ms 158 ms 190 ms 159.153.68.252

Trace complete.

CROSSBONES

A Dutchie in the middle of the Pacific..

Myli-EU's Avatar


Myli-EU
01.27.2012 , 05:15 AM | #24
Hi James,

Lag is at any time of the day, I connect for about 20 seconds and the problems start...
this is at 10:10 GMT.


Tracing route to 159.153.72.252 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms MyRouter.Home
2 23 ms 21 ms 23 ms 027abe7e.bb.sky.com [2.122.190.126]
3 22 ms 22 ms 22 ms 10.245.185.193
4 28 ms 27 ms 28 ms te0-6-0-2.er10.thlon.ov.easynet.net [89.200.134.
213]
5 24 ms 24 ms 26 ms ldn-b5-link.telia.net [80.239.193.109]
6 24 ms 24 ms 24 ms ldn-bb1-link.telia.net [80.91.246.144]
7 34 ms 35 ms 34 ms dln-b3-link.telia.net [80.91.249.134]
8 35 ms 50 ms 34 ms bioware-ic-147166-dln-b3.c.telia.net [80.239.192
.78]
9 35 ms 39 ms 35 ms 159.153.72.42
10 35 ms 34 ms 34 ms 159.153.72.252

Trace complete.

C:\Users\user>

I witnessed dcs and up to 80k ms just now.
Ryka - Mercenary Healer
Officer of <P R I M E> Part of the Prime Gaming Community
Hydian Way
''If it bleeds, we can kill it''

Lyloron's Avatar


Lyloron
01.27.2012 , 06:02 AM | #25
Timezone: AST (Atlantic Standard Time)
Time of Day: 7:55am AST

Since the most recent patch (which could just be a coincidence) my latency is double what is was prior.

Tracing route to 159.153.92.28 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms ******
2 41 ms 25 ms 19 ms ******
3 12 ms 12 ms 12 ms blk-222-226-89.eastlink.ca [24.222.226.89]
4 31 ms 24 ms 25 ms ns-hlfx-dr002.ns.eastlink.ca [24.215.102.217]
5 22 ms 28 ms 24 ms ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 70 ms 47 ms 53 ms xe-0-3-0.mtl10.ip4.tinet.net [77.67.70.77]
7 118 ms 121 ms 121 ms xe-10-0-1.sjc10.ip4.tinet.net [89.149.180.213]
8 125 ms 123 ms 120 ms TenGigE0-3-4-0.GW3.SJC7.ALTER.NET [152.179.48.17
]
9 125 ms 125 ms 120 ms 0.xe-4-0-1.XL4.SJC7.ALTER.NET [152.63.50.101]
10 136 ms 134 ms 134 ms 0.xe-7-0-3.XT2.DCA5.ALTER.NET [152.63.0.21]
11 135 ms 133 ms 135 ms TenGigE0-7-0-0.GW5.DCA5.ALTER.NET [152.63.37.114
]
12 123 ms 128 ms 127 ms dft-gw.customer.alter.net [152.179.164.162]
13 125 ms 129 ms 127 ms 159.153.92.28

Trace complete.

Mihoshi's Avatar


Mihoshi
01.27.2012 , 06:15 AM | #26
Ok, here my result. Don't mind the long ping times, currently playing from Asia.

On EU servers.
Lag spikes during the whole day but most I get at 7-12 pm CET primetime.

9 184 ms 194 ms 204 ms 138.171.208.203.in-addr.arpa.noptr.antlabs.com [203.208.171.138]
10 180 ms 179 ms 180 ms 226.171.208.203.in-addr.arpa.noptr.antlabs.com [203.208.171.226]
11 188 ms 179 ms 179 ms cw.com.any2ix.coresite.com [206.223.143.96]
12 267 ms 270 ms 267 ms xe-1-1-0-xcr1.ash.cw.net [195.2.28.49]
13 290 ms 276 ms 279 ms xe-5-1-0-xcr1.nyk.cw.net [195.2.21.137]
14 266 ms 256 ms 255 ms xe-3-1-0-xcr1.lnd.cw.net [195.2.25.198]
15 * 270 ms 269 ms xe-0-0-0-xcr1.duc.cw.net [195.2.21.242]
16 291 ms 271 ms 283 ms bioware-gw2.duc.cw.net [195.2.27.90]
17 * 270 ms 274 ms 46.72.153.159.in-addr.arpa.noptr.antlabs.com [159.153.72.46]
18 267 ms 267 ms 267 ms 8.73.153.159.in-addr.arpa.noptr.antlabs.com [159.153.73.8]


9 183 ms 183 ms 183 ms 138.171.208.203.in-addr.arpa.noptr.antlabs.com [203.208.171.138]
10 181 ms 180 ms 180 ms 226.171.208.203.in-addr.arpa.noptr.antlabs.com [203.208.171.226]
11 178 ms 178 ms 194 ms cw.com.any2ix.coresite.com [206.223.143.96]
12 274 ms 267 ms 267 ms xe-1-1-0-xcr1.ash.cw.net [195.2.28.49]
13 298 ms 279 ms 314 ms xe-5-1-0-xcr1.nyk.cw.net [195.2.21.137]
14 256 ms 259 ms 258 ms xe-3-1-0-xcr1.lnd.cw.net [195.2.25.198]
15 276 ms 355 ms 296 ms xe-0-0-0-xcr1.duc.cw.net [195.2.21.242]
16 268 ms * 267 ms bioware-gw2.duc.cw.net [195.2.27.90]
17 271 ms 271 ms 280 ms 46.72.153.159.in-addr.arpa.noptr.antlabs.com [159.153.72.46]
18 267 ms 267 ms 267 ms 8.73.153.159.in-addr.arpa.noptr.antlabs.com [159.153.73.8]

9 183 ms 187 ms 186 ms 138.171.208.203.in-addr.arpa.noptr.antlabs.com [203.208.171.138]
10 181 ms 180 ms 179 ms xe-0-1-0-0.laxow-dr3.ix.singtel.com [203.208.149.117]
11 179 ms 194 ms 203 ms cw.com.any2ix.coresite.com [206.223.143.96]
12 267 ms 267 ms 279 ms xe-1-1-0-xcr1.ash.cw.net [195.2.28.49]
13 277 ms 284 ms 278 ms xe-5-1-0-xcr1.nyk.cw.net [195.2.21.137]
14 284 ms 257 ms 352 ms xe-3-1-0-xcr1.lnd.cw.net [195.2.25.198]
15 275 ms 269 ms * xe-0-0-0-xcr1.duc.cw.net [195.2.21.242]
16 268 ms 267 ms 267 ms bioware-gw2.duc.cw.net [195.2.27.90]
17 270 ms 303 ms 272 ms 46.72.153.159.in-addr.arpa.noptr.antlabs.com [159.153.72.46]
18 267 ms 267 ms 267 ms 8.73.153.159.in-addr.arpa.noptr.antlabs.com [159.153.73.8]

MadWik's Avatar


MadWik
01.27.2012 , 07:05 AM | #27
The latency and disconnects seem to happen for me most often when I'm on my ship (XS Freighter), either walking around or doing space missions.

I have not had a disconnect problem until this week's patch. Now at times my latency will spike from 46ms to 8000ms, keeps rising and disconnect.

Here are my tracert logs from this morning.

Just logged in. Everything normal.
1/27/2012 7:28AM EST
Code:
Tracing route to 159.153.92.28 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ***** [*****] 
  2     7 ms     *        *     ***** 
  3     *        *        7 ms  acr01ssvlsc-gbe-4-9.ssvl.sc.charter.com [96.34.66.12] 
  4     7 ms     7 ms     8 ms  acr02spbgsc-tge-2-4.spbg.sc.charter.com [96.34.64.16] 
  5     9 ms     9 ms     9 ms  crr02spbgsc-tge-0-3-0-0.spbg.sc.charter.com [96.34.64.53] 
  6     8 ms     *        *     crr01spbgsc-tge-0-4-0-7.spbg.sc.charter.com [96.34.64.138] 
  7    12 ms     *       11 ms  bbr01spbgsc-tge-0-2-0-0.spbg.sc.charter.com [96.34.2.244] 
  8    16 ms    22 ms    16 ms  cha-b1-link.telia.net [80.239.196.117] 
  9    15 ms    15 ms     *     atl-bb1-link.telia.net [80.91.245.206] 
 10    27 ms    58 ms    26 ms  ge-10-0-4.mpr3.atl6.us.above.net [64.125.12.97] 
 11    28 ms    52 ms    26 ms  xe-0-0-0.mpr4.atl6.us.above.net [64.125.31.42] 
 12    28 ms    27 ms    27 ms  xe-2-3-0.cr1.dca2.us.above.net [64.125.31.54] 
 13    26 ms    27 ms    25 ms  xe-1-0-1.er1.iad10.us.above.net [64.125.26.238] 
 14    27 ms    27 ms    27 ms  64.125.199.186.t00673-01.above.net [64.125.199.186] 
 15    29 ms    27 ms    27 ms  159.153.92.28 

Trace complete.
-----
Completed "Kalee" Space Mission (I often DC right at the end)
1/27/2012 7:37AM EST

Code:
Tracing route to 159.153.92.28 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ***** [*****] 
  2     *        6 ms     7 ms  *****  
  3    11 ms     7 ms     7 ms  acr01ssvlsc-gbe-4-9.ssvl.sc.charter.com [96.34.66.12] 
  4    10 ms     7 ms     8 ms  acr02spbgsc-tge-2-4.spbg.sc.charter.com [96.34.64.16] 
  5     7 ms     9 ms     9 ms  crr02spbgsc-tge-0-3-0-0.spbg.sc.charter.com [96.34.64.53] 
  6     9 ms     7 ms     8 ms  crr01spbgsc-tge-0-4-0-7.spbg.sc.charter.com [96.34.64.138] 
  7    10 ms    11 ms    11 ms  bbr01spbgsc-tge-0-2-0-0.spbg.sc.charter.com [96.34.2.244] 
  8    16 ms    26 ms    16 ms  cha-b1-link.telia.net [80.239.196.117] 
  9    16 ms    15 ms    15 ms  atl-bb1-link.telia.net [80.91.245.206] 
 10    27 ms    29 ms    27 ms  ge-10-0-4.mpr3.atl6.us.above.net [64.125.12.97] 
 11    27 ms    28 ms    29 ms  xe-0-0-0.mpr4.atl6.us.above.net [64.125.31.42] 
 12    42 ms    31 ms    27 ms  xe-2-3-0.cr1.dca2.us.above.net [64.125.31.54] 
 13    28 ms    26 ms    25 ms  xe-1-0-1.er1.iad10.us.above.net [64.125.26.238] 
 14    27 ms    27 ms    27 ms  64.125.199.186.t00673-01.above.net [64.125.199.186] 
 15    29 ms    30 ms    32 ms  159.153.92.28 

Trace complete.
-----
Just as the Kalee mission closed, I got the disconnect.
9000 ERRORCODE
1/27/2012 7:39AM EST
Code:
Tracing route to 159.153.92.28 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ***** [*****] 
  2     6 ms     9 ms     *     ***** 
  3     7 ms     7 ms     8 ms  acr01ssvlsc-gbe-4-9.ssvl.sc.charter.com [96.34.66.12] 
  4     8 ms     7 ms     9 ms  acr02spbgsc-tge-2-4.spbg.sc.charter.com [96.34.64.16] 
  5    14 ms    13 ms     9 ms  crr02spbgsc-tge-0-3-0-0.spbg.sc.charter.com [96.34.64.53] 
  6    11 ms     8 ms     8 ms  crr01spbgsc-tge-0-4-0-7.spbg.sc.charter.com [96.34.64.138] 
  7     8 ms    11 ms    11 ms  bbr01spbgsc-tge-0-2-0-0.spbg.sc.charter.com [96.34.2.244] 
  8    18 ms    17 ms    15 ms  cha-b1-link.telia.net [80.239.196.117] 
  9    16 ms    15 ms    15 ms  atl-bb1-link.telia.net [213.155.134.202] 
 10    28 ms    26 ms    27 ms  ge-10-0-4.mpr3.atl6.us.above.net [64.125.12.97] 
 11    33 ms    29 ms    27 ms  xe-0-0-0.mpr4.atl6.us.above.net [64.125.31.42] 
 12    26 ms    28 ms    32 ms  xe-2-3-0.cr1.dca2.us.above.net [64.125.31.54] 
 13    27 ms    27 ms    27 ms  xe-1-0-1.er1.iad10.us.above.net [64.125.26.238] 
 14    26 ms    27 ms    28 ms  64.125.199.186.t00673-01.above.net [64.125.199.186] 
 15    27 ms    26 ms    30 ms  159.153.92.28 

Trace complete.
-----

I logged in again and tried the "Drexel" space mission. My latency was bouncing, but it looked like it was recovering. Then it Disconnected.
9000 ERRORCODE
1/27/2012 7:49AM EST

Code:
Tracing route to 159.153.92.28 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ***** [*****] 
  2     6 ms     6 ms     *     *****  
  3     8 ms    15 ms     8 ms  acr01ssvlsc-gbe-4-9.ssvl.sc.charter.com [96.34.66.12] 
  4    18 ms     8 ms    11 ms  acr02spbgsc-tge-2-4.spbg.sc.charter.com [96.34.64.16] 
  5     8 ms     7 ms     8 ms  crr02spbgsc-tge-0-3-0-0.spbg.sc.charter.com [96.34.64.53] 
  6     8 ms     8 ms     7 ms  crr01spbgsc-tge-0-4-0-7.spbg.sc.charter.com [96.34.64.138] 
  7    11 ms    11 ms    11 ms  bbr01spbgsc-tge-0-2-0-0.spbg.sc.charter.com [96.34.2.244] 
  8    20 ms    16 ms    15 ms  cha-b1-link.telia.net [80.239.196.117] 
  9    17 ms    16 ms    35 ms  atl-bb1-link.telia.net [213.155.134.202] 
 10    27 ms    27 ms    28 ms  ge-10-0-4.mpr3.atl6.us.above.net [64.125.12.97] 
 11    27 ms    27 ms    27 ms  xe-0-0-0.mpr4.atl6.us.above.net [64.125.31.42] 
 12    26 ms    30 ms    27 ms  xe-2-3-0.cr1.dca2.us.above.net [64.125.31.54] 
 13    27 ms    27 ms    27 ms  xe-1-0-1.er1.iad10.us.above.net [64.125.26.238] 
 14    26 ms    27 ms     *     64.125.199.186.t00673-01.above.net [64.125.199.186] 
 15    28 ms    27 ms    28 ms  159.153.92.28 

Trace complete.

Quijar's Avatar


Quijar
01.27.2012 , 08:27 AM | #28
Tracert from Spain at 15:22 (GMT+1)

Code:
Traza a 159.153.72.252 sobre caminos de 30 saltos como máximo.

  1     7 ms     6 ms     6 ms  S************N [0.0.0.0]
  2     8 ms     7 ms     6 ms  10.105.240.65
  3    11 ms    11 ms    14 ms  10.105.240.17
  4    12 ms    11 ms    11 ms  10.254.7.57
  5    12 ms    11 ms    13 ms  10.254.3.118
  6    14 ms    21 ms    13 ms  mad-b1-link.telia.net [213.248.90.85]
  7    40 ms    39 ms    40 ms  prs-bb1-link.telia.net [80.91.245.58]
  8    47 ms    57 ms    50 ms  ldn-bb1-link.telia.net [213.155.134.39]
  9    57 ms    57 ms    62 ms  dln-b3-link.telia.net [80.91.249.134]
 10    62 ms    61 ms    61 ms  bioware-ic-147166-dln-b3.c.telia.net [80.239.192.78]
 11    58 ms    59 ms    62 ms  159.153.72.42
 12    58 ms    65 ms    58 ms  159.153.72.252

Traza completa.
from server:

Code:
traceroute to 159.153.72.252 (159.153.72.252), 30 hops max, 40 byte packets
 1  rbx-49-m1.fr.eu (91.121.158.253)  221.857 ms  221.882 ms  222.000 ms
 2  rbx-1-6k.fr.eu (91.121.130.1)  0.499 ms * *
 3  rbx-g1-a9.fr.eu (94.23.122.106)  1.359 ms  1.731 ms  1.919 ms
 4  gsw-2-6k.fr.eu (213.251.128.106)  12.852 ms * *
 5  gblx.as3549.fr.eu (213.186.32.249)  4.006 ms  4.043 ms  4.086 ms
 6  208.178.58.58 (208.178.58.58)  4.024 ms  4.076 ms  4.007 ms
 7  prs-bb1-link.telia.net (80.91.247.50)  48.260 ms  48.100 ms  45.886 ms
 8  ldn-bb1-link.telia.net (80.91.247.35)  12.683 ms  12.698 ms  12.688 ms
 9  dln-b3-link.telia.net (80.91.249.134)  22.900 ms  22.927 ms  22.942 ms
10  bioware-ic-147167-dln-b3.c.telia.net (80.239.192.82)  23.338 ms  23.476 ms  23.541 ms
11  159.153.72.252 (159.153.72.252)  23.232 ms  23.104 ms  23.221 ms
Hispania Republic & Hispania Empire
The Red Eclipse | Comunidad HISPANIA

BoneEater's Avatar


BoneEater
01.27.2012 , 09:34 AM | #29
Okay, me again. I was finally able to get the traceroute output while experiencing the problem.

So, for comparison, this is how it looked like when I could play the game with no issue at all.

Server: Sith Triumverate, EU
Time: 4 pm, CET

Code:
Routenverfolgung zu 159.153.72.252 über maximal 30 Abschnitte

  1     1 ms     1 ms     1 ms  ***
  2     *        *        *     Zeitüberschreitung der Anforderung.
  3     9 ms     9 ms    10 ms  172.30.17.61
  4    12 ms    16 ms    13 ms  HSI-KBW-078-042-040-045.hsi3.kabel-badenwuerttem
berg.de [78.42.40.45]
  5    15 ms    13 ms    17 ms  ae2.FRA-M2.ip-bb.kabel-badenwuerttemberg.de [78.
42.40.13]
  6    17 ms    18 ms    16 ms  decix.xcr1.fix.cw.net [80.81.192.33]
  7    44 ms    44 ms    46 ms  xe-1-0-1-xcr1.amd.cw.net [195.2.28.81]
  8    55 ms    47 ms    43 ms  xe-4-0-0-xcr1.lsw.cw.net [195.2.25.201]
  9    29 ms    29 ms    31 ms  xe-4-1-0-xcr1.lnd.cw.net [195.2.25.54]
 10    81 ms    43 ms    43 ms  xe-0-0-0-xcr1.duc.cw.net [195.2.21.242]
 11    43 ms    44 ms    45 ms  bioware-gw2.duc.cw.net [195.2.27.90]
 12    48 ms    45 ms    45 ms  159.153.72.252
Now this is what I got when my latency started to spike to over 200k.

Time: 4:11 pm, CET

Code:
Routenverfolgung zu 159.153.72.252 über maximal 30 Abschnitte

  1  User-PC [***]  meldet: Zielhost nicht erreichbar.

Ablaufverfolgung beendet.
I did it twice during the latency jump. It was the same outcome.

Also, here's another traceroute output directly after getting disconnected from the game.

Time: 4:15 pm, CET

Code:
Routenverfolgung zu 159.153.72.252 über maximal 30 Abschnitte

  1     1 ms     2 ms     2 ms  ***
  2     *        *        *     Zeitüberschreitung der Anforderung.
  3    11 ms    20 ms    10 ms  172.30.17.61
  4    12 ms    13 ms    12 ms  HSI-KBW-078-042-040-045.hsi3.kabel-badenwuerttem
berg.de [78.42.40.45]
  5    15 ms    16 ms    15 ms  ae2.FRA-M2.ip-bb.kabel-badenwuerttemberg.de [78.
42.40.13]
  6    15 ms    15 ms    16 ms  decix.xcr1.fix.cw.net [80.81.192.33]
  7    46 ms    58 ms    46 ms  xe-1-0-1-xcr1.amd.cw.net [195.2.28.81]
  8    44 ms    44 ms    45 ms  xe-4-0-0-xcr1.lsw.cw.net [195.2.25.201]
  9    31 ms    28 ms    32 ms  xe-4-1-0-xcr1.lnd.cw.net [195.2.25.54]
 10    45 ms    44 ms    44 ms  xe-0-0-0-xcr1.duc.cw.net [195.2.21.242]
 11    47 ms    44 ms    45 ms  bioware-gw2.duc.cw.net [195.2.27.90]
 12    47 ms    49 ms    46 ms  159.153.72.252

Ablaufverfolgung beendet.
Everything seems normal after the disconnect.

I hope that helpes you Mr. Baldwin.

EDIT: Oh, btw, the latency jump occured on the Imperial fleet, but that's not representative because the latency occures everywhere seemingly at random. At least when it happens to me, don't know about other people.
. Never forget

"Use the force Harry." -Gandalf

Kraussner's Avatar


Kraussner
01.27.2012 , 09:47 AM | #30
From server Canderous Ordo
At around 7:30am Pacific Time

Did this traceroute when latency was shooting up to 100000+ ms. It's been five days since I got to swing my lightsaber at something.


Tracing route to 159.153.92.28 over a maximum of 30 hops

1 14 ms 2 ms 3 ms homeportal [192.168.1.254]
2 4 ms 4 ms 3 ms bb115-66-135-254.singnet.com.sg [***]
3 5 ms 4 ms 8 ms 202.166.126.66
4 6 ms 44 ms 10 ms ae2-10.shiraz.singnet.com.sg [202.166.126.65]
5 5 ms 5 ms 5 ms xe-11-2-0.budweiser.singnet.com.sg [202.166.122.50]
6 13 ms 4 ms 5 ms ae1-0.beck.singnet.com.sg [202.166.124.234]
7 8 ms 14 ms 5 ms 203.208.190.130
8 5 ms 8 ms 4 ms 203.208.152.209
9 197 ms 181 ms 196 ms so-3-0-2-0.plapx-cr2.ix.singtel.com [203.208.182.130]
10 179 ms 183 ms * ge-3-1-0-0.sngc3-ar4.ix.singtel.com [203.208.152.110]
11 204 ms 179 ms 182 ms ge-11-3-5.mpr2.pao1.us.above.net [64.125.13.5]
12 222 ms * 192 ms xe-2-2-0.cr2.sjc2.us.above.net [64.125.31.70]
13 180 ms 230 ms 185 ms xe-1-2-0.cr2.lax112.us.above.net [64.125.31.234]
14 * 245 ms * xe-3-2-0.cr2.iah1.us.above.net [64.125.30.49]
15 2086 ms 236 ms * xe-0-0-0.cr1.iah1.us.above.net [64.125.30.65]
16 275 ms * 273 ms xe-3-1-0.cr1.dca2.us.above.net [64.125.29.38]
17 275 ms 268 ms 301 ms xe-0-3-1.er1.iad10.us.above.net [64.125.29.6]
18 262 ms 279 ms 250 ms 64.125.199.186.t00673-01.above.net [64.125.199.186]
19 258 ms 284 ms * 159.153.92.28
20 252 ms 274 ms 254 ms 159.153.92.28

Trace complete.