In-Game Latency Issues

Comment below rating threshold, click here to show it.

King Drippy

Junior Member

03-22-2013

Heya all. Recently (Nidalee skin patch) I've had issues with ping in-game. I usually sit at a consistent 20-30 ms, but since the patch it's been a constant 150+ spiking to 250+ pretty regularly. I have no idea as to why. Everything else runs perfectly fine with my usually ms etc etc. I have a Netalyzr test and I was wondering if I could get anyone to check it out and let me know what they see (I'm no networking genius). Any help would be greatly appreciated. Thanks in advance.

Summary of Noteworthy Events +
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive
The path between our system and your network does not appear to handle fragmented IPv6 traffic properly
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 prohibited.
This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
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 +
Hidden Proxy Detection (?): OK +

Network Access Link Properties +
Network performance (?): Latency: 64 ms, Loss: 0.0% +
TCP connection setup latency (?): 59ms +
Background measurement of network health (?): no transient outages +
Network bandwidth (?): Upload 710 Kbit/s, Download 5.4 Mbit/s +
Network buffer measurements (?): Uplink 710 ms, Downlink 140 ms
We estimate your uplink as having 710 ms of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. Real-time applications, such as games or audio chat, may also work poorly when conducting large uploads at the same time.
We estimate your downlink as having 140 ms of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.

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 +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 229 ms +
Direct probing of DNS resolvers (?): +
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
DNS results wildcarding (?): OK +
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?): OK +

IPv6 Tests +
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): OK +
IPv6 connectivity (?): OK +
IPv6 TCP connectivity (?): OK +
IPv6 Path MTU (?): Warning
Your system can not send or receive fragmented traffic over IPv6.
The path between your network and our system supports an MTU of at least 1472 bytes. The path between our system and your network has an MTU of 1472 bytes. The bottleneck is at IP address 2602:306:bc33:32f0::1. The path between our system and your network does not appear to handle fragmented IPv6 traffic properly.
IPv6 Traceroute (?): OK +

Network Security Protocols +
DNSSEC Network Transport Tests (?): OK +
DNSSEC Support from the DNS Roots (?): OK +
Host Properties +

System clock accuracy (?): Warning
Your computer's clock is 8 seconds slow.
Browser properties (?): OK +
Uploaded data (?): OK