View Single Post

LNSSnorkle's Avatar


LNSSnorkle
01.06.2013 , 07:36 AM | #513
Greetings. Starting yesterday, me and several of my friends spread out over Portugal have had nearly constant lag spikes when playing SWTOR. This started yesterday. The connection bar has the usual 4 bars(40-55 latency), then suddenly drops to 2 bars (300-500 latency), sometimes 1 red bar (1300+ latency), then back to normal. It has happened on the "Tomb of Freedon Nadd" european server, both on empire and republic side. We are spread out over 3 cities and 2 different ISPs.

Time of day you feel latency is worst (if it is restricted to a particular time of day, please include your timezone)
- It's constant and happens every so often, at various times of day. It has happened in the morning, afternoon and evening. Happens approximately 10-20 times per hour.

Your traceroute output at the time you are experiencing the issue using the 'code' tag (see below for details)
-

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



  1    <1 ms     1 ms    <1 ms  zonhub.home [192.168.1.1] 

  2     6 ms     5 ms     6 ms  10.22.255.254 

  3     6 ms     5 ms     6 ms  10.137.198.209 

  4     8 ms     7 ms     8 ms  10.255.48.74 

  5     8 ms     7 ms     7 ms  195.219.214.21 

  6    34 ms    36 ms    35 ms  80.231.158.5 

  7    36 ms    36 ms    35 ms  80.231.158.10 

  8    35 ms    35 ms    61 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22] 

  9    39 ms     *       43 ms  Vlan756.icore2.LDN-London.as6453.net [80.231.131.26] 

 10    83 ms    36 ms    36 ms  Vlan523.icore2.LDN-London.as6453.net [195.219.83.26] 

 11    47 ms    45 ms    44 ms  ae5-xcr1.lsw.cw.net [195.2.28.25] 

 12    47 ms    46 ms    47 ms  xe-11-0-0-xcr1.duc.cw.net [195.2.21.246] 

 13    45 ms    45 ms    46 ms  bioware-gw2.duc.cw.net [195.2.27.90] 

 14    46 ms    47 ms    53 ms  159.153.72.252 



Trace complete.
Your traceroute output when you are not experiencing the issue as a comparison
- Since it is nearly constant and unpredictable, I don't think this can be seen in traceroutes, let alone provide one for comparison when it is not happening... Still, here is one I did last night for comparison...


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



  1    <1 ms     1 ms    <1 ms  zonhub.home [192.168.1.1] 

  2     6 ms     6 ms     5 ms  10.22.255.254 

  3     6 ms     5 ms     6 ms  10.137.198.209 

  4     7 ms     7 ms     8 ms  10.255.48.74 

  5     8 ms     7 ms     8 ms  195.219.214.21 

  6    36 ms    36 ms    39 ms  80.231.158.5 

  7    36 ms    37 ms    34 ms  80.231.158.10 

  8    35 ms    36 ms    53 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22] 

  9    38 ms    36 ms     *     Vlan756.icore2.LDN-London.as6453.net [80.231.131.26] 

 10    66 ms    36 ms    36 ms  Vlan523.icore2.LDN-London.as6453.net [195.219.83.26] 

 11    46 ms    36 ms    37 ms  ae5-xcr1.lsw.cw.net [195.2.28.25] 

 12    46 ms    47 ms    46 ms  xe-11-0-0-xcr1.duc.cw.net [195.2.21.246] 

 13    46 ms    45 ms    45 ms  bioware-gw2.duc.cw.net [195.2.27.90] 

 14    46 ms    46 ms    50 ms  159.153.72.252 



Trace complete.
The WinMTR tool however finds something interesting in a node... Vlan756.icore2.LDN-London.as6453.net is dropping packets left and right, as seen below.

Code:
|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             zonhub.home -    0 |   51 |   51 |    0 |    0 |    2 |    1 |

|                           10.22.255.254 -    0 |   51 |   51 |    5 |   10 |   13 |    5 |

|                          10.137.198.209 -    0 |   51 |   51 |    5 |    9 |   15 |    6 |

|                            10.255.48.74 -    0 |   51 |   51 |    7 |    8 |   18 |   10 |

|                          195.219.214.21 -    0 |   51 |   51 |    7 |   11 |   50 |   12 |

|                            80.231.158.5 -    0 |   51 |   51 |   35 |   41 |   57 |   40 |

|                           80.231.158.10 -    0 |   51 |   51 |   34 |   44 |   95 |   42 |

|    if-19-2.tcore2.L78-London.as6453.net -    0 |   51 |   51 |   34 |   41 |   57 |   40 |

|    Vlan756.icore2.LDN-London.as6453.net -   12 |   34 |   30 |   34 |   42 |   56 |   45 |

|    Vlan523.icore2.LDN-London.as6453.net -    0 |   51 |   51 |   39 |   43 |  105 |   39 |

|                     ae5-xcr1.lsw.cw.net -    0 |   51 |   51 |   35 |   41 |   67 |   40 |

|               xe-11-0-0-xcr1.duc.cw.net -    0 |   51 |   51 |   46 |   55 |  125 |   51 |

|                  bioware-gw2.duc.cw.net -    0 |   51 |   51 |   45 |   50 |   55 |   46 |

|                          159.153.72.252 -    0 |   51 |   51 |   48 |   52 |   62 |   50 |

|________________________________________________|______|______|______|______|______|______|
To finish this, I'd just like to state that i used to work for my ISP, and 4 of the other affected players still do, and they are looking into the issue themselves, and have yet to find any problem related to their infrastructure. Most likely it is really an issue affecting that hop (Vlan756.icore2.LDN-London.as6453.net ) in the route the packets are taking to get to the bioware server. Is there anything that can be done to fix this?