The strange bit is here, those are some rather clean traces and fast ping graphs. There's some spikes here in the traceroute you ran outbound, but there isn't packet loss or high latency showing up in this case. Almost looks as if there isn't congestion to begin with circuit-wise. What I do notice however is the increase in round trip time. NDT measures this while transfers are in session, and during congested times this can be higher.
Considering the NDT test was ran on-network, the receive window for a Windows 7 machine should be lower (basically where it is), due to lesser latency and a smaller window only being needed to achieve the data rate. If you test off-peak hours, that should prove to be higher. Windows 7 Dynamically adjusts this based on latency and based on the connection capacity to deliver data reliably.
I'd like to check one final thing though on your computer before getting you to Verizon. Hope you'll bear with me here. Go to Start > use the Search box to find the program called "cmd.exe" and open it. In the Command Prompt, run the following command for me:
netsh int tcp show global
When you press Enter, it should give you some readout. Right click on the Window and choose "Mark." From here, highlight the readout of the command, and then press Enter on your keyboard to copy the results. Paste the results into this window for us. If those check out, we'll look at things from Verizon's end.
Some food for thought from a 5Mbps line on Verizon (I do throttle uploads due to high bandwidth usage here, and test was ran while two PCs were running online games):
Analysis information:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [8192]
running 10s outbound test (client to server) . . . . . 396.00Kb/s
running 10s inbound test (server to client) . . . . . . 4.40Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_17
------ Web100 Detailed Analysis ------
Client Receive Window detected at 134144 bytes.
Cable modem/DSL/T1 link found.
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 = 177.37 msec; the Packet size = 1452 Bytes; and
No packet loss - but packets arrived out-of-order 0.13% of the time
This connection is receiver limited 57.29% of the time.
This connection is sender limited 41.38% of the time.
This connection is network limited 1.32% 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
Server says [71.186.xxx.xxx] but Client says [10.x.x.x]
