Hi everyone. Having some trouble with my broadband connection at the moment, its only really started happening this last week or so but i just cant figure it out. Every video i watch on the net regardless of the website insists on buffering ever few seconds and is very slow. The same goes for sky player on the xbox and zune movies on xbox, where before i could always stream hd movies instantly it detects that my connection is just too rubbish to do it now. Ive tried updating the router firmware, and tried a hard reset but it hasnt made much difference. If anyone can shed any light on this very annoying problem i would be very grateful.

« SpeedGuide.net TCP Analyzer Results »
Tested on: 11.04.2011 22:03
IP address: 82.69.xx.xxx
Client OS: Windows 7

TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 65700 (multiple of MSS)
RWIN Scaling: 2 bits (2^2=4)
Unscaled RWIN : 16425
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 2628kbps (329KBytes/s)
BDP limit (500ms): 1051kbps (131KBytes/s)
MTU Discovery: ON
TTL: 116
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)








Summary of Noteworthy Events –


Major Abnormalities

•Your system has an IPv6 address that does not work

Minor Aberrations

•Certain TCP protocols are blocked in outbound traffic
•Network packet buffering may be excessive
•Not all DNS types were correctly processed


Address-based Tests –


NAT detection (?): NAT Detected


Your global IP address is 82.69.60.175 while your local one is 192.168.1.66. You are behind a NAT. Your local address is in unroutable address space.

Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.



The NAT or some other process renumbers TCP ports. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis as seen by our server.



Local Network Interfaces (?): IPv6 Connectivity Problem

Your computer reports the following network interfaces, with the following IP addresses for each one: •eth0: (an ethernet interface)
•eth1: (an ethernet interface)
•eth2: (an ethernet interface)
•eth3: (an ethernet interface)◦fe80::7436:f903:9543:2769 (a link-local IPv6 address)
◦192.168.1.66 [Jeremy-PC.lan] (a private IPv4 address)

•eth4: (an ethernet interface)◦fe80::180:3b7e:7106:5486 (a link-local IPv6 address)

•eth5: (an ethernet interface)
•eth6: (an ethernet interface)
•eth7: (an ethernet interface)
•eth8: (an ethernet interface)
•eth9: (an ethernet interface)
•lo: (a local loopback interface)◦::1 (an IPv6 loopback address)
◦127.0.0.1 (an IPv4 loopback address)

•net0:
•net1:
•net10:
•net11:
•net12:
•net13:
•net14:
•net2:
•net3:
•net4: ◦fe80::2cdf:e1bb:3642:5c0f (a link-local IPv6 address)

•net5:
•net6: ◦fe80::5efe:c0a8:142 (a link-local IPv6 address)

•net7: ◦2001:0:5ef5:79fd:3843:13ef:adba:c350 [Jeremy-PC] (a Teredo IPv6 address)
◦fe80::3843:13ef:adba:c350 [Jeremy-PC] (a link-local IPv6 address)

•net8:
•net9:
•ppp0:
•ppp1:

Your system has an IPv6 address, yet was unable to fetch an image using IPv6. This can cause substantial problems as your web browser or other programs may first attempt to contact hosts using the non-functional IPv6 connection.

DNS-based host information (?): OK

You are not a Tor exit node for HTTP traffic.

You are not listed on any Spamhaus blacklists.

The SORBS DUHL believes you are using a statically assigned IP address.

NAT support for Universal Plug and Play (UPnP) (?): Not found

UPnP broadcasts for NAT devices remained unanswered. Therefore your NAT does not appear to support UPnP, or your computer's firewall is filtering multicast responses.



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 allowed.

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 blocked.

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 13 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.248.108.3 (0 ms)
2.ip-10-1-16-5.ec2.internal (0 ms)
3.ip-10-1-17-14.ec2.internal (0 ms)
4.216.182.224.80 (0 ms)
5.72.21.222.148 (2 ms)
6.72.21.220.28 (1 ms)
7.77.67.108.33 (1 ms)
8.xe-7-1-0.lon10.ip4.tinet.net (80 ms)
9.zen-internet-gw.ip4.tinet.net (80 ms)
10.ge-2-0-0-0.cr2.th-lon.zen.net.uk (79 ms)
11.ge-3-0-0-0.cr1.wh-man.zen.net.uk (84 ms)
12.ge-4-1-200.dsl13.wh-man.zen.net.uk (87 ms)
13.*

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: 98ms Loss: 0.0%

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

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

TCP connection setup latency (?): 110ms

The time it takes your computer to set up a TCP connection with our server is 110 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 380 Kbit/sec, Download 1.8 Mbit/sec

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

Your Downlink: We measured your downlink's receiving bandwidth at 1.8 Mbit/sec. This level of bandwidth works well for many users.

Network buffer measurements (?): Uplink 91 ms, Downlink 819 ms

We estimate your uplink as having 91 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.

We estimate your downlink as having 820 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


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

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 212.23.6.163, which resolves to cache06.dns.zen.co.uk. Additional nameservers observed for your host: 212.23.3.162, 212.23.3.163, 212.23.6.161.

DNS resolver properties (?): Lookup latency 190ms

Your ISP's DNS resolver requires 190 msec to conduct an external lookup. It takes 160 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 (?)

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

The resolver at 192.168.1.254 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 does not wildcard NXDOMAIN errors.
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.



18 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.



3 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 (?): OK

Your ISP correctly leaves non-resolving names untouched.

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 (?): IPv6 Connectivity Problem


IPv6 connectivity (?): No IPv6 Support

Host Properties +



System clock accuracy (?): OK


Browser properties (?): OK


Uploaded data (?): OK