For years, I have used »
speedtest.insight.rr.com/ as my ONLY speed test. Not for the server location, ui, speed of testing, or anything else. It was solely for the DETAILS the test provided. I have never seen any other speedtest come close, other than a few DOS text diagnostic tools during the 2400 or 9600 baud days.
It appears that the speed test might be down/dead. This speedtest helped me win a fight with timewarner over peaktime congestion, here on the direct forum. It left them with NO excuses, and expedited the area's docsis 3.0 upgrade. This test helped not only my connection, but also that of my neighbors and friends. So there is an odd personal connection as well. (A very funny and ironic situation happened to me with a tech during that ordeal, it's at the bottom of this post to stay on topic, PLEASE continue reading though)
I know TWC bought out insight and that could be the reason, and that is why I am hoping to find the test on another local's mirror! My last use was Feb 8th 2013 and this is my first time checking since. Down or me reports down, as well as different DNS servers having no luck.
At the bottom of this post, I will include my latest test verbatim. This is to give you an idea of the extensiveness and usefulness of the test. It literally helped me diagnose and fix hundreds of connections over the years, including my own. I
sincerely hope that this speedtest was mirror'd on another rr's local website.
PLEASE check your local RR website, and see if you have a test similar to the one I am describing.
These subdomains are acting very weird. rr.com goes to roadrunners website like normal. insight.rr.com redirects to a coupons.com website. speedtest.insight.rr.com gives me a 103 error.
Quick details: It was Java app located on two urls: »
speedtest.insight.rr.com/ and »
speedtest.insight.rr.com ··· ced.htmlMy last test:
WEB100 Enabled Statistics:
------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_07
------ Web100 Detailed Analysis ------
100 Mbps FastEthernet link found.
Link set to Full Duplex mode
Good network cable(s) found
Web100 reports the Round trip time = 88.34 msec; the Packet size = 1460 Bytes; and
No packet loss - but packets arrived out-of-order 0.06% of the time
This connection is sender limited 86.8% of the time.
This connection is network limited 13.20% of the time.
The following TCP settings were detected:
TCP Receive Window (RWIN): 456976 bytes
Selective ACKs: ON
Nagle Algorithm: ON
Explicit Congestion Notification: OFF
Time Stamping: OFF
Window Scaling: ON
------ Potential Bottlenecks ------
The theoretical network limit is 126.1 Mbps
The NDT server has a 1024.0 KByte buffer which limits the throughput to 90.56 Mbps
Your PC/Workstation has a 446.0 KByte buffer which limits the throughput to 39.46 Mbps
The network based flow control limits the throughput to 34.55 Mbps
Client Data reports link is 'FastE', Client Acks report link is 'Ethernet'
Server Data reports link is 'OC-48', Server Acks report link is 'OC-48'
------ Routing Analysis ------
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [184.57.82.163] but Client says [192.168.0.11]
(Quick funny story: The fourth and final tech TWC sent out to my house when I was fighting them literally lived seven houses down the street. He admitted to me he had the same problem I did, and there was nothing he could do other than check the wiring (Which was done the three times prior). He complained to me that he couldn't watch a youtube video without frustration due to the 5-20% packetloss and 1.5-5mb speeds during peak. We were both on docsis 2.0 15/1 "turbo/boost" plans at the time. We shared quite a good laugh at the situation, and he truly wished me the best of luck making a stink to corporate represenative)
(Extended TWC fight details/another funny story: Took 42 days from the initial post in the direct forum to a real fix. Told that two supposed "fixes" happened during that time period. Each did literally nothing.
Had my trouble ticket get created by TWC direct, then found out from them that it was closed without their knowledge. Granted, this happened six days before the fix, but still they only checked because I held them accountable. Eleven traceroutes, twenty-three speedtests, and fourteen line monitors originating from four different servers is what it took.)
However I must say TWC direct did the best job they could, and that's why I am still with them as an isp. I will also ask them about the status of this speedtest in the direct forum, and respond with the results when/if I get them.
A HUGE thank you in advance. Best of karma to y'all.