Welcome to the Forum Archive!

Years of conversation fill a ton 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 the boards to join in the latest League of Legends discussions.

GO TO BOARDS


Possible lag spike culprit?

1
Comment below rating threshold, click here to show it.

hauk2008

Junior Member

12-04-2012

So I've noticed in a quite a few tracert results that the requests always seem to time out right after internap-gw.ip4.tinet.net ... just trying to get more results.. so if anyone is having ping problems recently please open command prompt and type "tracert 95.172.65.76" to see if you also time out at this point in the trace. could help with a solution from riot


Comment below rating threshold, click here to show it.

Illgresi

Member

12-05-2012

Glad you made this thread - I also ran a tracert and got a timeout after reaching an internap domain. The preseason patch has brought me a lot of trouble in terms of ping.


Comment below rating threshold, click here to show it.

hauk2008

Junior Member

12-05-2012

bump :/


Comment below rating threshold, click here to show it.

Elderpriest

Senior Member

12-05-2012

Also timeout at that point 1-16 fine then 17-24 time out.


Comment below rating threshold, click here to show it.

Drake Obsidian

Member

12-05-2012

fine till it hit 212.119.15.6 from me


Comment below rating threshold, click here to show it.

xwaffleman

Junior Member

12-05-2012

Request Timed out, internap-gw.ip4.tinet.net <-- right after that bad boy ;D

http://www.speedtest.net/result/2353748628.png

I do believe I shouldn't lag, haha


1