Same issue here with very slow uploads on all devices in the house. As with others, I've done the optimization, reset the router, reset the ONT, reset DHCP, turned WMM/QoS on and off, and even tried different FIOS Routers and via ethernet cable. All the same -- slow, slow upload speed and timing out for any upload greater than about 750kb. Verizon phone customer service tried all the basic things--line checks, remote ONT reset, and about a bizzilion speed checks, with no success. So today a Verizon Tech came to the house and manually reset everything, checked the household wiring, and then called his upper echelon support.
At first they said they didn't see a problem--all the lines seemed ok. But the Tech at my house could not upload anything bigger than 1mb on his own devices. So they thought maybe it might be something called a "bad pong" (this, I take it is a network card of some form up at the central office). But reseting the pong did not work. The upstream tech could indeed see that packet loss on the upload was high, but did not know why. So they decided to do something they call "kick the "key key"" (maybe "kick the kiki"?). Even the Verizon tech at my house did not know what a "ki ki" is or where such a device might be found. But, apparently, kicking the ki ki is something that can only be done during the nightime hours.
So here I sit, hoping that this ki ki kick works. If not, I have no clue.
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [261360]
running 10s outbound test (client to server) . . . . . 1.55Mb/s
running 10s inbound test (server to client) . . . . . . 57.26Mb/s
------ Client System Details ------
OS data: Name = Windows 7, Architecture = x86, Version = 6.1
Java data: Vendor = Oracle Corporation, Version = 1.7.0_21
------ Web100 Detailed Analysis ------
Client Receive Window detected at 261360 bytes.
10 Mbps Ethernet link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 30.2 msec; the Packet size = 1452 Bytes; and
There were 75 packets retransmitted, 1480 duplicate acks received, and 954 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 7.09% of the time.
This connection is sender limited 86.28% of the time.
This connection is network limited 6.63% 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