Welcome to the Forum Archive!

Years of conversation fill a tonne of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out Boards to join in the latest League of Legends discussions.

GO TO BOARDS


Random lag spikes?

Comment below rating threshold, click here to show it.

Cypherous

Member

02-11-2013

Quote:
Verzwileon:
Bump, got it up to 13000 ping after a couple of minutes smooth playing... every game since last night.
Playing on mac


Bumps dont help if you dont post the requested information

On a mac you need top open terminal and type in traceroute 95.172.65.76

I am unfamiliar with the exact procedure to copy that information though but google will help you


Comment below rating threshold, click here to show it.

Andro

Junior Member

02-11-2013

Hey everyone,

here are the results of my "tracert 95.172.65.76" command. I guess at the very moment it looks fine, but as soon as i start playing the ping jumps up and down. Let me know if that data helps or if I should do it again.

Thanks a lot!

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1ST: NOT INGAME

Routenverfolgung zu 95.172.65.76 über maximal 30 Abschnitte

1 2 ms 4 ms 5 ms alice.box [192.168.1.1]
2 22 ms 18 ms * lo1.br10.kae.de.hansenet.net [213.191.89.42]
3 20 ms 21 ms 21 ms ae1-102.cr02.str.de.hansenet.net [213.191.88.226
]
4 35 ms 36 ms 36 ms ge-5-1-0-0.cr02.ber.de.hansenet.net [213.191.66.
233]
5 41 ms 42 ms 42 ms so-0-2-0-0.cr01.asham.de.hansenet.net [213.191.8
7.137]
6 42 ms 40 ms 37 ms ae0-0.xd01.asham.de.hansenet.net [62.109.72.2]
7 39 ms 37 ms 37 ms ae0-0.pr01.asham.de.hansenet.net [213.191.66.162
]
8 37 ms 38 ms 46 ms rmwc-hmbg-de03-chan-0-0.nw.mediaways.net [213.20
.88.202]
9 47 ms 41 ms 97 ms rmwc-hmbg-de04-xe-0-0-1-0.nw.mediaways.net [195.
71.251.74]
10 57 ms 59 ms 56 ms xmwc-lond-uk01-chan-1-0.nw.mediaways.net [195.71
.254.130]
11 52 ms 52 ms 51 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
12 58 ms 58 ms 58 ms ae3.scr4.LON3.gblx.net [67.17.111.142]
13 60 ms 59 ms 59 ms ae4-30G.scr4.FRA4.gblx.net [67.16.146.14]
14 168 ms 68 ms 59 ms lag2.ar4.fra4.gblx.net [67.16.145.242]
15 52 ms 50 ms 49 ms internap.ethernet20-3.ar4.fra4.gblx.net [64.209.
103.178]

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2ND: INGAME

Routenverfolgung zu 95.172.65.76 über maximal 30 Abschnitte

1 * * * Zeitüberschreitung der Anforderung.
2 * * * Zeitüberschreitung der Anforderung.
3 * 2817 ms * ae1-102.cr02.str.de.hansenet.net [213.191.88.226
]

4 163 ms * * ge-5-1-0-0.cr02.ber.de.hansenet.net [213.191.66.
233]
5 * * * Zeitüberschreitung der Anforderung.
6 * * * Zeitüberschreitung der Anforderung.
7 * * * Zeitüberschreitung der Anforderung.
8 * * * Zeitüberschreitung der Anforderung.
9 621 ms * 507 ms rmwc-hmbg-de04-xe-0-0-1-0.nw.mediaways.net [195.
71.251.74]

10 59 ms 57 ms 62 ms xmwc-lond-uk01-chan-1-0.nw.mediaways.net [195.71
.254.130]
11 53 ms 52 ms 53 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
12 58 ms 59 ms 57 ms ae3.scr4.LON3.gblx.net [67.17.111.142]
13 58 ms 59 ms 60 ms ae4-30G.scr4.FRA4.gblx.net [67.16.146.14]
14 58 ms 64 ms 58 ms lag2.ar4.fra4.gblx.net [67.16.145.242]
15 47 ms 49 ms 142 ms internap.ethernet20-3.ar4.fra4.gblx.net [64.209.
103.178]
16 * * * Zeitüberschreitung der Anforderung.
17 * *
------------------------------------------------------------------------------------------------------------------------------------------------------------------------

3RD: INGAME


Routenverfolgung zu 95.172.65.76 über maximal 30 Abschnitte

1 4 ms 2 ms 4 ms alice.box [192.168.1.1]
2 21 ms 19 ms 18 ms lo1.br10.kae.de.hansenet.net [213.191.89.42]
3 21 ms 38 ms 70 ms ae1-102.cr02.str.de.hansenet.net [213.191.88.226
]
4 37 ms 38 ms 37 ms ge-5-1-0-0.cr02.ber.de.hansenet.net [213.191.66.
233]
5 43 ms 40 ms 37 ms so-0-0-0-0.cr01.asham.de.hansenet.net [213.191.6
6.17]
6 49 ms 42 ms 42 ms ae0-0.xd02.asham.de.hansenet.net [62.109.67.2]
7 42 ms 42 ms 42 ms ae1-0.pr01.asham.de.hansenet.net [213.191.66.154
]
8 40 ms 36 ms 37 ms rmwc-hmbg-de03-chan-0-0.nw.mediaways.net [213.20
.88.202]
9 44 ms 43 ms 44 ms rmwc-hmbg-de04-xe-0-0-0-0.nw.mediaways.net [62.5
3.171.14]
10 57 ms 59 ms 57 ms xmwc-lond-uk01-chan-1-0.nw.mediaways.net [195.71
.254.130]
11 52 ms 51 ms 54 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
12 69 ms 76 ms 70 ms ae3.scr4.LON3.gblx.net [67.17.111.142]
13 66 ms 153 ms 62 ms ae4-30G.scr4.FRA4.gblx.net [67.16.146.14]
14 184 ms 364 ms 2104 ms lag2.ar4.fra4.gblx.net [67.16.145.242]
15 319 ms 523 ms 110 ms internap.ethernet20-3.ar4.fra4.gblx.net [64.209.
103.178]

16 * * * Zeitüberschreitung der Anforderung.
17 * *


Comment below rating threshold, click here to show it.

PoldiS

Junior Member

02-12-2013

Hey
here's the tracert report, altough I must say I couldn't start tracking right when the problem showed up, because it lasts few seconds... hope it helps

C:\Windows\system32>tracert 95.172.65.76

Traccia instradamento verso 95.172.65.76 su un massimo di 30 punti di passaggio

1 4 ms <1 ms <1 ms alicegate.homenet.telecomitalia.it [192.168.1.1]

2 * * * Richiesta scaduta.
3 8 ms 9 ms 9 ms 172.17.65.65
4 10 ms 18 ms 25 ms 172.17.9.205
5 21 ms 20 ms 19 ms 172.17.8.93
6 22 ms 23 ms 22 ms 172.17.10.89
7 25 ms 21 ms 23 ms bundle-ether11.milano26.mil.seabone.net [93.186.
128.201]
8 41 ms 43 ms 41 ms xe-11-1-0.franco31.fra.seabone.net [89.221.34.18
3]
9 54 ms 92 ms 53 ms global-crossing.franco31.fra.seabone.net [89.221
.34.110]
10 54 ms 53 ms 52 ms xe2-1-0-10G.scr3.FRA4.gblx.net [67.16.146.38]
11 40 ms 47 ms 40 ms lag1.ar4.fra4.gblx.net [67.16.145.238]
12 41 ms 55 ms 60 ms internap.ethernet20-3.ar4.fra4.gblx.net [64.209.
103.178]
13 * * * Richiesta scaduta.
14 * * * Richiesta scaduta.
15 * * * Richiesta scaduta.
16 * * * Richiesta scaduta.
17 * * * Richiesta scaduta.
18 * * * Richiesta scaduta.
19 * * * Richiesta scaduta.
20 * * * Richiesta scaduta.
21 * * * Richiesta scaduta.
22 * * * Richiesta scaduta.
23 * * * Richiesta scaduta.
24 * * * Richiesta scaduta.
25 * * * Richiesta scaduta.
26 * * * Richiesta scaduta.
27 * * * Richiesta scaduta.
28 * * * Richiesta scaduta.
29 * * * Richiesta scaduta.
30 * * * Richiesta scaduta.

Traccia completata.


Comment below rating threshold, click here to show it.

PoldiS

Junior Member

02-13-2013

bump ^^


Comment below rating threshold, click here to show it.

layas diary

Member

02-14-2013

My traceroute looks exactly the same like the one from PoldiS. On the second is a hop and from 13 to 30 no answer. What is the problem? My provider? My router-settings? Or could a be a problem ensuing from riot?


Comment below rating threshold, click here to show it.

Brazorrr

Junior Member

02-14-2013

Exactly the same problem .. really annoys me
Btw when i use that command, i only get the "not recognised command" error, help?!


Comment below rating threshold, click here to show it.

PoldiS

Junior Member

02-16-2013

Bump
p.s.: for those of you who haven't tried yet, I was told to change my DNS servers, still didn't work for me


Comment below rating threshold, click here to show it.

LemonKushGG

Junior Member

02-16-2013

I have been having the same issue but sometimes it will "attempt to reconnect" for up to 3 mins when I get back I've either been killed or back and base and all my team are hating on me.

I have complained to my ISP (BT) and they have checked everything and it's all fine. I also cannot give you the requested information because I am on Windows 8.

This issue has to be Riot side because I have ran speed tests when I'm lagging in game and I get 30 to 40 ping not the 400+ the game is giving me.


Comment below rating threshold, click here to show it.

FireShark30

Junior Member

02-16-2013

Hi, same here. CPU E8200 @ 2.66 Ghz GPU: 9600 GT
My trace also stops after "internap", maybe something is wrong there?
I also discovered that my +12V rail only delivers +11.15 V which is bad, but it seems unlikely that this also is causing the problems since so many people are having them. I've only had this problem for a little over a week.

C:\Users\>tracert 95.172.65.76

Traceren van de route naar 95.172.65.76 via maximaal 30 hops

1 <1 ms <1 ms <1 ms router.home [192.168.1.254]
2 73 ms 34 ms 35 ms 82-170-255-254.ip.telfort.nl [82.170.255.254]
3 53 ms 44 ms 47 ms nl-asd-dc2-ice-ir01.kpn.net [193.172.66.189]
4 51 ms 45 ms 47 ms nl-rt-dc2-ice-ir01.kpn.net [139.156.222.69]
5 38 ms 44 ms 38 ms ge-3-1-8.ams11.ip.tiscali.net [193.172.66.238]
6 49 ms 52 ms 49 ms xe-10-1-0.fra23.ip4.tinet.net [141.136.111.253]

7 49 ms 48 ms 48 ms internap-gw.ip4.tinet.net [77.67.73.166]
8 * * * Time-out bij opdracht.
9 * * * Time-out bij opdracht.
10 * * * Time-out bij opdracht.
11 * * * Time-out bij opdracht.
12 * * * Time-out bij opdracht.
13 * * * Time-out bij opdracht.
14 * * * Time-out bij opdracht.
15 * * * Time-out bij opdracht.
16 * * * Time-out bij opdracht.
17 * * * Time-out bij opdracht.
18 * * * Time-out bij opdracht.
19 * * * Time-out bij opdracht.
20 * * * Time-out bij opdracht.
21 * * * Time-out bij opdracht.
22 * * * Time-out bij opdracht.
23 * * * Time-out bij opdracht.
24 * * * Time-out bij opdracht.
25 * * * Time-out bij opdracht.
26 * * * Time-out bij opdracht.
27 * * * Time-out bij opdracht.
28 * * * Time-out bij opdracht.
29 * * * Time-out bij opdracht.
30 * * * Time-out bij opdracht.

De trace is voltooid.


Comment below rating threshold, click here to show it.

PoldiS

Junior Member

02-17-2013

Bump :'(