Diablo® III

Lag, D/C's you name it

Anything that could happen with an internet connection is happening to me. I ran a traceroute and a pathping and here are the results, I cannot hook up directly to the modem with an ethernet cable because I use a desktop and the modem is in the living room, Any help would be greatly appreciated, I just came back after a long hiatus and I just want to play with my friends.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 * 3 ms 2 ms 192.168.0.1
2 688 ms 116 ms 37 ms 74-129-8-1.dhcp.insightbb.com [74.129.8.1]
3 12 ms 11 ms 13 ms 74-128-23-137.dhcp.insightbb.com [74.128.23.137]
4 22 ms 21 ms 14 ms tge0-13-0-3.lsvqkydb-ccr01.midwest.rr.com [65.29.25.28]
5 27 ms 22 ms 25 ms network-065-189-140-166.mwrtn.rr.com [65.189.140.166]
6 36 ms 33 ms 31 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
7 32 ms 31 ms 34 ms 107.14.19.135
8 34 ms 64 ms 33 ms ix-17-0.tcore1.AEQ-Ashburn.as6453.net [66.198.154.21]
9 36 ms 32 ms 34 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
10 36 ms 34 ms 34 ms 192.205.34.245
11 98 ms 99 ms 223 ms cr2.wswdc.ip.att.net [12.122.84.82]
12 102 ms 103 ms 93 ms cr1.cgcil.ip.att.net [12.122.18.21]
13 99 ms 99 ms 97 ms cr2.dvmco.ip.att.net [12.122.31.85]
14 98 ms 101 ms 97 ms cr1.slkut.ip.att.net [12.122.30.25]
15 104 ms 103 ms 102 ms cr2.la2ca.ip.att.net [12.122.30.30]
16 118 ms 99 ms 101 ms gar20.la2ca.ip.att.net [12.122.128.181]
17 97 ms 95 ms 96 ms 12-122-254-234.attens.net [12.122.254.234]
18 95 ms 93 ms 94 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 MININT-M5AJ3UF.cinci.rr.com [192.168.0.6]
1 192.168.0.1
2 74-129-8-1.dhcp.insightbb.com [74.129.8.1]
3 74-128-23-137.dhcp.insightbb.com [74.128.23.137]
4 tge0-13-0-3.lsvqkydb-ccr01.midwest.rr.com [65.29.25.28]
5 network-065-189-140-166.mwrtn.rr.com [65.189.140.166]
6 ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
7 107.14.19.135
8 ix-17-0.tcore1.AEQ-Ashburn.as6453.net [66.198.154.21]
9 if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
10 192.205.34.245
11 cr2.wswdc.ip.att.net [12.122.84.82]
12 cr1.cgcil.ip.att.net [12.122.18.21]
13 cr2.dvmco.ip.att.net [12.122.31.85]
14 cr1.slkut.ip.att.net [12.122.30.25]
15 cr2.la2ca.ip.att.net [12.122.30.30]
16 gar20.la2ca.ip.att.net [12.122.128.181]
17 12-122-254-234.attens.net [12.122.254.234]
18 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 MININT-M5AJ3UF.cinci.rr.com [192.168.0.6]
0/ 100 = 0% |
1 9ms 3/ 100 = 3% 3/ 100 = 3% 192.168.0.1
0/ 100 = 0% |
2 20ms 2/ 100 = 2% 2/ 100 = 2% 74-129-8-1.dhcp.insightbb.com [74.129.8.1]
0/ 100 = 0% |
3 25ms 0/ 100 = 0% 0/ 100 = 0% 74-128-23-137.dhcp.insightbb.com [74.128.23.137]
0/ 100 = 0% |
4 26ms 2/ 100 = 2% 2/ 100 = 2% tge0-13-0-3.lsvqkydb-ccr01.midwest.rr.com [65.29.25.28]
0/ 100 = 0% |
5 37ms 1/ 100 = 1% 1/ 100 = 1% network-065-189-140-166.mwrtn.rr.com [65.189.140.166]
0/ 100 = 0% |
6 40ms 1/ 100 = 1% 1/ 100 = 1% ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
0/ 100 = 0% |
7 44ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.135
1/ 100 = 1% |
8 42ms 1/ 100 = 1% 0/ 100 = 0% ix-17-0.tcore1.AEQ-Ashburn.as6453.net [66.198.154.21]
2/ 100 = 2% |
9 40ms 20/ 100 = 20% 17/ 100 = 17% if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
0/ 100 = 0% |
10 46ms 3/ 100 = 3% 0/ 100 = 0% 192.205.34.245
97/ 100 = 97% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.84.82]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.
Edited by Stumpy#1451 on 7/22/2013 11:14 PM PDT
Reply Quote
top is the traceroute bottom is the pathping
Reply Quote
MVP - Technical Support
View profile
Looking at this your problems start at your router and the first hop.
1 * 3 ms 2 ms 192.168.0.1
2 688 ms 116 ms 37 ms 74-129-8-1.dhcp.insightbb.com [74.129.8.1]


That shows a timeout on the router at hop one then your latency spikes at the first node of your ISP.

1 9ms 3/ 100 = 3% 3/ 100 = 3% 192.168.0.1
0/ 100 = 0% |
2 20ms 2/ 100 = 2% 2/ 100 = 2% 74-129-8-1.dhcp.insightbb.com [74.129.8.1]
0/ 100 = 0% |


This here shows 3% packet loss at your router and 2% at hop two. My guess is that the router issue is being carried forward.

You can try powering down the modem, router and PC then restarting them in sequence. Sometimes that helps. If you own the router, you can also try updating the firmware on it. If you don't own it then contact your ISP.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]