Outrageous packet loss, nearly unuseable internet

[CMPerolio]

Hello. I'm coming here today, because over the past week or so, I have been getting terrible slow, fluctuating internet every single day. The problems begins at exactly 7 AM EST every morning and continues until it feels like working again, ranging from 2 hours to 10 hours yesterday and today 7 and a half hours (so far... currently still experiencing the problem).

I play Diablo 3, an online Action RPG game. It is completely unplayable when this is happening. I have run a tracert and pathping for the game, and they responded informing me the issue is on Verizon's end, which I of course presumed already.

They informed me to go to Verizon and post these results as they should greatly help you find the solution, so here I am, and I seriously hope you can do something about this problem. Otherwise I may need to look elsewhere for a new service.

Tracert:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 17 ms 112 ms 14 ms verizon.home [192.168.1.1]
2 87 ms 217 ms 59 ms L100.TAMPFL-DSL-02.verizon-gni.net [71.98.160.1]
3 42 ms 115 ms 50 ms P0-1-0-0.TAMPFL-LCR-21.verizon-gni.net [130.81.34.148]
4 86 ms 47 ms 126 ms so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net [130.81.28.212]
5 89 ms 111 ms 70 ms 0.ae1.BR1.MIA19.ALTER.NET [152.63.87.162]
6 328 ms 329 ms 52 ms 204.255.168.18
7 112 ms 444 ms 238 ms cr81.fldfl.ip.att.net [12.122.82.22]
8 2485 ms 846 ms 270 ms cr2.ormfl.ip.att.net [12.122.1.45]
9 746 ms 654 ms 318 ms cr1.ormfl.ip.att.net [12.122.5.185]
10 773 ms 1018 ms 1165 ms cr2.hs1tx.ip.att.net [12.122.1.5]
11 353 ms 314 ms 118 ms cr1.dlstx.ip.att.net [12.122.28.157]
12 1033 ms 2772 ms 717 ms cr2.dlstx.ip.att.net [12.122.1.210]
13 744 ms 171 ms 305 ms cr2.la2ca.ip.att.net [12.122.28.178]
14 256 ms 616 ms 603 ms gar29.la2ca.ip.att.net [12.122.129.241]
15 121 ms 123 ms 125 ms 12-122-254-238.attens.net [12.122.254.238]
16 748 ms 1088 ms 646 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 And the pathping.

Tracing route to 12.129.209.68 over a maximum of 30 hops

 0 Dustin-PC.home [192.168.1.2] 
 1 verizon.home [192.168.1.1] 
 2 L100.TAMPFL-DSL-02.verizon-gni.net [71.98.160.1] 
 3 P0-1-0-0.TAMPFL-LCR-21.verizon-gni.net [130.81.34.148] 
 4 * so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net [130.81.28.212] 
 5 0.ae1.BR1.MIA19.ALTER.NET [152.63.87.162] 
 6 * * 204.255.168.18 
 7 * * cr81.fldfl.ip.att.net [12.122.82.22] 
 8 cr2.ormfl.ip.att.net [12.122.1.45] 
 9 cr1.ormfl.ip.att.net [12.122.5.185] 
 10 cr2.hs1tx.ip.att.net [12.122.1.5] 
 11 cr1.dlstx.ip.att.net [12.122.28.157] 
 12 cr2.dlstx.ip.att.net [12.122.1.210] 
 13 cr2.la2ca.ip.att.net [12.122.28.178] 
 14 gar29.la2ca.ip.att.net [12.122.129.241] 
 15 12.122.251.190 
 16 mdf001c7613r0002.lax1.attens.net [206.16.68.54] 
 17 * * * 
Computing statistics for 400 seconds...
 Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
 0 Dustin-PC.home [192.168.1.2] 
 46/ 100 = 46% |
 1 404ms 47/ 100 = 47% 1/ 100 = 1% verizon.home [192.168.1.1] 
 0/ 100 = 0% |
 2 544ms 46/ 100 = 46% 0/ 100 = 0% L100.TAMPFL-DSL-02.verizon-gni.net [71.98.160.1] 
 1/ 100 = 1% |
 3 543ms 47/ 100 = 47% 0/ 100 = 0% P0-1-0-0.TAMPFL-LCR-21.verizon-gni.net [130.81.34.148] 
 0/ 100 = 0% |
 4 823ms 47/ 100 = 47% 0/ 100 = 0% so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net [130.81.28.212] 
 1/ 100 = 1% |
 5 749ms 48/ 100 = 48% 0/ 100 = 0% 0.ae1.BR1.MIA19.ALTER.NET [152.63.87.162] 
 3/ 100 = 3% |
 6 689ms 51/ 100 = 51% 0/ 100 = 0% 204.255.168.18 
 49/ 100 = 49% |
 7 --- 100/ 100 =100% 0/ 100 = 0% cr81.fldfl.ip.att.net [12.122.82.22] 
 0/ 100 = 0% |
 8 --- 100/ 100 =100% 0/ 100 = 0% cr2.ormfl.ip.att.net [12.122.1.45] 
 0/ 100 = 0% |
 9 --- 100/ 100 =100% 0/ 100 = 0% cr1.ormfl.ip.att.net [12.122.5.185] 
 0/ 100 = 0% |
 10 --- 100/ 100 =100% 0/ 100 = 0% cr2.hs1tx.ip.att.net [12.122.1.5] 
 0/ 100 = 0% |
 11 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.28.157] 
 0/ 100 = 0% |
 12 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.122.1.210] 
 0/ 100 = 0% |
 13 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.28.178] 
 0/ 100 = 0% |
 14 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241] 
 0/ 100 = 0% |
 15 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190 
 0/ 100 = 0% |
 16 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54] 

Trace complete.

I really hope you can solve and fix this problem as soon as possible as it's also interferring with my work...

Thank you.

[dslr595148]

Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up.  It might shown up as the final hop (bottom-most line of the trace)  might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.

For example this what I see

---

news.giganews.com

    traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
    1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 13 ms 13 ms 13 ms
    2 ash-bb1-link.telia.net (213.248.70.241) 39 ms 7 ms 7 ms
    3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 4 ms
    4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.20.137) 6 ms 6 ms 6 ms
    5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (130.81.13.170) 6 ms 6 ms 6 ms
    6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms

---

Step two: Can you provide the Transceiver Statistics from your modem?

#3 If you don't know how to get that info, What is the brand and model of your modem?

[smith6612]

The traces and pathping results are being skewed by your network connection to your router. If you're on Wireless, get wired up and ensure your Wi-Fi is off, and then re-run the tests. The first hop in your traces is your router. That should be 1ms or less, very consistent with no loss.