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 (Read-Only)
Information Request: Network Latency Issues
 
First BioWare Post First BioWare Post

Randytravis's Avatar


Randytravis
02.13.2012 , 10:59 AM | #271
Quote: Originally Posted by simulatorboy View Post
Just did an experiment this morning - a time when the game is almost totally empty. Ran a ping to 159.153.92.28 without the game client running at all. Most of the time, the ping comes back in 20 ms but every few minutes I get a ping for 3000 ms. This would indicate that either that server gets overloaded or some other network element is the problem. So, customer support, is this server a clean one that is just used for ping or is it in some way running the game server?
Indeed i have done the same, and had the same results. The problem is that the issues can happen at any point down the route.

Randytravis's Avatar


Randytravis
02.13.2012 , 11:05 AM | #272
I would suggest some people do a tracert to say google.com and see what happens.

Heres one ive just done which implys my issue is a ISP issue:



Tracing route to google.com [209.85.229.99]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms SkyRouter.Home [****]
2 37 ms 36 ms 40 ms dr14.ennby.ov.easynet.net [****]
3 41 ms 40 ms 38 ms 5adfcf48.bb.sky.com [90.223.207.72]
4 58 ms 58 ms 54 ms 5adfcf02.bb.sky.com [90.223.207.2]
5 57 ms 60 ms 54 ms 5adfcf02.bb.sky.com [90.223.207.2]
6 * * * Request timed out.
7 63 ms 71 ms 65 ms 64.233.175.25
8 65 ms 65 ms 59 ms 209.85.253.92
9 66 ms 68 ms 73 ms 72.14.232.134
10 70 ms 69 ms 70 ms 72.14.236.191
11 62 ms * 86 ms 209.85.243.73
12 65 ms 57 ms 59 ms ww-in-f99.1e100.net [209.85.229.99]

Trace complete.

Kindajenin's Avatar


Kindajenin
02.13.2012 , 11:09 AM | #273 This is the last staff post in this thread.  
Quote: Originally Posted by Randytravis View Post
I would suggest some people do a tracert to say google.com and see what happens.

Heres one ive just done which implys my issue is a ISP issue:



Tracing route to google.com [209.85.229.99]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms SkyRouter.Home [****]
2 37 ms 36 ms 40 ms dr14.ennby.ov.easynet.net [****]
3 41 ms 40 ms 38 ms 5adfcf48.bb.sky.com [90.223.207.72]
4 58 ms 58 ms 54 ms 5adfcf02.bb.sky.com [90.223.207.2]
5 57 ms 60 ms 54 ms 5adfcf02.bb.sky.com [90.223.207.2]
6 * * * Request timed out.
7 63 ms 71 ms 65 ms 64.233.175.25
8 65 ms 65 ms 59 ms 209.85.253.92
9 66 ms 68 ms 73 ms 72.14.232.134
10 70 ms 69 ms 70 ms 72.14.236.191
11 62 ms * 86 ms 209.85.243.73
12 65 ms 57 ms 59 ms ww-in-f99.1e100.net [209.85.229.99]

Trace complete.
Greetings Randytravis,

You can see there on your 6th line you are experiencing data loss, you really should send this information to your ISP provider to investigate.
Kindajenin| BioWare Customer Service – Forum Support

AislingKerrigan's Avatar


AislingKerrigan
02.13.2012 , 01:28 PM | #274
I don't get any time outs, yet TOR still lag spikes like hell. Is it Bioware's policy to blame the customer, ISP, whoever? That's good to know you care so little about retaining subscribers..

sumfizz's Avatar


sumfizz
02.13.2012 , 05:22 PM | #275
time zone: central, 3pm-10pm

Tracing route to 159.153.68.252 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms ***
2 44 ms 44 ms 44 ms ***
3 42 ms 43 ms 45 ms ***
4 46 ms 47 ms 46 ms ***
5 55 ms 57 ms 77 ms ***
6 65 ms 84 ms 74 ms ***
7 99 ms 100 ms 66 ms ae5-338.edge9.Dallas1.Level3.net [4.59.118.237]
8 80 ms 118 ms 81 ms ae-3-80.edge2.Dallas3.Level3.net [4.69.145.140]
9 84 ms 102 ms 88 ms mci-level3-30g.dallas3.level3.net [4.68.62.166]
10 86 ms 94 ms 93 ms 0.ae1.XL3.DFW7.ALTER.NET [152.63.96.46]
11 125 ms 127 ms 130 ms 0.ge-5-0-0.XT1.SCL2.ALTER.NET [152.63.10.10]
12 122 ms 117 ms 143 ms 0.TenGigE0.6.2.0.ALTER.NET [152.63.56.38]
13 113 ms 136 ms 105 ms vantagedatacenters-gw.customer.alter.net [152.179.99.218]
14 106 ms 122 ms 116 ms 159.153.68.53
15 137 ms 116 ms 121 ms 159.153.68.252

Trace complete.

AislingKerrigan's Avatar


AislingKerrigan
02.13.2012 , 06:05 PM | #276
Tried a trace route from my Mac to see if it was an issue with the firewall/wireless router on my PC.


Traceroute has started…

traceroute to 159.153.92.28 (159.153.92.28), 64 hops max, 72 byte packets
1 ******** (*********) 3.934 ms 0.963 ms 1.639 ms
2 96.81.60.1 (96.81.60.1) 8.336 ms 9.015 ms 7.692 ms
3 te-6-1-ur09.sacramento.ca.sacra.comcast.net (69.139.197.225) 8.425 ms 12.942 ms 16.581 ms
4 te-0-2-0-2-ar03.fresno.ca.fresno.comcast.net (68.87.221.33) 13.997 ms 13.784 ms 14.044 ms
5 pos-3-9-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.93.113) 19.966 ms 19.160 ms 20.059 ms
6 pos-2-14-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.185) 20.594 ms 22.475 ms 20.502 ms
7 pos-0-6-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.85.66) 23.248 ms 23.197 ms 31.561 ms
8 tierzero-comcast.lax1.ca.us.tierzero.net (75.149.228.134) 23.978 ms 22.966 ms 23.702 ms
9 xe-3-0-0.er2.sjc2.us.above.net (64.125.30.177) 24.470 ms 23.263 ms 24.653 ms
10 xe-0-1-0.cr2.sjc2.us.above.net (64.125.28.22) 23.844 ms 23.313 ms 23.916 ms
11 xe-2-1-0.cr2.lax112.us.above.net (64.125.26.29) 31.385 ms 78.036 ms 33.725 ms
12 xe-2-3-0.cr2.iah1.us.above.net (64.125.25.17) 109.072 ms 64.091 ms 63.878 ms
13 xe-1-0-0.cr1.iah1.us.above.net (64.125.30.69) 63.915 ms 83.844 ms 65.090 ms
14 xe-3-1-0.cr1.dca2.us.above.net (64.125.29.38) 101.170 ms 95.110 ms 93.272 ms
15 xe-7-0-0.er1.iad10.us.above.net (64.125.29.209) 93.339 ms 93.411 ms 92.674 ms
16 64.125.199.186.t00673-01.above.net (64.125.199.186) 93.369 ms 92.960 ms 92.511 ms
17 159.153.92.28 (159.153.92.28) 92.872 ms 93.465 ms 92.326 ms




I also pinged 159.153.92.28 and noticed occasional packet loss (15%+).

muleskinner's Avatar


muleskinner
02.13.2012 , 07:22 PM | #277
I have 5 here, I also sent these results to my ISP. The last two weeks or so the game has slowly become almost unplayable, it appears that I may have found the problem. Still it appears there is plenty of lag out there even when my ISP is working.

Tracing route to 159.153.92.28 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms ****
2 10 ms 9 ms 10 ms adsl-64-175-39-254.dsl.pltn13.pacbell.net [64.175.39.254]
3 10 ms * 10 ms dist2-vlan60.pltnca.sbcglobal.net [76.197.23.194]
4 10 ms 28 ms 14 ms ag2-10g0-12-5-0.pltnca.sbcglobal.net [151.164.103.6]
5 11 ms 11 ms 12 ms ggr7.sffca.ip.att.net [12.122.114.13]
6 * 13 ms 14 ms xe-1-2-0.mpr4.sjc7.us.above.net [64.125.12.117]
7 * 15 ms 14 ms xe-3-0-0.er2.sjc2.us.above.net [64.125.30.177]
8 15 ms 14 ms 14 ms xe-0-1-0.cr2.sjc2.us.above.net [64.125.28.22]
9 23 ms 22 ms 23 ms xe-2-1-0.cr2.lax112.us.above.net [64.125.26.29]
10 58 ms 57 ms 57 ms xe-2-3-0.cr2.iah1.us.above.net [64.125.25.17]
11 57 ms 58 ms 57 ms xe-1-0-0.cr1.iah1.us.above.net [64.125.30.69]
12 83 ms * 83 ms xe-3-1-0.cr1.dca2.us.above.net [64.125.29.38]
13 86 ms 82 ms 82 ms xe-7-0-0.er1.iad10.us.above.net [64.125.29.209]
14 83 ms 82 ms 83 ms 64.125.199.186.t00673-01.above.net [64.125.199.186]
15 82 ms 83 ms 83 ms 159.153.92.28

Trace complete.


Tracing route to 159.153.92.28 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms ****
2 10 ms 11 ms 10 ms adsl-64-175-39-254.dsl.pltn13.pacbell.net [64.175.39.254]
3 * * * Request timed out.
4 11 ms 11 ms 11 ms ag2-10g0-12-5-0.pltnca.sbcglobal.net [151.164.103.6]
5 11 ms * * ggr7.sffca.ip.att.net [12.122.114.13]
6 13 ms * 49 ms xe-1-2-0.mpr4.sjc7.us.above.net [64.125.12.117]
7 14 ms 14 ms 14 ms xe-3-0-0.er2.sjc2.us.above.net [64.125.30.177]
8 27 ms 14 ms 14 ms xe-0-1-0.cr2.sjc2.us.above.net [64.125.28.22]
9 23 ms 22 ms 77 ms xe-2-1-0.cr2.lax112.us.above.net [64.125.26.29]
10 57 ms 90 ms 57 ms xe-2-3-0.cr2.iah1.us.above.net [64.125.25.17]
11 * 57 ms 58 ms xe-1-0-0.cr1.iah1.us.above.net [64.125.30.69]
12 83 ms 83 ms 83 ms xe-3-1-0.cr1.dca2.us.above.net [64.125.29.38]
13 * 82 ms * xe-7-0-0.er1.iad10.us.above.net [64.125.29.209]
14 82 ms 83 ms 83 ms 64.125.199.186.t00673-01.above.net [64.125.199.186]
15 83 ms * 83 ms 159.153.92.28

Trace complete.


Tracing route to 159.153.92.28 over a maximum of 30 hops

1 1 ms 1 ms 1 ms ****
2 10 ms 10 ms 10 ms adsl-64-175-39-254.dsl.pltn13.pacbell.net [64.175.39.254]
3 9 ms 10 ms 10 ms dist2-vlan60.pltnca.sbcglobal.net [76.197.23.194]
4 * 10 ms 10 ms ag2-10g0-12-5-0.pltnca.sbcglobal.net [151.164.103.6]
5 11 ms 23 ms 39 ms ggr7.sffca.ip.att.net [12.122.114.13]
6 * 13 ms 13 ms xe-1-2-0.mpr4.sjc7.us.above.net [64.125.12.117]
7 * 15 ms 16 ms xe-3-0-0.er2.sjc2.us.above.net [64.125.30.177]
8 14 ms 14 ms 15 ms xe-0-1-0.cr2.sjc2.us.above.net [64.125.28.22]
9 24 ms 32 ms 57 ms xe-1-2-0.cr2.lax112.us.above.net [64.125.31.234]
10 23 ms 23 ms * xe-0-0-0.cr1.lax112.us.above.net [64.125.30.233]
11 * * 57 ms xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]
12 83 ms 85 ms 86 ms xe-3-1-0.cr1.dca2.us.above.net [64.125.29.38]
13 82 ms 82 ms 82 ms xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]
14 * 82 ms 82 ms 64.125.199.186.t00673-01.above.net [64.125.199.186]
15 82 ms 82 ms 86 ms 159.153.92.28

Trace complete.


Tracing route to 159.153.92.28 over a maximum of 30 hops

1 1 ms 1 ms <1 ms ****
2 10 ms 25 ms 18 ms adsl-64-175-39-254.dsl.pltn13.pacbell.net [64.175.39.254]
3 10 ms 10 ms * dist2-vlan60.pltnca.sbcglobal.net [76.197.23.194]
4 * 10 ms 21 ms ag2-10g0-12-5-0.pltnca.sbcglobal.net [151.164.103.6]
5 * * * Request timed out.
6 * 52 ms 13 ms xe-1-2-0.mpr4.sjc7.us.above.net [64.125.12.117]
7 15 ms 14 ms 14 ms xe-3-0-0.er2.sjc2.us.above.net [64.125.30.177]
8 * 14 ms 14 ms xe-0-1-0.cr2.sjc2.us.above.net [64.125.28.22]
9 22 ms 22 ms * xe-1-2-0.cr2.lax112.us.above.net [64.125.31.234]
10 23 ms 23 ms 24 ms xe-0-0-0.cr1.lax112.us.above.net [64.125.30.233]
11 * 57 ms 58 ms xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]
12 83 ms 83 ms 83 ms xe-3-1-0.cr1.dca2.us.above.net [64.125.29.38]
13 82 ms 82 ms 82 ms xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]
14 83 ms 82 ms 82 ms 64.125.199.186.t00673-01.above.net [64.125.199.186]
15 83 ms 83 ms 83 ms 159.153.92.28

Trace complete.

Tracing route to 159.153.92.28 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms ****
2 10 ms 10 ms 10 ms adsl-64-175-39-254.dsl.pltn13.pacbell.net [64.175.39.254]
3 10 ms * 10 ms dist2-vlan60.pltnca.sbcglobal.net [76.197.23.194]
4 10 ms 10 ms 9 ms ag2-10g0-12-5-0.pltnca.sbcglobal.net [151.164.103.6]
5 11 ms 11 ms 11 ms ggr7.sffca.ip.att.net [12.122.114.13]
6 13 ms * 13 ms xe-1-2-0.mpr4.sjc7.us.above.net [64.125.12.117]
7 14 ms 14 ms 14 ms xe-3-0-0.er2.sjc2.us.above.net [64.125.30.177]
8 15 ms 14 ms 15 ms xe-0-1-0.cr2.sjc2.us.above.net [64.125.28.22]
9 25 ms 22 ms 23 ms xe-1-2-0.cr2.lax112.us.above.net [64.125.31.234]
10 * 22 ms 23 ms xe-0-0-0.cr1.lax112.us.above.net [64.125.30.233]
11 57 ms 57 ms 57 ms xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]
12 119 ms 82 ms 83 ms xe-3-1-0.cr1.dca2.us.above.net [64.125.29.38]
13 82 ms 82 ms 82 ms xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]
14 107 ms 82 ms * 64.125.199.186.t00673-01.above.net [64.125.199.186]
15 84 ms 249 ms 92 ms 159.153.92.28
Trace complete.
There are 10 kinds of people, those who understand binary and those who do not.

Chahur's Avatar


Chahur
02.13.2012 , 07:39 PM | #278
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.
Same here, I can't even get past the character selection screen to play the game sometimes, I don't even have to be on a server or playing the game for lag to hit me, this just started about 2 weeks ago, prior to that the game ran perfectly.

Edit: I just tried to log in and the lag hit before I could select my character, this is on a west coast server, my latency is always 100+ regardless of when I log in or which character I choose, I always have full connection to the server. I'm not a techie so I don't know if this is good or bad. I did notice prior to the lag problem that my graphics card alway seemed to be working over time, and I could faintly smell something was getting hot, not sure if it was my computer or something else. IS it possible that something is wrong with my graphics card, even though it still functions? I mean my monitor still works so I don't think my graphics card is totally smoked, but maybe there is another issue that is unrelated to this game.

JediKamo's Avatar


JediKamo
02.13.2012 , 08:12 PM | #279
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>tracert 159.153.92.28

Tracing route to 159.153.92.28 over a maximum of 30 hops

  1     3 ms     3 ms     2 ms  dslrouter.westell.com [192.168.1.1]
  2    31 ms    28 ms    27 ms  74-42-176-1.dsl2.plcd.ca.frontiernet.net [74.42.
176.1]
  3    34 ms    33 ms    48 ms  74.40.45.69
  4    45 ms    37 ms    40 ms  xe--0-2-0---0.cor02.plal.ca.frontiernet.net [74.
40.3.173]
  5    60 ms    35 ms    28 ms  ae1---0.cbr01.plal.ca.frontiernet.net [74.40.3.1
70]
  6    33 ms    34 ms    28 ms  ge4-0.mpr2.pao1.us.mfnx.net [198.32.176.11]
  7    34 ms    30 ms    31 ms  xe-3-0-0.cr1.sjc2.us.above.net [64.125.31.66]
  8    48 ms    50 ms    44 ms  xe-1-2-0.cr1.lax112.us.above.net [64.125.29.2]
  9    96 ms   119 ms    98 ms  xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]
 10   119 ms   108 ms   106 ms  xe-2-1-0.cr1.dca2.us.above.net [64.125.25.113]
 11   107 ms   119 ms   107 ms  xe-0-0-1.er1.iad10.us.above.net [64.125.31.206]

 12   114 ms   107 ms   107 ms  64.125.199.186.t00673-01.above.net [64.125.199.1
86]
 13   137 ms   132 ms   120 ms  159.153.92.28

Trace complete.

C:\Windows\system32>
Lag of 25,000 and did this tracert (Rubat Crystal, 6:08pm PST)

I think it is clear that this time the problem is NOT with the internet connection anywhere along the line.

AislingKerrigan's Avatar


AislingKerrigan
02.13.2012 , 08:13 PM | #280
Quote: Originally Posted by JediKamo View Post
Code:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>tracert 159.153.92.28

Tracing route to 159.153.92.28 over a maximum of 30 hops

  1     3 ms     3 ms     2 ms  dslrouter.westell.com [192.168.1.1]
  2    31 ms    28 ms    27 ms  74-42-176-1.dsl2.plcd.ca.frontiernet.net [74.42.
176.1]
  3    34 ms    33 ms    48 ms  74.40.45.69
  4    45 ms    37 ms    40 ms  xe--0-2-0---0.cor02.plal.ca.frontiernet.net [74.
40.3.173]
  5    60 ms    35 ms    28 ms  ae1---0.cbr01.plal.ca.frontiernet.net [74.40.3.1
70]
  6    33 ms    34 ms    28 ms  ge4-0.mpr2.pao1.us.mfnx.net [198.32.176.11]
  7    34 ms    30 ms    31 ms  xe-3-0-0.cr1.sjc2.us.above.net [64.125.31.66]
  8    48 ms    50 ms    44 ms  xe-1-2-0.cr1.lax112.us.above.net [64.125.29.2]
  9    96 ms   119 ms    98 ms  xe-2-0-0.cr1.iah1.us.above.net [64.125.25.46]
 10   119 ms   108 ms   106 ms  xe-2-1-0.cr1.dca2.us.above.net [64.125.25.113]
 11   107 ms   119 ms   107 ms  xe-0-0-1.er1.iad10.us.above.net [64.125.31.206]

 12   114 ms   107 ms   107 ms  64.125.199.186.t00673-01.above.net [64.125.199.1
86]
 13   137 ms   132 ms   120 ms  159.153.92.28

Trace complete.

C:\Windows\system32>
Lag of 25,000 and did this tracert (Rubat Crystal, 6:08pm PST)

I think it is clear that this time the problem is NOT with the internet connection anywhere along the line.
We may think it is clear but I don't think Bioware does.. Will just be more of the "It's your fault/It's your ISP" excuses.