Hi everyone,
I have been getting major lag spikes while playing league of legends and dota 2. The ICSI Netalyzr showed an uplink of 1800ms and a downlink of 130ms.
ICSI Netalyzr results:
The ICSI Netalyzr
Start » Analysis » Results
Result Summary + – (help)
c-98-247-217-46.hsd1.wa.comcast.net / 98.247.217.46
Recorded at 21:23 EDT (01:23 UTC next day), Apr 20 2014. Permalink. Client/server transcript.
Summary of Noteworthy Events + –
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive
Not all DNS types were correctly processed
Only some root servers returned DNSSEC information
Address-based Tests + –
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Not found +
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: 130 ms, Loss: 0.0% +
TCP connection setup latency (?): 130ms +
Background measurement of network health (?): no transient outages +
Network bandwidth (?): Upload 880 Kbit/s, Download 2.9 Mbit/s +
Network buffer measurements (?): Uplink 1800 ms, Downlink 130 ms –
We estimate your uplink as having 1800 ms 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 130 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 54 ms +
Direct probing of DNS resolvers (?) –
Your system is configured to use 2 DNS resolver(s).
The resolver at 75.75.75.75 can process all tested types. Requests from this resolver come from 76.96.94.91. This resolver requries 90 ms to fetch a result from our server and 45 ms to return a result from its cache. It validates DNSSEC. It provides DNSSEC records upon request. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
The resolver at 75.75.76.76 could not process the following tested types:
Medium (~1300B) TXT records
Requests from this resolver come from 76.96.98.28. This resolver requries 184 ms to fetch a result from our server and 188 ms to return a result from its cache. It validates DNSSEC. It provides DNSSEC records upon request. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
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 (?): Note +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Network Security Protocols + –
DNSSEC Support from the DNS Roots (?): Warning –
Only some DNS root server instances returned proper DNSSEC information. The working roots are: A, B, C, E, F, G, H, I, J, K, L, M
Host Properties + –
System clock accuracy (?): OK +
Browser properties (?): OK +
Uploaded data (?): OK +
ID 36ea240d-4027-c5bbd603-9830-4c81-bfd4 FAQs + Blog + Papers + Links + ICSI