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

OwenBrooks's Avatar


OwenBrooks
01.16.2013 , 04:51 AM | #541
Hi Huxebewa,

if you are sure you have no major traffic on your link, have a talk to your ISP and provide them these tracerts.

1859 ms 86 ms 2295 ms 10.106.208.1 This is just after your router, need to work out with the ISP why it is like this.

Hi Oliseth,

I can see no major issues, apart from that one drop in the first tracert at level3.net.

Have a read of SoulPrism post in this thread, nicely detailed, it may help you.

http://www.swtor.com/community/showthread.php?t=585974

QQbubblehrth's Avatar


QQbubblehrth
01.21.2013 , 05:16 AM | #542
Up until saturday night my game ran fine, experienced minor-magor lag when going to a new planet but that usually cleared up after 5 minutes or so. since saturday night i have been getting horrible lag for the entire time i am on. The lag has made doing any warzones virtually impossible, has been causing my character to not appear visually on my screen for up to a minutes after logging onto it, other player characters and NPC's dont appear for sometimes up to 5-10 minutes after log in. other visual graphics are 'Blurry' for an extended length after log in as well. Asked about i in game and was told to run a tracert, did so and guess what... alter.net popped up on it. Been reading this thread and it appears that this has been an Issue for a Year?!?! seriously BW pull your thumbs outta yer butts and do something to make it so our connections dont have to go through these servers that have been causing YOUR PAYING CUSTOMERS issues for at least a year!!!

Valkyrst's Avatar


Valkyrst
01.29.2013 , 07:39 AM | #543
Same issues as above poster on the Progenitor.

Normally have a ping of 140ms (from India) but recently I've been having severe spikes that sometimes result in disconnection or just me standing in one place whilst the entire universe destroys me.

It's becoming really annoying since Warzones are almost impossible without things going badly wrong.

Hekatai's Avatar


Hekatai
01.29.2013 , 11:27 AM | #544
Code:
Tracing route to 159.153.72.252 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  P-2812HNU [10.0.0.138]
  2    22 ms    22 ms    27 ms  ti0024a380-l100.ti.telenor.net [148.122.176.174]

  3    23 ms    21 ms    22 ms  ti0024d320-ge1-0-1-10.ti.telenor.net [146.172.82
.17]
  4    44 ms    45 ms    44 ms  ti0024c400-xe8-0-2.ti.telenor.net [146.172.99.21
3]
  5    52 ms    45 ms    45 ms  ti0005c400-ae7-0.ti.telenor.net [146.172.98.130]

  6    55 ms    44 ms    51 ms  ti0001c400-ae2-0.ti.telenor.net [146.172.100.121
]
  7    45 ms    49 ms    47 ms  ti3001c310-ae9-0.ti.telenor.net [146.172.98.45]

  8    45 ms    48 ms    54 ms  ti3002b400-ae1-0.ti.telenor.net [146.172.105.82]

  9    84 ms    77 ms    77 ms  s-b2-link.telia.net [213.248.93.137]
 10    79 ms    88 ms    84 ms  s-bb1-link.telia.net [80.91.247.216]
 11   129 ms   218 ms   132 ms  hbg-bb1-link.telia.net [213.155.130.9]
 12   177 ms   142 ms   187 ms  ldn-bb1-link.telia.net [80.91.250.221]
 13   160 ms   148 ms   149 ms  dln-b3-link.telia.net [80.91.249.134]
 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.

Poopflinga's Avatar


Poopflinga
01.30.2013 , 06:43 PM | #545
I only get a lag spike after being log'd in for about one minute. My latency is always around 27ms for the last year playing. Now I get latency that increases by about 900ms per second until I get to 25,000ms in which the loading screen appears and the game basically does nothing.


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

C:\>tracert 159.153.92.28

Tracing route to 159.153.92.28 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms POOPFLINGA [192.168.1.1]
2 8 ms 7 ms 7 ms 96.120.64.49
3 7 ms 7 ms 7 ms te-5-4-ur01.warren.ma.boston.comcast.net [68.87.
159.97]
4 9 ms 16 ms 7 ms te-7-1-ur02.springfield.ma.boston.comcast.net [6
8.87.145.121]
5 22 ms 18 ms 11 ms be-24-ar01.chartford.ct.hartford.comcast.net [68
.85.69.125]
6 13 ms 11 ms 11 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [
68.85.162.69]
7 22 ms 35 ms 23 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.93.185]
8 22 ms 18 ms 19 ms pos-1-0-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.42]
9 * 26 ms * Vlan546.icore1.NTO-NewYork.as6453.net [209.58.26
.57]
10 19 ms 17 ms 19 ms Vlan590.icore1.NTO-NewYork.as6453.net [209.58.26
.94]
11 25 ms 24 ms 25 ms 0.xe-7-0-3.XT1.DCA5.ALTER.NET [152.63.40.41]
12 30 ms 27 ms 27 ms TenGigE0-4-4-0.GW5.DCA5.ALTER.NET [152.63.4.109]

13 26 ms 27 ms 27 ms dft-gw.customer.alter.net [152.179.164.162]
14 26 ms 27 ms 26 ms 159.153.92.28

Trace complete.

C:\>tracert 159.153.92.28

Tracing route to 159.153.92.28 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms POOPFLINGA [192.168.1.1]
2 8 ms 8 ms 6 ms 96.120.64.49
3 9 ms 8 ms 7 ms te-5-4-ur01.warren.ma.boston.comcast.net [68.87.
159.97]
4 8 ms 8 ms 7 ms te-7-1-ur02.springfield.ma.boston.comcast.net [6
8.87.145.121]
5 11 ms 11 ms 11 ms be-24-ar01.chartford.ct.hartford.comcast.net [68
.85.69.125]
6 16 ms 17 ms 14 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [
68.85.162.69]
7 25 ms 22 ms 24 ms he-2-8-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.93.185]
8 18 ms 20 ms 19 ms pos-1-0-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.42]
9 19 ms * * Vlan546.icore1.NTO-NewYork.as6453.net [209.58.26
.57]
10 19 ms 20 ms 19 ms Vlan590.icore1.NTO-NewYork.as6453.net [209.58.26
.94]
11 25 ms 25 ms 24 ms 0.xe-7-0-3.XT1.DCA5.ALTER.NET [152.63.40.41]
12 29 ms 27 ms 27 ms TenGigE0-4-4-0.GW5.DCA5.ALTER.NET [152.63.4.109]

13 25 ms 27 ms 26 ms dft-gw.customer.alter.net [152.179.164.162]
14 27 ms 27 ms 25 ms 159.153.92.28

Trace complete.

C:\Users\Jake>

bigray's Avatar


bigray
01.30.2013 , 07:01 PM | #546
Tracing route to 159.153.92.28 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 7 ms 96.120.36.25
3 9 ms 9 ms 14 ms te-9-2-ur02.boynton.fl.pompano.comcast.net [68.8
6.161.193]
4 10 ms 9 ms 8 ms 68.86.165.50
5 13 ms 15 ms 16 ms te-0-4-0-4-ar03.northdade.fl.pompano.comcast.net
[68.85.127.201]
6 17 ms 23 ms 23 ms he-2-7-0-0-cr01.miami.fl.ibone.comcast.net [68.8
6.93.81]
7 16 ms 15 ms 15 ms pos-0-0-0-0-pe01.nota.fl.ibone.comcast.net [68.8
6.87.102]
8 29 ms 29 ms 29 ms ix-0-1-2-0.tcore1.MLN-Miami.as6453.net [66.110.9
.101]
9 29 ms 29 ms 39 ms 0.xe-7-3-0.BR1.MIA19.ALTER.NET [204.255.168.9]
10 38 ms 42 ms 37 ms 0.xe-2-1-4.XT1.DCA5.ALTER.NET [152.63.6.85]
11 52 ms 38 ms 39 ms TenGigE0-4-2-0.GW5.DCA5.ALTER.NET [152.63.4.105]

12 43 ms 39 ms 43 ms dft-gw.customer.alter.net [152.179.164.162]
13 43 ms 38 ms 40 ms 159.153.92.28

I don't think it's an internet problem. Something is up with your local infrastructure.

Tramell's Avatar


Tramell
01.30.2013 , 07:06 PM | #547
Timezone: EST
Current time of test: 7:58pm

Tracing route to 159.153.92.28 over a maximum of 30 hops

1 7 ms 3 ms 3 ms [***]
2 35 ms 10 ms 20 ms 96.153.40.1
3 16 ms 13 ms 16 ms te-8-3-rr01.bloomfield.ct.hartford.comcast.net [68.85.186.193]
4 24 ms 17 ms 12 ms be-50-ar01.chartford.ct.hartford.comcast.net [68.87.182.238]
5 25 ms 19 ms 18 ms pos-1-4-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.69]
6 52 ms 46 ms 47 ms he-2-6-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.93.33]
7 45 ms 42 ms 64 ms pos-0-4-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.85.22]
8 * * * Request timed out.
9 49 ms 43 ms 45 ms 0.ae20.BR2.NYC4.ALTER.NET [204.255.168.173]
10 50 ms 50 ms 54 ms 0.xe-7-0-3.XT1.DCA5.ALTER.NET [152.63.40.41]
11 62 ms 63 ms 61 ms TenGigE0-6-0-0.GW5.DCA5.ALTER.NET [152.63.37.110
]
12 56 ms 54 ms 51 ms dft-gw.customer.alter.net [152.179.164.162]
13 54 ms 56 ms 57 ms 159.153.92.28

Trace complete.

tdprange's Avatar


tdprange
01.30.2013 , 07:06 PM | #548
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Users\Trent> tracert 159.153.92.28
Tracing route to 159.153.92.28 over a maximum of 30 hops

1 3 ms <1 ms 1 ms 192.168.1.1
2 62 ms 26 ms 29 ms 76.21.192.1
3 12 ms 13 ms 14 ms xe-0-2-0-32767-sur01.alexandria.va.bad.comcast.n
et [68.85.147.77]
4 13 ms 14 ms 20 ms ae-21-0-ar04.capitolhghts.md.bad.comcast.net [68
.85.114.25]
5 19 ms 17 ms 16 ms pos-4-3-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.90.173]
6 15 ms 15 ms 14 ms pos-0-2-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.70]
7 14 ms 14 ms 16 ms 66.208.233.42
8 32 ms 27 ms 30 ms 216.6.87.34
9 30 ms 30 ms 28 ms 0.xe-3-1-3.XL3.IAD8.ALTER.NET [152.63.39.26]
10 30 ms 32 ms 35 ms 0.xe-10-0-0.GW10.IAD8.ALTER.NET [152.63.33.193]

11 30 ms 31 ms 28 ms dft-gw.customer.alter.net [152.179.50.154]
12 32 ms 28 ms 28 ms 159.153.92.69
13 33 ms 28 ms 34 ms 159.153.92.28

Trace complete.

C:\Users\Trent>

bigray's Avatar


bigray
01.30.2013 , 07:09 PM | #549
More info - I was just in the game and kept a ping running. As soon as the game froze I switched out and saw successive failed packets, and then the pings recovered. However the client does not seem to be able to recover from this kind of condition.

Reply from 159.153.92.28: bytes=32 time=39ms TTL=241
Reply from 159.153.92.28: bytes=32 time=39ms TTL=241
Reply from 159.153.92.28: bytes=32 time=39ms TTL=241
Reply from 159.153.92.28: bytes=32 time=41ms TTL=241
Reply from 159.153.92.28: bytes=32 time=49ms TTL=241
Reply from 159.153.92.28: bytes=32 time=40ms TTL=241
Reply from 159.153.92.28: bytes=32 time=40ms TTL=241
Reply from 159.153.92.28: bytes=32 time=38ms TTL=241
Reply from 159.153.92.28: bytes=32 time=40ms TTL=241
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 159.153.92.28: bytes=32 time=45ms TTL=241
Reply from 159.153.92.28: bytes=32 time=44ms TTL=241
Reply from 159.153.92.28: bytes=32 time=48ms TTL=241
Reply from 159.153.92.28: bytes=32 time=44ms TTL=241
Reply from 159.153.92.28: bytes=32 time=49ms TTL=241
Reply from 159.153.92.28: bytes=32 time=44ms TTL=241
Reply from 159.153.92.28: bytes=32 time=45ms TTL=241
Reply from 159.153.92.28: bytes=32 time=44ms TTL=241
Reply from 159.153.92.28: bytes=32 time=45ms TTL=241
Reply from 159.153.92.28: bytes=32 time=45ms TTL=241
Reply from 159.153.92.28: bytes=32 time=45ms TTL=241
Reply from 159.153.92.28: bytes=32 time=44ms TTL=241

Ping statistics for 159.153.92.28:
Packets: Sent = 106, Received = 101, Lost = 5 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 50ms, Average = 40ms

By the time I tried to run a tracert, the pings had recovered and so the trace was normal. I think you've got a bad piece of equipment somewhere in your network. I do have a network background and run a datacenter myself so it's at least an educated guess. Good luck - this kind of thing can be a PIA to track down!

Scoob's Avatar


Scoob
02.07.2013 , 08:58 AM | #550
Tracing route to 159.153.92.28 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 27 ms 26 ms 27 ms drr01.crdl.il.frontiernet.net [74.42.148.56]
3 27 ms 26 ms 26 ms 50.40.128.5
4 33 ms 33 ms 34 ms 74.42.149.157
5 35 ms 34 ms 34 ms xe--10-3-0---0.cor02.chcg.il.frontiernet.net [74
.40.1.97]
6 34 ms 34 ms 34 ms ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
42]
7 34 ms 35 ms 34 ms mpr1.ord7.us [206.223.119.86]
8 35 ms 38 ms 36 ms xe-2-3-0.cr1.ord2.us.above.net [64.125.22.209]
9 56 ms 57 ms 55 ms xe-2-0-0.cr1.lga5.us.above.net [64.125.24.33]
10 58 ms 60 ms 57 ms xe-3-2-0.cr1.dca2.us.above.net [64.125.26.101]
11 60 ms 61 ms 61 ms xe-3-2-0.er1.iad10.us.above.net [64.125.29.209]

12 61 ms 60 ms 61 ms 64.125.199.186.t00673-01.above.net [64.125.199.1
86]
13 62 ms 62 ms 62 ms 159.153.92.28

Trace complete.