LoL Lag

Comment below rating threshold, click here to show it.

DockTourMoonDoe

Junior Member

09-26-2011

Hi guys I have suddenly started having really bad lag problems in LoL. I have never before had these problems, and then all of the sudden I have started having lag so bad that I cant move my character. What I read from other people is that they used Netalyzer scans to figure out problems, but I dont know what any of it means or how to ifx it, so I am going to post the results on here and hopefully someone can help me. I really want to play dominion, but I know that the lag could ruin my team's chances of winning, so please help!




The ICSI Netalyzr


Start Analysis Results


Result Summary
+/– (help)
c-24-20-71-157.hsd1.or.comcast.net / 24.20.71.157
Recorded at 16:21 EDT (20:21 UTC), Sep 26 2011. Permalink. Referrer. Client/server transcript.

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


Summary of Noteworthy Events –


Major Abnormalities

•Your DNS resolver returns IP addresses for names that do not exist

Minor Aberrations

•Certain TCP protocols are blocked in outbound traffic
•Network packet buffering may be excessive
•Virus filtering appears to be present on your host or network
•Not all DNS types were correctly processed
•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

Basic UDP access is available.
The applet was able to send fragmented UDP traffic.

The applet was able to receive fragmented UDP traffic.

Direct UDP access to remote DNS servers (port 53) is allowed.

Direct UDP access to remote NTP servers (port 123) is allowed.

Direct UDP access to remote NetBIOS NS servers (port 137) is blocked.

Direct UDP access to remote NetBIOS DGM servers (port 138) is blocked.

Direct UDP access to remote IKE key exchange servers (port 500) is allowed.

Direct UDP access to remote OpenVPN servers (port 1194) is allowed.

Direct UDP access to remote Slammer servers (port 1434) is allowed.

Direct UDP access to remote L2 tunneling servers (port 1701) is allowed.

Direct UDP access to remote IPSec NAT servers (port 4500) is allowed.

Direct UDP access to remote RTP servers (port 5004) is allowed.

Direct UDP access to remote RTCP servers (port 5005) is allowed.

Direct UDP access to remote SIP servers (port 5060) is allowed.

Direct UDP access to remote VoIP servers (port 7078) is allowed.

Direct UDP access to remote VoIP servers (port 7082) is allowed.

Direct UDP access to remote SCTP servers (port 9899) is allowed.

Direct UDP access to remote Steam gaming servers (port 27005) is allowed.

Direct UDP access to remote Steam gaming servers (port 27015) is allowed.

Traceroute (?): OK


It takes 21 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
1.10.209.112.3 (0 ms)
2.ip-10-1-14-13.ec2.internal (0 ms)
3.ip-10-1-2-138.ec2.internal (0 ms)
4.216.182.232.66 (0 ms)
5.216.182.232.50 (0 ms)
6.72.21.220.224 (0 ms)
7.72.21.220.132 (2 ms)
8.72.21.220.148 (1 ms)
9.vlan90.csw4.Washington1.Level3.net (1 ms)
10.ae-91-91.ebr1.Washington1.Level3.net (1 ms)
11.ae-81-81.ebr1.Washington1.Level3.net (1 ms)
12.*
13.*
14.COMCAST-IP.edge2.Washington12.Level3.net (3 ms)
15.pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net (37 ms)
16.pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net (38 ms)
17.pos-0-11-0-0-cr01.seattle.wa.ibone.comcast.net (74 ms)
18.so-6-1-0-0-ar03.troutdale.or.bverton.comcast.net (78 ms)
19.so-6-1-0-0-ar03.troutdale.or.bverton.comcast.net (79 ms)
20.ge-4-1-0-ten19.beaverton.or.bverton.comcast.net (88 ms)
21.c-24-20-71-157.hsd1.or.comcast.net (96 ms)

Path MTU (?): OK

The path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1500 bytes.

Network Access Link Properties –

Network latency measurements (?): Latency: 99ms Loss: 0.0%

The round-trip time (RTT) between your computer and our server is 99 msec, which is good.

We recorded no packet loss between your system and our server.

TCP connection setup latency (?): 100ms

The time it takes your computer to set up a TCP connection with our server is 100 msec, which is good.

Network background health measurement (?): no transient outages

During most of Netalyzr's execution, the applet continuously measures the state of the network in the background, looking for short outages. During testing, the applet observed no such outages.

Network bandwidth measurements (?): Upload 3.6 Mbit/sec, Download 5.2 Mbit/sec

Your Uplink: We measured your uplink's sending bandwidth at 3.6 Mbit/sec. This level of bandwidth works well for many users.

Your Downlink: We measured your downlink's receiving bandwidth at 5.2 Mbit/sec. This level of bandwidth works well for many users.
During this test, the applet observed 10 reordered packets.

Network buffer measurements (?): Uplink 530 ms, Downlink 630 ms

We estimate your uplink as having 530 msec 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 630 msec 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 downloads. Real-time applications, such as games or audio chat, may also work poorly when conducting large downloads at the same time.

HTTP Tests –

Address-based HTTP proxy detection (?): OK

We detected no explicit sign of HTTP proxy via IP address changes.

Content-based HTTP proxy detection (?): OK

No HTTP header or content changes hint at the presence of a proxy.

HTTP proxy detection via malformed requests (?): OK

Deliberately malformed HTTP requests arrive at our server unchanged. We are not able to detect a proxy along the path to our server using this method.

Filetype-based filtering (?): Note

Files of type exe remain unmodified by the network.

Files of type mp3 remain unmodified by the network.

Files of type torrent remain unmodified by the network.

A test "virus" (the benign EICAR test file that antivirus vendors recognize as a test) was blocked or modified in transit.

HTTP caching behavior (?): OK

We detected no signs of a transparent HTTP cache in your network path.

JavaScript-based tests (?): OK

The applet did not execute within a frame.

Your web browser reports the following cookies for our web page: •netAlizEd = BaR (set by our server)
•netalyzrStatus = running (set by our server)

Your web browser was unable to fetch an image using IPv6.

DNS Tests –


Restricted domain DNS lookup (?): OK

We can successfully look up a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.

Unrestricted domain DNS lookup (?): OK

We can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.

Direct DNS support (?): OK

All tested DNS types were received OK.

Direct EDNS support (?): OK

EDNS-enabled requests for small responses are answered successfully.

EDNS-enabled requests for medium-sized responses are answered successfully.

EDNS-enabled requests for large responses are answered successfully.

DNS resolver address (?): OK

The IP address of your ISP's DNS Resolver is 76.96.94.73, which resolves to bvrt-cns04b.beaverton.or.bverton.comcast.net. Additional nameservers observed for your host: 68.87.69.147, 76.96.94.70.

DNS resolver properties (?): Lookup latency 40ms

Your ISP's DNS resolver requires 40 msec to conduct an external lookup. It takes 26 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 does not use EDNS.

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 (?)

Your system is configured to use 1 DNS resolver(s).

The resolver at 192.168.1.1 was unable to process the following tested types:•Medium (~1300B) TXT records
•Large (~3000B) TXT records
•Large (~3000B) TXT records fetched with EDNS0
It does not validate DNSSEC. It wildcards NXDOMAIN errors. Instead of an error it returns the following IP address(es): 208.68.143.50. The resolver reports the following properties:• Version: dnsmasq-2.39
• Authors: Simon Kelley
• Copyright: Copyright (C) 2000-2007 Simon Kelley

DNS glue policy (?): OK

Your ISP's DNS resolver does not accept generic additional (glue) records — good.

Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers.

Your ISP's DNS resolver does not follow CNAMEs.

DNS resolver port randomization (?): OK

Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.

DNS lookups of popular domains (?): OK

90 of 90 popular names were resolved successfully. Show all names.

12 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

Your host ignores external DNS requests.

DNS results wildcarding (?): Warning


Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 208.68.143.50, which does not resolve. You can inspect the resulting HTML content here.

There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer's typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.

The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.

The following lists your DNS server's behavior in more detail.
•www.{random}.com is mapped to 208.68.143.50.
•www.{random}.org is mapped to 208.68.143.50.
•fubar.{random}.com is correctly reported as an error.
www.yahoo.cmo [sic] is mapped to 208.68.143.50.
•nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 208.68.143.50.

DNS-level redirection of specific sites (?): OK

Your ISP does not appear to be using DNS to redirect traffic for specific websites.

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 14 seconds slow.

Browser properties (?): OK

Your web browser sends the following parameters to all web sites you visit:•User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
•Accept: text/html, application/xhtml+xml, */*
•Accept Language: en-US
•Accept Encoding: gzip, deflate
•Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Java identifies your operating system as Windows 7.
Uploaded data (?): OK

The applet uploaded the following additional content: •apache_404
•custom_404
•nxpage
•plain_404
•raw_http_content
•upnp_0_descr
•upnp_0_details

Thanks,
A sad summoner


Comment below rating threshold, click here to show it.

Cyborg5

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

Senior Member

09-26-2011

Its saying that your internet is fine, but your hardware might be up to date. I would also check firewalls. The first things in the post are the important things, and the Major Abberation=Major Problem. Im not sure what it means, but it is an internet problem.


Comment below rating threshold, click here to show it.

NoradIV

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

Member

09-26-2011

Quote:
Originally Posted by Cyborg5 View Post
Its saying that your internet is fine, but your hardware might be up to date. I would also check firewalls. The first things in the post are the important things, and the Major Abberation=Major Problem. Im not sure what it means, but it is an internet problem.
+1

This is true, the main things that it says is if you do some heavy download, your performance will be severely degraded.

The "Major Abnormalities " thing is in fact a custom page that your isp show you when you enter an non-existing page. This is nothing wrong.

Althought, take a time to consider that RIOT recently added Dominion in their servers. I experienced some lag too from their servers (everybody lagged at the same time). This is possibly not you who is causing your lag.

If you're still lagging, consider looking if someone else in your house is downloading, of you have some software that you don't remember who is downloading, or running a virus scan that may be using your bandwidth.

If everything goes well, well its probably just RIOT who is screwing you.

Good luck!


Comment below rating threshold, click here to show it.

DockTourMoonDoe

Junior Member

09-28-2011

The thing is, its not just lag. My whole interhet just dies on me. My skype dies, my game disconects, and my internet completely stops working. Now it could be that Riot is screwing with me, but I was just hoping it was a fixable problem because its gotten me killed quite a few times.


Comment below rating threshold, click here to show it.

GetWr3cked

Senior Member

09-28-2011

"We estimate your uplink as having 530 msec 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 630 msec 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 downloads. Real-time applications, such as games or audio chat, may also work poorly when conducting large downloads at the same time."

Everyone who is having this problem is having this said almost exactly.
My suggestion to you is if you are using Wireless, direct connect using Ethernet connection, shut off all "wifi" options on all your other devices such as phones, ipods, ipads.

Your bandwidth is being stretched for some reason, mine wasn't uploading fast enough from time to time, this fixed it.


Comment below rating threshold, click here to show it.

FiNhOFoLiA

Junior Member

09-28-2011

test for Package Loss on www.pingtest.net