League of Legends poor network performance

[#1]

Hi Support,
I've had issues playing League of Legends for the past two nights. Last night I paid for the gaming package hoping for the situation to improve but there is no difference.
Last night I did a disconnect/reconnect on the router's web interface and the issues resolved but tonight I had severe network issues around 23:00 tonight which caused my game to lag out. Reconnecting didn't seem to improve things.
I've checked with wireshark and the packets are being classified correctly as 0xa0
Running a tracert on the game server ip shows my router pinging around 100ms(!) This was immediately after rebooting the technicolor.
Tracing route to 95.172.70.92 over a maximum of 30 hops

  1    70 ms    98 ms    98 ms  dsldevice.lan [192.168.1.254]
  2    59 ms    25 ms    23 ms  lo0-central10.ptw-ag01.plus.net [195.166.128.195]
  3    65 ms    74 ms    74 ms  link-b-central10.ptw-gw02.plus.net [212.159.2.146]
  4    68 ms    62 ms    63 ms  242.core.access.plus.net [212.159.0.242]
  5    75 ms    84 ms    62 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  6    50 ms    62 ms    95 ms  te-4-2.car5.London1.Level3.net [217.163.45.249]
  7    62 ms    90 ms    62 ms  ae-51-51.csw1.London1.Level3.net [4.69.139.88]
  8    75 ms    62 ms    44 ms  ae-117-3503.edge3.London1.Level3.net [4.69.166.138]
  9    79 ms    74 ms    52 ms  gblx-level3-50g.London1.Level3.net [4.68.110.158]
 10    79 ms    73 ms    53 ms  ae5.scr3.LON3.gblx.net [67.17.72.22]
 11   105 ms   123 ms    98 ms  xe4-2-1-10G.scr3.FRA4.gblx.net [67.16.164.114]
 12    49 ms    81 ms    77 ms  lag1.ar4.fra4.gblx.net [67.16.145.238]
 13    62 ms    96 ms    66 ms  internap.ethernet20-3.ar4.fra4.gblx.net [64.209.103.178]
 14    82 ms    93 ms    93 ms  border1.po2-8g-bbnet2.fra002.pnap.net [95.172.67.65]
 15     *     ^C

The ping to the 2nd hop is surprisingly high, I checked this a minute later and got this:

Pinging 195.166.128.195 with 32 bytes of data:
Reply from 195.166.128.195: bytes=32 time=61ms TTL=126
Reply from 195.166.128.195: bytes=32 time=49ms TTL=126
Reply from 195.166.128.195: bytes=32 time=77ms TTL=126
Reply from 195.166.128.195: bytes=32 time=52ms TTL=126

Pinging dsldevice.lan [192.168.1.254] with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Thanks in advance,
Ash

[#2]

I had this issue other week ago. Dropped about 5 times on saturday night yet connection through PN only showed one drop.
Trace showed 48ms/99ms/99ms to router. Tried a home hub, no issues since, pushing almost 2 weeks.

[#3]

Quote from: All4One

I had this issue other week ago. Dropped about 5 times on saturday night yet connection through PN only showed one drop. Trace showed 48ms/99ms/99ms to router. Tried a home hub, no issues since, pushing almost 2 weeks.

Is that a BT home hub?

[#4]

I think using any other router would be a good move if yours is giving you any sort of ping time, well so long as your on a wired connection direct to the router.
I had an issue with mtu mismatch on my pc (but I put it there on purpose to test something), then 2 days later I got a mismatch of mtu again (no idea why) so its always worth checking those things (they should be at 1500 by default in case you don't know)
but if there's nothing your aware of changing on your setup (no new software no new updates no new hardware) and your getting delays like that on your home network that aren't cleared by a reboot of both pc + router I'd be looking at the router, if the problems clear but reoccur within a day or two then I would also be looking at the router as being suspect
so if you have the ability swap it out with something you know works (even if its not as good) and if its gone belly up then you need to go through the fault checker in the PlusNet member centre (to arrange for a replacement)

[#5]

Hi roobarbandcustard,
Just wanted to mention that the high ping times to the router is down to the router itself not replying as a priority (other packets are routed first hence the delay). It still forwards outbound pings as with the normal traffic, but the first hop is slow  because of what I've mentioned.

[#6]

Thanks Matt,
I updated the firmware to 10.2.2.B this evening and that first hop is now <1ms.
Unfortunately the issues with lag are continuing, I had a period of packetloss around 21:30 which again spoiled my gaming.

  1     1 ms     1 ms     1 ms  dsldevice.lan [192.168.1.254]
  2    26 ms    25 ms    26 ms  lo0-central10.pcl-ag06.plus.net [195.166.128.187]
  3    27 ms     *       26 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.180]
  4    27 ms    30 ms     *     212.core.access.plus.net [212.159.0.212]
  5    51 ms    27 ms    26 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6    27 ms    26 ms    27 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  7     *       34 ms    38 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  8    37 ms    35 ms    33 ms  po5.peh-cr01.plus.net [84.93.232.16]
  9    35 ms    36 ms    35 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
 10    36 ms    34 ms    35 ms  portal.plus.net [212.159.8.2]

Disconnect/Reconnected and...

  1     1 ms     1 ms     2 ms  dsldevice.lan [192.168.1.254]
  2    26 ms    25 ms    24 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186]
  3    25 ms    25 ms    25 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.178]
  4    25 ms    25 ms    24 ms  210.core.access.plus.net [212.159.0.210]
  5    26 ms    25 ms    24 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  6    24 ms    25 ms    25 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  7    25 ms    25 ms    25 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  8    36 ms    33 ms    34 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  9    34 ms    32 ms    33 ms  po5.peh-cr01.plus.net [84.93.232.16]
 10    33 ms    35 ms    34 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
 11    35 ms    34 ms    34 ms  portal.plus.net [212.159.8.2]

[#7]

Just seen this post.  How is it working now?

[#8]

And about 14 hours till finals start!! WOOO

[#9]

Well all the stuff in the first post went absolutely over my head, all I know is that I'm having ridiculous lag/ping issues when playing League of Legends [and surprisingly it's not the EUW server's fault].
Occasionally the game runs absolutely fine, but then towards the evening I get between 300-700 ping and the game freezes up. All I can do is sit there and watch while the enemy kill me and the 'Attempting to reconnect' text appears.
Seriously frustrating.
What do?

[#10]

Are you on a wireless or wired connection beachchick?
I had no issues last night and rarely do on EUW.
Have you run a traceroute whilst having the issues?
How long does it stay attempting to reconnect before it reconnects?

[#11]

I'm on a wired connection, I don't know what a traceroute is and basically I disconnect every 5 seconds for about 30 seconds sooo....not good 😕

[#12]

I don't play league of legends, but playing world of tanks I am experiencing packet loss on the following hop...te-4-2.car5.London1.Level3.net ( 217.163.45.249 ) which I notice is in the tracert further up the page.
Can anything be done about this? It's been ongoing for a few weeks now but is starting to get more frequent and becoming a real annoyance, with the severity ranging from around 2 or 3% loss up to 31% loss which makes the game pretty much unplayable.
Currently loss is running @ 7% 

[#13]

Packet loss on that hop would indicate the servers for the game or enroute something like that? That hop doesn't look like a PN issue?

[#14]

Oh I agree, it's &*#$@%£ Level3 as usual. Was just hoping that if enough people were complaining, something might get done  
It's the first hop after Plusnet's network, apparently located in London Telehouse North CSL2.

[#15]

So.... anyone got any advice/fixes?