Extremely slow and high latency all day.

Question

DSL is running extremely slow during peak hours from 12 afternoon to 12 midnight.   Lower than 50% of rated speed and high latency
I have been frustrated with this DSL Service for months now.  I am considering contacting BBB to file a complaint and I am tired of dealing with customer service giving me the run around.  Internet is a monopoly in my area therefore verizon feels it doesn't have to do anything to keep its customers when they provide crappy service.  I am on waitlist for another internet service provider and it is going to take almost a year because of how bad the internet options are in the area and demand for better options.    I even had to pay over 100 dollars to get a truck roll come to my house to fix any issues within the house and the internet has not gotten better.  Atleast I feel I should get a refund or something.  
Here is my speedtest result just now.  http://www.speedtest.net/my-result/2899553407
It has been even slower at other times. http://www.speedtest.net/my-result/2893509440
Modem is Westell 6100 or something. 
Transceiver Statistics
Transceiver Revision:
7.2.3.0
Vendor ID Code:
4
Line Mode:
G.DMT Mode
Data Path:
Interleaved
Transceiver Information
Downstream Path
Upstream Path
DSL Speed (Kbits/Sec)
3360
864
Margin (dB)
15.5
13.0
Line Attenuation (dB)
21.5
13.0
Transmit Power (dBm)
7.6
11.9
Giganews line info
news.giganews.com
traceroute to {edited for privacy}, 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 ash-bb1-link.telia.net (213.248.70.241) 0 ms 0 ms 0 ms
3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 3 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 3 ms TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 3 ms
4 P1-8-0-0.LSANCA-LCR-21.verizon-gni.net (130.81.151.237) 72 ms 72 ms 72 ms
5 P9-3.LSANCA-LCR-01.verizon-gni.net (130.81.193.123) 75 ms P8-0.LSANCA-DSL-44.verizon-gni.net (130.81.35.133) 75 ms 76 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * Max number of unresponsive hops reached (firewall or filter?)
news-europe.giganews.com
traceroute to {edited for privacy}, 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms
2 te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 0 ms te7-7.ccr01.ams05.atlas.cogentco.com (149.11.104.9) 0 ms te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 0 ms
3 te0-7-0-16.ccr21.ams03.atlas.cogentco.com (154.54.72.42) 0 ms 0 ms 0 ms
4 te0-3-0-0.ccr21.lon13.atlas.cogentco.com (130.117.48.141) 8 ms 8 ms te0-2-0-0.ccr21.lon13.atlas.cogentco.com (154.54.28.158) 8 ms
5 te0-7-0-4.ccr21.jfk02.atlas.cogentco.com (154.54.84.125) 90 ms te0-0-0-4.ccr21.jfk02.atlas.cogentco.com (154.54.84.129) 90 ms *
6 te0-3-0-6.ccr21.dca01.atlas.cogentco.com (154.54.41.5) 96 ms te0-0-0-2.ccr21.dca01.atlas.cogentco.com (154.54.25.238) 96 ms te0-2-0-7.ccr21.dca01.atlas.cogentco.com (154.54.41.1) 96 ms
7 be2042.ccr21.iad02.atlas.cogentco.com (154.54.26.126) 97 ms 97 ms 97 ms
8 uunet.iad01.atlas.cogentco.com (154.54.13.138) 99 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 105 ms 105 ms
9 P0-8-0-0.LSANCA-LCR-22.verizon-gni.net (130.81.29.127) 177 ms 178 ms P1-0-0-0.LSANCA-LCR-21.verizon-gni.net (130.81.199.39) 174 ms
10 P8-0.LSANCA-DSL-44.verizon-gni.net (130.81.35.133) 175 ms P9-3.LSANCA-LCR-02.verizon-gni.net (130.81.193.109) 187 ms 182 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * Max number of unresponsive hops reached (firewall or filter?)
Here is what ICSI Netalyzer Results have stated.  
Network Access Link Properties + –
Network performance (?): Latency: 580 ms, Loss: 15.5% –
The round-trip time (RTT) between your computer and our server is 580 ms, which is somewhat high. This may be due to a variety of factors, including distance between your computer and our server, a slow network link, or other network traffic.
We recorded a packet loss of 16%. This loss is very significant and will lead to serious performance problems. It could be due either to very high load on our servers due to a large number of visitors, or problems in your network. Of the packet loss, at least 14.0% of the packets appear to have been lost on the path from your computer to our servers.
TCP connection setup latency (?): 720ms –
The time it takes for your computer to set up a TCP connection with our server is 720 ms, which is quite high. This may be due to a variety of factors, including a significant distance between your computer and our server, a particularly slow or poor network link, or problems in your network.
Background measurement of network health (?): 3 transient outages, longest: 0.8 seconds –
During most of Netalyzr's execution, the client continuously measures the state of the network in the background, looking for short outages. During testing, the client observed 3 such outages. The longest outage lasted for 0.8 seconds. This suggests a general problem with the network where connectivity is intermittent. This loss might also cause some of Netalyzr's other tests to produce incorrect results.
Network bandwidth (?): Upload 700 Kbit/s, Download 2.3 Mbit/s +
Network buffer measurements (?): Uplink 5400 ms, Downlink 1200 ms –
We estimate your uplink as having 5400 ms of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.
We estimate your downlink as having 1200 ms of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite 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 +
Unrestricted domain DNS lookup (?): OK +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 520 ms +
Direct probing of DNS resolvers (?): +
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
DNS results wildcarding (?): Warning –
Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 199.101.28.20, which resolves to search.dnsassist.verizon.net. You can inspect the resulting HTML content here.
There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer's typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.
The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.
The following lists your DNS server's behavior in more detail.
Please help.  I am so frustrated I literally have fights with my family over internet problems.  I am right now looking for other options and even starting to think about paying over 100 a month for dedicated line or T1 if they can service my area.  

Answer 1

Not a single response from Verizon on this? And after you posted the tests & information they will need? I think I may have to make a service choice soon. Its bad enough Verizon can't post a simple email address for our support, they have removed Usenet access, removed access to our websites (I use HTML so their sitebuilder is useless)... Sheeshe...