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

Crossbow's Avatar


Crossbow
05.10.2012 , 01:06 PM | #471
1 53687086ms 20/ 100 = 20% 0/ 100 = 0%
0/ 100 = 0% |
2 --- 100/ 100 =100% 80/ 100 = 80% 10.87.0.1
0/ 100 = 0% |
3 22ms 20/ 100 = 20% 0/ 100 = 0% 80.5.164.45
0/ 100 = 0% |
4 28ms 21/ 100 = 21% 1/ 100 = 1% 82.15.206.245
0/ 100 = 0% |
5 27ms 21/ 100 = 21% 1/ 100 = 1% 212.43.163.82
0/ 100 = 0% |
6 35ms 21/ 100 = 21% 1/ 100 = 1% 62.253.174.18
0/ 100 = 0% |
7 27ms 20/ 100 = 20% 0/ 100 = 0% 213.248.70.29
0/ 100 = 0% |
8 31ms 20/ 100 = 20% 0/ 100 = 0% 80.91.248.217
0/ 100 = 0% |
9 36ms 20/ 100 = 20% 0/ 100 = 0% 80.91.249.134
0/ 100 = 0% |
10 41ms 20/ 100 = 20% 0/ 100 = 0% 80.239.192.82
0/ 100 = 0% |
11 36ms 20/ 100 = 20% 0/ 100 = 0% 159.153.72.46
0/ 100 = 0% |
12 41ms 20/ 100 = 20% 0/ 100 = 0% 159.153.75.111
"We ain't thinking about tomorrow, we're having too much fun today.."
John Dillenger 1934

Qael's Avatar


Qael
05.10.2012 , 08:11 PM | #472
This is my tracert from tonight to the west coast server from milaca, mn


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

  1    <1 ms    <1 ms    <1 ms  192.168.254.254
  2    46 ms    43 ms    48 ms  50.107.32.1
  3    48 ms    50 ms    47 ms  173.84.252.69
  4    61 ms     *       58 ms  xe--0-3-0---0.cor01.lkvl.mn.frontiernet.net [74.
40.4.121]
  5    82 ms     *       59 ms  ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.5
0]
  6     *        *        *     Request timed out.
  7    63 ms    62 ms    60 ms  mpr1.ord7.us [206.223.119.86]
  8     *        *        *     Request timed out.
  9   119 ms   113 ms   150 ms  xe-2-2-0.cr1.sjc2.us.above.net [64.125.26.137]
 10   159 ms   115 ms   117 ms  xe-1-1-0.er1.sjc2.us.above.net [64.125.26.198]
 11     *      114 ms   113 ms  209.66.92.106.t00673-04.above.net [209.66.92.106
]
 12   124 ms   114 ms   114 ms  159.153.68.252

Trace complete.
This is not something that only happens at parts of the day for me. This is a constant issue.

Qael's Avatar


Qael
05.14.2012 , 08:26 PM | #473
Another tracert for tonight while my game was at over 300k ms

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

  1    <1 ms    <1 ms    <1 ms  dslrouter.netgear.com [192.168.254.254]
  2    45 ms    62 ms    43 ms  50.107.32.1
  3    53 ms    51 ms    49 ms  173.84.252.69
  4    60 ms    59 ms     *     xe--0-3-0---0.cor01.lkvl.mn.frontiernet.net [74.
40.4.121]
  5    63 ms    58 ms    60 ms  ae4---0.cor01.chcg.il.frontiernet.net [74.40.5.5
0]
  6    65 ms    64 ms    56 ms  ae0---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
38]
  7    60 ms    61 ms    59 ms  mpr1.ord7.us [206.223.119.86]
  8    72 ms    63 ms    60 ms  xe-2-2-0.cr1.ord2.us.above.net [64.125.26.249]
  9   112 ms   139 ms     *     xe-1-2-0.cr1.sjc2.us.above.net [64.125.26.229]
 10   113 ms   116 ms   112 ms  xe-4-3-0.er1.sjc2.us.above.net [64.125.28.53]
 11   113 ms   114 ms   110 ms  209.66.92.106.t00673-04.above.net [209.66.92.106
]
 12   113 ms   111 ms     *     159.153.68.252
 13   116 ms   118 ms     *     159.153.68.252
 14     *      114 ms   111 ms  159.153.68.252

Trace complete.

Qael's Avatar


Qael
05.14.2012 , 08:28 PM | #474
A ping -t while experiencing 400k ms

Code:
C:\Users\Josh>ping -t 159.153.68.252

Pinging 159.153.68.252 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 159.153.68.252: bytes=32 time=112ms TTL=242
Reply from 159.153.68.252: bytes=32 time=113ms TTL=242
Reply from 159.153.68.252: bytes=32 time=114ms TTL=242
Reply from 159.153.68.252: bytes=32 time=116ms TTL=242
Reply from 159.153.68.252: bytes=32 time=112ms TTL=242
Reply from 159.153.68.252: bytes=32 time=112ms TTL=242
Reply from 159.153.68.252: bytes=32 time=123ms TTL=242
Request timed out.
Request timed out.
Reply from 159.153.68.252: bytes=32 time=121ms TTL=242
Reply from 159.153.68.252: bytes=32 time=121ms TTL=242
Reply from 159.153.68.252: bytes=32 time=112ms TTL=242
Reply from 159.153.68.252: bytes=32 time=117ms TTL=242
Reply from 159.153.68.252: bytes=32 time=121ms TTL=242
Reply from 159.153.68.252: bytes=32 time=116ms TTL=242
Reply from 159.153.68.252: bytes=32 time=113ms TTL=242

Ping statistics for 159.153.68.252:
    Packets: Sent = 18, Received = 14, Lost = 4 (22% loss),
Approximate round trip times in milli-seconds:
    Minimum = 112ms, Maximum = 123ms, Average = 115ms
Control-C
^C

elitenz's Avatar


elitenz
05.14.2012 , 08:59 PM | #475
Quote: Originally Posted by JamesBaldwin View Post
My name is James Baldwin, and I am a network engineer here at BioWare. We are continuing to look into reports regarding ongoing latency and lag issues within the game. While not all in-game lag issues are caused by network latency, we have experienced several network events in the past weeks which have negatively impacted play experience for some. We are continuing to work with our vendors to investigate ongoing issues as well as identifying end user ISPs who may be experiencing high latency or packet loss.

To help us more quickly identify these issues I am beginning this thread to better organize our network latency investigation.

If you believe you are experiencing issues due to network latency, please provide the following in this thread:
  • Time of day you feel latency is worst (if it is restricted to a particular time of day, please include your timezone)
  • Your traceroute output at the time you are experiencing the issue using the 'code' tag (see below for details)
  • Your traceroute output when you are not experiencing the issue as a comparison
To help us get maximum benefit from this thread to help you, please avoid other comments that are not reports on this issue. Thanks.

If you have output from another tool, e.g. winmtr, feel free to include this after you have included output from Microsoft's tracert.

Getting your traceroute output

You can access traceroute through a Command Prompt. Click the Start Menu and type "cmd" or "command". When the shell opens and you are presented a prompt, type one of the following:

If you play on an East Coast server: tracert 159.153.92.28
If you play on a West Coast server: tracert 159.153.68.252
If you play on a European server: tracert 159.153.72.252

When providing the traceroute output, if you are worried about providing information regarding your public IP address, remove any lines up to and include your public IP by replacing them with ***.

Please note: if you are experiencing less than 70ms of network latency and 0% packet loss, you are most likely not experiencing network-induced lag in the game.

Here's what we're looking for as an example:

Time of day: 9PM-10PM Pacific

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

  1     1 ms     1 ms     1 ms  ***
  2     1 ms     1 ms     1 ms  aus-brdr-01.twtelecom.net [207.114.255.13]
  3    68 ms    39 ms    40 ms  ash1-pr1-xe-0-3-0-0.us.twtelecom.net [66.192.240.218]
  4    42 ms    42 ms    42 ms  64.125.199.186.t00673-01.above.net [64.125.199.186]
  5    42 ms    43 ms    42 ms  159.153.92.28

Trace complete.
Thank you in advance for your help!
I suggest you start looking at the actual server that the pacific has dalborra on it's either way under spec or just lacks the bandwidth because if these problems are not fixed we will find other games to play here is my tracert and it shows there is no packet loss or anything but the game server has other ideas.

Tracing route to ip-142.73.45.175.VOCUS.net.au [175.45.73.142]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms BoB.Orcon [10.1.1.1]
2 33 ms 33 ms 33 ms xxx.xxx.xxx.xxx
3 32 ms 32 ms 33 ms xe-3-1-0-235.cre1.sky.orcon.net.nz [121.98.9.169]
4 33 ms 32 ms 32 ms vocus1.ape.net.nz [192.203.154.123]
5 57 ms 58 ms 57 ms ten-0-2-0-400.bdr01.akl01.akl.VOCUS.net.au [114.31.202.43]
6 57 ms 58 ms 58 ms ip-88.202.31.114.VOCUS.net.au [114.31.202.88]
7 62 ms 58 ms 58 ms ip-130.192.31.114.VOCUS.net.au [114.31.192.130]
8 59 ms 58 ms 58 ms ge-0-5-0-1.cor01.syd04.nsw.VOCUS.net.au [175.45.72.76]
9 57 ms 57 ms 57 ms ge-0-0-0.bdr02.syd04.nsw.VOCUS.net.au [175.45.72.78]
10 57 ms 57 ms 56 ms ip-142.73.45.175.VOCUS.net.au [175.45.73.142]

Trace complete.

Just a side Note: this game was working 100% while doing beta on the US Shadow Hand server and then once it was live on Shadow Hand then once the Australian servers started there were no issues the game was running like a gem how it should but maybe in the last week on the transfers that's when this problem started and it seems to be on and off also at all times of the day not just in peak times but you can't run things like Denova because everytime I do I am heading for victory with 300k-1,000,000 latency issues also when landing on the fleet problems also occur.

elitenz's Avatar


elitenz
05.14.2012 , 09:56 PM | #476
Once again the network is a lemon just done a screenshot also done 2 tracerts check the screenshot out

http://i50.tinypic.com/r91quw.jpg

ianmoonex's Avatar


ianmoonex
05.20.2012 , 04:08 PM | #477
Tracert test 1
Spoiler

ianmoonex's Avatar


ianmoonex
05.20.2012 , 04:09 PM | #478
Tracert test 2
Spoiler

Nandrolone's Avatar


Nandrolone
05.23.2012 , 02:44 AM | #479
I am quitting tonight because of this issue. Im sad because my Operative healer was level 48 and dominating pvp warzones, 50 was going to be awesome!

But tonight I lagged out twice in Fleet just trying to walk from the elevators to the pvp bounty board. Then on 3rd restart of game I entered a warzone and battled so hard! 10 minutes of back-and-forth battling. Just as we take the vital central flag and an awesome, memorable victory looks imminent.... NOPE. No victory for you, no xp, no valor, no medals, just 10 minutes of hard effort pissed against the wall.

I could restart the game a fourth time. I could trawl 2000 forum posts and gather heaps of information and be my own network technician just to make this one piece of software work.

OR I could bin this piece of **** before it wastes more of my time.

Say what you want about Blizzard and their ancient looking MMO, we all know Blizz would NEVER allow this bug to go unsolved.

Maybe I'll swalllow my pride and roll a gosh darn panda after all?



P.S. Every single one of you guys posting in this thread is hopelessly naive. No-one is reading your little reports, its just to make you feel important, make you feel listened to, and make you feel like action is being taken as we speak.

And make you not unsubscribe, which incidentally is the actual true only thing Bioware would take notice of.

Forget these fools-errand tech reports, the software doesnt work so bin it until it does.

RunningFox's Avatar


RunningFox
05.23.2012 , 02:53 AM | #480
Spoiler

The Executioner Legacy