Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Packet Loss to 159.153.72.252

STAR WARS: The Old Republic > English > Customer Service
Packet Loss to 159.153.72.252

ZavienUK's Avatar


ZavienUK
01.29.2013 , 11:04 AM | #11
Quote: Originally Posted by Stoofa View Post
Let me see if I can copy and paste. What tags are you using to keep the trace outputs clean? IE. The "Code" heading on your posts?
I'm wondering whether is it something to do with the fact that the first few hops don't respond to a ping (which my ISP had previously told me is normal - their equipment doesn't respond)

I'm just outputting the command to a txt file and then copying and pasting here with [ code ] and [ /code ] tags

ZavienUK's Avatar


ZavienUK
01.29.2013 , 11:06 AM | #12
Quote: Originally Posted by DNordman View Post
I also get loads of timeouts when pinging 159.153.72.252.
Thanks DNordman, Stoofa above proved the issue was at the Bioware end, but thats reassuring. My ISP has had lots of packet loss issues in the past, so it's nice to know it's not my ISP again.

Stoofa's Avatar


Stoofa
01.29.2013 , 11:09 AM | #13
OK, test to see if my copy & paste works. Obviously top is me (Corporate leased line connection from my place of work). Wrap-around isn't great I'm afraid, but you should be able to see what's what.
Code:
H:\>pathping 159.153.72.252

Tracing route to 159.153.72.252 over a maximum of 30 hops

  0  IT-000322.aminocom.com [10.171.24.22]
  1  uk-swa-gw01.aminocom.com [10.171.0.1]
  2  62.255.172.254
  3  popl-lam-4-tenge13-2225.network.virginmedia.net [213.104.8.210]
  4  popl-core-2b-xe-121-0.network.virginmedia.net [82.14.168.6]
  5  popl-bb-1b-ae9-0.network.virginmedia.net [82.14.127.245]
  6  popl-bb-1c-ae1-0.network.virginmedia.net [213.105.159.190]
  7  xe-1-0-0-xcr1.lsw.cw.net [166.63.211.129]
  8  xe-11-0-0-xcr1.duc.cw.net [195.2.21.246]
  9  bioware-gw1.duc.cw.net [195.2.27.86]
 10  159.153.72.53
 11  159.153.72.252

Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           IT-000322.aminocom.com [10.171.24.
22]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  uk-swa-gw01.aminocom.com [10.171.0
.1]
                                0/ 100 =  0%   |
  2    0ms     0/ 100 =  0%     0/ 100 =  0%  62.255.172.254
                                0/ 100 =  0%   |
  3   14ms     0/ 100 =  0%     0/ 100 =  0%  popl-lam-4-tenge13-2225.network.vi
rginmedia.net [213.104.8.210]
                                0/ 100 =  0%   |
  4    6ms     0/ 100 =  0%     0/ 100 =  0%  popl-core-2b-xe-121-0.network.virg
inmedia.net [82.14.168.6]
                                0/ 100 =  0%   |
  5    7ms     0/ 100 =  0%     0/ 100 =  0%  popl-bb-1b-ae9-0.network.virginmed
ia.net [82.14.127.245]
                                0/ 100 =  0%   |
  6   11ms     0/ 100 =  0%     0/ 100 =  0%  popl-bb-1c-ae1-0.network.virginmed
ia.net [213.105.159.190]
                                0/ 100 =  0%   |
  7   14ms     0/ 100 =  0%     0/ 100 =  0%  xe-1-0-0-xcr1.lsw.cw.net [166.63.2
11.129]
                                0/ 100 =  0%   |
  8   26ms     0/ 100 =  0%     0/ 100 =  0%  xe-11-0-0-xcr1.duc.cw.net [195.2.2
1.246]
                               15/ 100 = 15%   |
  9   21ms    20/ 100 = 20%     5/ 100 =  5%  bioware-gw1.duc.cw.net [195.2.27.8
6]
                                0/ 100 =  0%   |
 10   23ms    20/ 100 = 20%     5/ 100 =  5%  159.153.72.53
                                0/ 100 =  0%   |
 11   21ms    15/ 100 = 15%     0/ 100 =  0%  159.153.72.252

Trace complete.

H:\>

ZavienUK's Avatar


ZavienUK
01.29.2013 , 11:19 AM | #14
Thanks for all your help, it's just frustrating I can't seem to run this myself so can keep an eye on things. Guess just have to sit and wait for Bioware to resolve this now

ChrisMattar's Avatar


ChrisMattar
01.29.2013 , 11:27 AM | #15
I got 23% packet loss on those.

Quote: Originally Posted by Stoofa View Post
If you run the "pathping" command you can see that it's actually "en route" to the IP address you've listed that is causing problems.
You've got two hops:

xe-11-0-0-xcr1.duc.cw.net (195.2.21.246)
&
bioware-gw1.duc.cw.net (195.2.27.86)

We have 14% packet loss between these two hops. The first one is a radius server belonging to the ISP and the second is a Bioware Gateway - so the link between Bioware's gateway and their ISP doesn't seem great.
Further down the path we have two IP addresses:

159.153.72.53
&
159.153.72.252

Now both of these IP addresses are inside the Bioware network. This is currently showing a 4% packet loss.
Neither are good when you should see <1% packet loss at all times.