Chronic Latency Spikes

Comment below rating threshold, click here to show it.

MaelstromM

This user has referred a friend to League of Legends, click for more information

Member

11-12-2012

For some time now (6 months or more), I have been experiencing terrible in-game lag spikes. The latency meter will jump from my standard 70-90 to 250-300 or more, stay this way for 2-3 seconds, then slowly drop back to normal over 2-3 seconds. The affect is noticeable while playing and my micro'ing is suffering for it. I have followed all directives in the Wrenchman's Toolbox, and am at a loss as to what is causing the problem.

I am also attaching a ping and tracert to leagueoflegends.com, which shows missed packets and substantial timeout.

Quote:
Summary of Noteworthy Events + –
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive
The NAT's DNS proxy doesn't fully implement the DNS standard
We received unexpected and possibly dangerous results when looking up important names
Your computer's clock is slightly slow
Address-based Tests + –
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Yes +
Reachability Tests + –
TCP connectivity (?): Note –
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): OK +
Traceroute (?): OK +
Path MTU (?): OK +
Network Access Link Properties + –
Network latency measurements (?): Latency: 34ms Loss: 0.0% +
TCP connection setup latency (?): 45ms +
Network background health measurement (?): no transient outages +
Network bandwidth (?): Upload 960 Kbit/sec, Download 9.8 Mbit/sec +
Network buffer measurements (?): Uplink 1700 ms, Downlink 2100 ms –
We estimate your uplink as having 1700 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.
We estimate your downlink as having 2100 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.
HTTP Tests + –
Address-based HTTP proxy detection (?): OK +
Content-based HTTP proxy detection (?): OK +
HTTP proxy detection via malformed requests (?): OK +
Filetype-based filtering (?): OK +
HTTP caching behavior (?): OK +
JavaScript-based tests (?): OK +
DNS Tests + –
Restricted domain DNS lookup (?): OK +
Unrestricted domain DNS lookup (?): OK +
Direct DNS support (?): OK +
Direct EDNS support (?): OK +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 88ms –
Your ISP's DNS resolver requires 88 msec to conduct an external lookup. It takes 73 msec for your ISP's DNS resolver to lookup a name on our server.
Your resolver correctly uses TCP requests when necessary.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver requests DNSSEC records.
Your DNS resolver advertises the ability to accept DNS packets of up to 4096 bytes.
Your DNS resolver can successfully receive a smaller (~1400 byte) DNS response.
Your DNS resolver can successfully receive a large (>1500 byte) DNS response.
Your DNS resolver can successfully accept large responses.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.
Your ISP's DNS server cannot use IPv6.
No transport problems were discovered which could affect the deployment of DNSSEC.
Direct probing of DNS resolvers (?): +
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): Warning –
One popular name has a moderate anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server, although we expected to find a name. This is most likely due to a slow responding DNS server. If you rerun Netalyzr and see this condition remain, it could be due to a misconfiguration on the part of the domain owner, deliberate blocking using DNS, or your DNS server could be misconfigured or enabling a Man-in-the-Middle attack.
Name IP Address Reverse Name/SOA
us.etrade.com 12.153.224.21 X
90 of 90 popular names were resolved successfully. Show all names.
20 popular names have a mild anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. The most likely cause is the site's use of a Content Delivery Network. Show all names.
2 popular names have a mild anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server. This is most likely due to a slow responding DNS server or misconfiguration on the part of the domain owner. Show all names.
DNS external proxy (?): OK +
DNS results wildcarding (?): OK +
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?): +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Host Properties + –
System clock accuracy (?): Warning –
Your computer's clock is 9 seconds slow.
Browser properties (?): OK +
Uploaded data (?): OK
Quote:
Pinging leagueoflegends.com [50.17.229.30] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 50.17.229.30:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
Control-C
^C
C:\Users\JandH>tracert leagueoflegends.com

Tracing route to leagueoflegends.com [50.17.229.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 28 ms 21 ms 19 ms 74-128-144-1.dhcp.insightbb.com [74.128.144.1]
3 11 ms 11 ms 11 ms 74-128-45-49.dhcp.insightbb.com [74.128.45.49]
4 9 ms 11 ms 9 ms 74.128.9.237
5 21 ms 20 ms 19 ms xe-4-3-3.edge5.Atlanta2.Level3.net [4.59.12.61]

6 22 ms 20 ms 23 ms vlan52.ebr2.Atlanta2.Level3.net [4.69.150.126]
7 22 ms 20 ms 20 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]

8 33 ms 34 ms 32 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

9 40 ms 34 ms 39 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.1
42]
10 34 ms 34 ms 35 ms ae-4-90.edge1.Washington1.Level3.net [4.69.149.2
05]
11 34 ms 32 ms 32 ms AMAZON.COM.edge1.Washington1.Level3.net [4.28.12
5.110]
12 33 ms 35 ms 35 ms 72.21.220.143
13 34 ms 34 ms 34 ms 205.251.245.53
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 32 ms 33 ms 33 ms 216.182.224.85
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 ^C


Comment below rating threshold, click here to show it.

DN Caibre

Senior Member

11-12-2012

Same issue here


Comment below rating threshold, click here to show it.

Sujing

This user has referred a friend to League of Legends, click for more information

Senior Member

11-13-2012

Yep, I've just recently been struck with high ping spikes. Only some games, however.


Comment below rating threshold, click here to show it.

MaelstromM

This user has referred a friend to League of Legends, click for more information

Member

11-16-2012

Bumping. Still getting latency spikes as described above!


Comment below rating threshold, click here to show it.

MaelstromM

This user has referred a friend to League of Legends, click for more information

Member

11-19-2012

Bumpage...


Comment below rating threshold, click here to show it.

MaelstromM

This user has referred a friend to League of Legends, click for more information

Member

12-19-2012

This is getting really old. The problem settled down for a bit, and now is back in full force and seems to be getting worse. A month old topic and not a single suggestion for a fix, no additional questions nor troubleshooting? I just want to play League without my ping bouncing over 200ms spikes whenever it feels like it!


Comment below rating threshold, click here to show it.

MaelstromM

This user has referred a friend to League of Legends, click for more information

Member

12-19-2012

Just had a game that was literally unplayable. From the load screen my latency was fine, 30 seconds into the match it started again. Just got off the phone with the ISP, again, and they tell me there is nothing they can do. I found a number for Riot that I can contact, but I'm sure they would prefer to handle it via forum or e-mail.


Comment below rating threshold, click here to show it.

MaelstromM

This user has referred a friend to League of Legends, click for more information

Member

12-23-2012

Yet again, unable to play League of Legends..


Comment below rating threshold, click here to show it.

Dark Kuno

Senior Member

12-23-2012

Mine are worse. will go from 90 up to 700

totally random and LoL is the only application experiencing this

making the game completely unplayable