Hi everyone,
I have been having problems with my internet and would really appreciate some advice. My internet has been acting crazy recently where it will be fine for maybe a day or 2, but then i will have days where it will be dropping every 5 minutes, although it seems to be connected and not giving any errors, and my browser will just sit for ages appearing to try and search for ages with no progress. If i play an online game it will work fine for 20 minutes or so but then i will get disconnected and nothing will happen, yet my internet connection seems to be strong. Its really unpredictable which can be very annoying and i have spoken to my ISP numerous times over the last 2 years and all they want to do is send me a new router, ive tried 4 different ones and this problem keeps occuring. When i do a test i normally get around 20-60 ping, with 3-4 Mbps and an impressive 0.3 Mbps upload! (im with BT), and that is my performance at best. Thank you for taking the time to read this and I am grateful for any insight.
Posted is a diagnostic i did using Netalyzr:
Major Abnormalities
Your ISP's DNS server is slow to lookup names
Your DNS resolver returns IP addresses for names that do not exist
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
Certain UDP protocols are blocked in outbound traffic
The network indicated bursts of packet loss
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 connections to remote FTP servers (port 21) failed.
This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.
Direct TCP access to remote SSH servers (port 22) is blocked.
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 blocked.
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 blocked.
Direct TCP access to remote SNMP servers (port 161) 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 HTTPS servers (port 443) is blocked.
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 blocked.
Direct TCP access to remote secure IMAP servers (port 585) is blocked.
Direct TCP access to remote authenticated SMTP servers (port 587) is blocked.
Direct TCP access to remote IMAP/SSL servers (port 993) is blocked.
Direct TCP access to remote POP/SSL servers (port 995) is blocked.
Direct TCP access to remote OpenVPN servers (port 1194) is blocked.
Direct TCP access to remote PPTP Control servers (port 1723) is blocked.
Direct TCP access to remote SIP servers (port 5060) is blocked.
Direct TCP access to remote BitTorrent servers (port 6881) is blocked.
Direct TCP access to remote TOR servers (port 9001) is blocked.
UDP connectivity (?): Note
Basic UDP access is available.
The client was able to send fragmented UDP traffic.
The client was able to receive fragmented UDP traffic.
UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy. The client was unable to transmit a non-DNS traffic on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy, NAT, or firewall intercepted and blocked the deliberately invalid request.
Direct UDP access to remote NTP servers (port 123) is blocked.
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 blocked.
Direct UDP access to remote OpenVPN servers (port 1194) is blocked.
Direct UDP access to remote Slammer servers (port 1434) is blocked.
Direct UDP access to remote L2 tunneling servers (port 1701) is blocked.
Direct UDP access to remote IPSec NAT servers (port 4500) is blocked.
Direct UDP access to remote RTP servers (port 5004) is blocked.
Direct UDP access to remote RTCP servers (port 5005) is blocked.
Direct UDP access to remote SIP servers (port 5060) is blocked.
Direct UDP access to remote VoIP servers (port 7078) is blocked.
Direct UDP access to remote VoIP servers (port 7082) is blocked.
Direct UDP access to remote SCTP servers (port 9899) is blocked.
Direct UDP access to remote Steam gaming servers (port 27005) is blocked.
Direct UDP access to remote Steam gaming servers (port 27015) is blocked.
Traceroute (?): Failed to complete +
Path MTU (?): OK +
Hidden Proxy Detection (?): OK +
Network Access Link Properties +
Network performance (?): Network latency could not be measured +
TCP connection setup latency (?): 120ms +
Background measurement of network health (?): 1 transient outages, longest: 76.4 seconds
During most of Netalyzr's execution, the client continuously measures the state of the network in the background, looking for short outages. During testing, the client observed 1 such outages. The longest outage lasted for 76.4 seconds. This suggests a general problem with the network where connectivity is intermittent. This loss might also cause some of Netalyzr's other tests to produce incorrect results.
Network bandwidth (?): Failed to complete +
Network buffer measurements (?): Failed to complete +
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 830 ms
Your ISP's DNS resolver requires 830 ms to conduct an external lookup. It takes 160 ms for your ISP's DNS resolver to lookup a name on our server.
This is particularly slow, and you may see significant performance degradation as a result.
Your resolver correctly uses TCP requests when necessary.
Your resolver is using QTYPE=A for default queries.
Your host or resolver also performs IPv6 queries in addition to IPv4 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 (?): +
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
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 92.242.132.15, which resolves to unallocated.barefruit.co.uk.
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 92.242.132.15.
www.{random}.org is mapped to 92.242.132.15.
fubar.{random}.com is mapped to 92.242.132.15.
www.yahoo.cmo [sic] is mapped to 92.242.132.15.
nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 92.242.132.15.
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 (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Network Security Protocols +
DNSSEC Support from the DNS Roots (?): OK +
Host Properties +
System clock accuracy (?): Warning
Your computer's clock is 10 seconds slow.
Browser properties (?): OK +
Uploaded data (?): OK +
Many thanks
Grandpaonfire
I have been having problems with my internet and would really appreciate some advice. My internet has been acting crazy recently where it will be fine for maybe a day or 2, but then i will have days where it will be dropping every 5 minutes, although it seems to be connected and not giving any errors, and my browser will just sit for ages appearing to try and search for ages with no progress. If i play an online game it will work fine for 20 minutes or so but then i will get disconnected and nothing will happen, yet my internet connection seems to be strong. Its really unpredictable which can be very annoying and i have spoken to my ISP numerous times over the last 2 years and all they want to do is send me a new router, ive tried 4 different ones and this problem keeps occuring. When i do a test i normally get around 20-60 ping, with 3-4 Mbps and an impressive 0.3 Mbps upload! (im with BT), and that is my performance at best. Thank you for taking the time to read this and I am grateful for any insight.
Posted is a diagnostic i did using Netalyzr:
Major Abnormalities
Your ISP's DNS server is slow to lookup names
Your DNS resolver returns IP addresses for names that do not exist
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
Certain UDP protocols are blocked in outbound traffic
The network indicated bursts of packet loss
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 connections to remote FTP servers (port 21) failed.
This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.
Direct TCP access to remote SSH servers (port 22) is blocked.
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 blocked.
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 blocked.
Direct TCP access to remote SNMP servers (port 161) 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 HTTPS servers (port 443) is blocked.
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 blocked.
Direct TCP access to remote secure IMAP servers (port 585) is blocked.
Direct TCP access to remote authenticated SMTP servers (port 587) is blocked.
Direct TCP access to remote IMAP/SSL servers (port 993) is blocked.
Direct TCP access to remote POP/SSL servers (port 995) is blocked.
Direct TCP access to remote OpenVPN servers (port 1194) is blocked.
Direct TCP access to remote PPTP Control servers (port 1723) is blocked.
Direct TCP access to remote SIP servers (port 5060) is blocked.
Direct TCP access to remote BitTorrent servers (port 6881) is blocked.
Direct TCP access to remote TOR servers (port 9001) is blocked.
UDP connectivity (?): Note
Basic UDP access is available.
The client was able to send fragmented UDP traffic.
The client was able to receive fragmented UDP traffic.
UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy. The client was unable to transmit a non-DNS traffic on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy, NAT, or firewall intercepted and blocked the deliberately invalid request.
Direct UDP access to remote NTP servers (port 123) is blocked.
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 blocked.
Direct UDP access to remote OpenVPN servers (port 1194) is blocked.
Direct UDP access to remote Slammer servers (port 1434) is blocked.
Direct UDP access to remote L2 tunneling servers (port 1701) is blocked.
Direct UDP access to remote IPSec NAT servers (port 4500) is blocked.
Direct UDP access to remote RTP servers (port 5004) is blocked.
Direct UDP access to remote RTCP servers (port 5005) is blocked.
Direct UDP access to remote SIP servers (port 5060) is blocked.
Direct UDP access to remote VoIP servers (port 7078) is blocked.
Direct UDP access to remote VoIP servers (port 7082) is blocked.
Direct UDP access to remote SCTP servers (port 9899) is blocked.
Direct UDP access to remote Steam gaming servers (port 27005) is blocked.
Direct UDP access to remote Steam gaming servers (port 27015) is blocked.
Traceroute (?): Failed to complete +
Path MTU (?): OK +
Hidden Proxy Detection (?): OK +
Network Access Link Properties +
Network performance (?): Network latency could not be measured +
TCP connection setup latency (?): 120ms +
Background measurement of network health (?): 1 transient outages, longest: 76.4 seconds
During most of Netalyzr's execution, the client continuously measures the state of the network in the background, looking for short outages. During testing, the client observed 1 such outages. The longest outage lasted for 76.4 seconds. This suggests a general problem with the network where connectivity is intermittent. This loss might also cause some of Netalyzr's other tests to produce incorrect results.
Network bandwidth (?): Failed to complete +
Network buffer measurements (?): Failed to complete +
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 830 ms
Your ISP's DNS resolver requires 830 ms to conduct an external lookup. It takes 160 ms for your ISP's DNS resolver to lookup a name on our server.
This is particularly slow, and you may see significant performance degradation as a result.
Your resolver correctly uses TCP requests when necessary.
Your resolver is using QTYPE=A for default queries.
Your host or resolver also performs IPv6 queries in addition to IPv4 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 (?): +
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
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 92.242.132.15, which resolves to unallocated.barefruit.co.uk.
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 92.242.132.15.
www.{random}.org is mapped to 92.242.132.15.
fubar.{random}.com is mapped to 92.242.132.15.
www.yahoo.cmo [sic] is mapped to 92.242.132.15.
nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 92.242.132.15.
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 (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Network Security Protocols +
DNSSEC Support from the DNS Roots (?): OK +
Host Properties +
System clock accuracy (?): Warning
Your computer's clock is 10 seconds slow.
Browser properties (?): OK +
Uploaded data (?): OK +
Many thanks
Grandpaonfire