Rowland Heights, CA
reply to andyjai
Re: Problem with Fios I swap to the refurbished Actiontec Rev I that I got from Verizon today and it gave me another IP, but the problem still exist.
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to 
running 10s outbound test (client to server) . . . . . 246.95Kb/s
running 10s inbound test (server to client) . . . . . . 21.23kb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_11
------ Web100 Detailed Analysis ------
Client Receive Window detected at 66560 bytes.
Link detection algorithm failed due to excessive Round Trip Times.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 0 msec; the Packet size = 1452 Bytes; and
There were 28 packets retransmitted, 10 duplicate acks received, and 21 SACK blocks received
The connection stalled 3 times due to packet loss
The connection was idle 0 seconds (Na%) of the time
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Speedtest.net Los Angeles
Atlantic Metro 17ms 33.21Down 24.45Up
DreamHost 11ms 38.63Down 30.07Up
Internode 17ms Test stuck on connecting
Race Comm. 21ms Test stuck on connecting
Centurylink.net (San Jose) 35ms 55.58Up 32.54Down
Speakeasy.net Test Fail
Now is 6pm and I will expect even worse speed after dinner.