Diablo® III

3/31: Cox Disconnections

90 Blood Elf Warrior
13520
Posts: 58
Omaha, NE - Cox
South Windsor, CT. Cox
100 Blood Elf Paladin
15640
Posts: 9
Cox, Wichita, KS

Please note the I am only having a problem if I connect to the US server, if I switch to the Asia Server I stay connect just fine.

Tracert to Americas

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 7 ms 7 ms 8 ms 70.183.70.189
4 9 ms 7 ms 9 ms 70.183.66.74
5 16 ms 16 ms 16 ms 70.183.69.6
6 15 ms 15 ms 15 ms 70.183.71.64
7 27 ms 27 ms 27 ms 68.1.2.109
8 26 ms 28 ms 26 ms 207.86.210.9
9 27 ms 27 ms 30 ms 207.88.15.50.ptr.us.xo.net [207.88.15.50]
10 29 ms 30 ms 31 ms 192.205.36.101
11 63 ms 62 ms 63 ms cr2.dlstx.ip.att.net [12.122.100.90]
12 63 ms 63 ms 63 ms cr2.la2ca.ip.att.net [12.122.28.178]
13 109 ms 61 ms 62 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 60 ms 61 ms 61 ms 12.122.251.190
15 71 ms 59 ms 60 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 76 ms 61 ms 61 ms 12.129.209.68

Trace complete.

===========================================

Tracert to 182.162.134.1

Tracing route to 182.162.134.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 23 ms 11 ms 12 ms 70.183.70.193
4 11 ms 29 ms 11 ms 70.183.66.73
5 17 ms 16 ms 16 ms 70.183.69.2
6 16 ms 15 ms 15 ms 70.183.71.60
7 * 27 ms 28 ms 68.1.5.135
8 27 ms 27 ms 28 ms ge5-16.br02.dal01.pccwbtn.net [63.218.23.17]
9 189 ms 188 ms 187 ms lg-uplus.ge2-4.br01.seo01.pccwbtn.net [63.216.140.18]
10 197 ms 199 ms 197 ms 1.208.105.245
11 198 ms 224 ms 198 ms 211.233.95.94
12 199 ms 198 ms 199 ms 211.234.120.10
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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.

----------------------------------------------

Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 8 ms 7 ms 7 ms 70.183.70.193
4 16 ms 14 ms 16 ms 70.183.69.6
5 16 ms 16 ms 14 ms 70.183.71.16
6 14 ms 15 ms 15 ms 70.183.71.64
7 26 ms 29 ms 27 ms 68.1.2.109
8 26 ms 29 ms 27 ms 207.86.210.9
9 26 ms 27 ms 27 ms 207.88.15.50.ptr.us.xo.net [207.88.15.50]
10 29 ms 27 ms 27 ms dls-bb1-link.telia.net [213.248.81.237]
11 79 ms 69 ms 69 ms nyk-bb1-link.telia.net [213.155.133.176]
12 139 ms 138 ms 139 ms ldn-bb1-link.telia.net [80.91.249.248]
13 151 ms 152 ms 150 ms adm-bb3-link.telia.net [213.155.136.115]
14 149 ms 151 ms 151 ms adm-b5-link.telia.net [80.91.246.101]
15 * * * Request timed out.
16 * * * Request timed out.
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.

------------------------

Not sure if the last two will help or not.
Gainesville, Florida - Cox
Posts: 3
I posted my information, and was just curious as to if anything had been discovered or what the current status of this issue was. Thanks for the quick forum post and the helpfulness of your tech support guys and god speed.
90 Human Warrior
12565
Posts: 11
Cox- Central Louisiana
03/31/2014 01:43 PMPosted by Esab
...

My user ID (the only user) is the admin account. So, not really sure whats going on with it. Thanks for the reply though :)


hit start button
type "cmd" in the search without quotes
right click the "cmd.exe" that appears at the top and choose "Run as Administrator"
Should be good to go from there.


Thank you! That seems to have worked, doing the trace now :)
Cox AZ.. dont know much about comps so cant get other info.
Phoenix AZ

Trace route

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 9 ms 8 ms 7 ms 10.114.32.1
2 9 ms 9 ms 16 ms 10.114.32.1
3 10 ms 9 ms 11 ms 172.21.0.30
4 13 ms 13 ms 16 ms 70.169.73.64
5 11 ms 11 ms 10 ms 70.169.75.157
6 14 ms 11 ms 13 ms ae57.bar2.Phoenix1.Level3.net [4.28.82.53]
7 25 ms 22 ms 23 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
8 21 ms 21 ms 21 ms ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.18]
9 30 ms 25 ms 29 ms ae-63-63.ebr3.LosAngeles1.Level3.net [4.69.137.33]
10 25 ms 21 ms 20 ms ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
11 32 ms 22 ms 21 ms ae-206-3606.bar2.Tustin1.Level3.net [4.69.158.118]
12 27 ms 23 ms 23 ms 192.205.37.145
13 27 ms 25 ms 25 ms cr1.la2ca.ip.att.net [12.122.128.102]
14 23 ms 23 ms 23 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 22 ms 24 ms 22 ms 12.122.251.190
16 34 ms 27 ms 26 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
17 23 ms 22 ms 23 ms 12.129.209.68

Trace complete.

Pathping

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Wilfred [192.168.1.4]
1 10.114.32.1
2 10.114.32.1
3 172.21.0.30
4 70.169.73.64
5 70.169.75.157
6 ae57.bar2.Phoenix1.Level3.net [4.28.82.53]
7 ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
8 ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.18]
9 ae-63-63.ebr3.LosAngeles1.Level3.net [4.69.137.33]
10 ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
11 ae-206-3606.bar2.Tustin1.Level3.net [4.69.158.118]
12 192.205.37.145
13 cr1.la2ca.ip.att.net [12.122.128.102]
14 gar20.la2ca.ip.att.net [12.122.128.181]
15 12.122.251.190
16 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
17 12.129.209.68

Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Wilfred [192.168.1.4]
0/ 100 = 0% |
1 9ms 0/ 100 = 0% 0/ 100 = 0% 10.114.32.1
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 10.114.32.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 172.21.0.30
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% 70.169.73.64
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% 70.169.75.157
0/ 100 = 0% |
6 13ms 0/ 100 = 0% 0/ 100 = 0% ae57.bar2.Phoenix1.Level3.net [4.28.82.53]
0/ 100 = 0% |
7 21ms 0/ 100 = 0% 0/ 100 = 0% ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
0/ 100 = 0% |
8 22ms 0/ 100 = 0% 0/ 100 = 0% ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.18]
0/ 100 = 0% |
9 21ms 0/ 100 = 0% 0/ 100 = 0% ae-63-63.ebr3.LosAngeles1.Level3.net [4.69.137.33]
0/ 100 = 0% |
10 23ms 0/ 100 = 0% 0/ 100 = 0% ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
0/ 100 = 0% |
11 27ms 0/ 100 = 0% 0/ 100 = 0% ae-206-3606.bar2.Tustin1.Level3.net [4.69.158.118]
0/ 100 = 0% |
12 27ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.145
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% cr1.la2ca.ip.att.net [12.122.128.102]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% 12.122.251.190
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

0/ 100 = 0% |
17 23ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.
Tucson, AZ/Cox Communications.

Trace Route:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.80.0.1
3 8 ms 6 ms 7 ms 172.21.1.166
4 12 ms 11 ms 15 ms 72.215.229.20
5 10 ms 11 ms 10 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
6 10 ms 12 ms 11 ms ae57.bar2.Phoenix1.Level3.net [4.28.82.53]
7 23 ms 23 ms 21 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
8 22 ms 23 ms 22 ms ae-82-82.csw3.LosAngeles1.Level3.net [4.69.137.26]
9 22 ms 23 ms 22 ms ae-81-81.ebr1.LosAngeles1.Level3.net [4.69.137.9]
10 22 ms 23 ms 23 ms ae-6-6.ebr1.Tustin1.Level3.net [4.69.153.222]
11 21 ms 21 ms 21 ms ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
12 26 ms 27 ms 23 ms 192.205.37.145
13 26 ms 27 ms 23 ms cr1.la2ca.ip.att.net [12.122.128.102]
14 82 ms 122 ms 62 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 25 ms 25 ms 25 ms 12.122.251.190
16 26 ms 24 ms 25 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
17 24 ms 27 ms 25 ms 12.129.199.178
18 23 ms 23 ms 22 ms 12.129.209.68

Trace complete.

Path Ping:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Jenda-PC.jenda [192.168.1.100]
1 192.168.1.1
2 10.80.0.1
3 172.21.1.166
4 72.215.229.20
5 mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
6 ae57.bar2.Phoenix1.Level3.net [4.28.82.53]
7 ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
8 ae-82-82.csw3.LosAngeles1.Level3.net [4.69.137.26]
9 ae-81-81.ebr1.LosAngeles1.Level3.net [4.69.137.9]
10 ae-6-6.ebr1.Tustin1.Level3.net [4.69.153.222]
11 ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
12 192.205.37.145
13 cr1.la2ca.ip.att.net [12.122.128.102]
14 gar20.la2ca.ip.att.net [12.122.128.181]
15 12.122.251.190
16 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
17 12.129.199.178
18 12.129.209.68

Computing statistics for 450 seconds...

Hope these stats help.
Support Forum Agent
Posts: 26,417
Hello,

Thank you for the reports and information. We've been in contact with our networking peers and shared the information. The issue is being worked on but it may take time to be resolved. We appreciate your patience during this time and will keep this thread updated as soon as we have more information.

______________________________
Monday - Friday, 7am - 4pm Pacific Time
Rate me! Click here!
Vista, CA

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 7 ms 7 ms 7 ms 10.135.0.1
2 9 ms 9 ms 7 ms 68.6.11.72
3 * * * Request timed out.
4 11 ms 9 ms 10 ms fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
5 29 ms 23 ms 27 ms sanjbprj01-ae0.0.rd.sj.cox.net [68.1.5.184]
6 22 ms 21 ms 23 ms xe-7-0-1.edge1.SanJose3.Level3.net [4.53.208.197]
7 22 ms 25 ms 22 ms ae-2-70.edge2.SanJose1.Level3.net [4.69.152.79]
8 48 ms 49 ms 54 ms 192.205.32.209
9 52 ms 64 ms 51 ms cr2.sffca.ip.att.net [12.122.149.134]
10 62 ms 64 ms 63 ms cr2.la2ca.ip.att.net [12.122.31.133]
11 48 ms 48 ms 53 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 52 ms 62 ms 49 ms 12.122.251.190
13 57 ms 60 ms 61 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
14 59 ms 57 ms 58 ms 12.129.209.68

Trace complete.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 GabrielDaggett [192.168.0.3]
1 10.135.0.1
2 68.6.11.72
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GabrielDaggett [192.168.0.3]
0/ 100 = 0% |
1 8ms 0/ 100 = 0% 0/ 100 = 0% 10.135.0.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 68.6.11.72

Trace complete.
cox phoenix AZ The issue seems resolved for me. Thank you.
Newport News, VA

Trace:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 10 ms 10.4.144.1
3 10 ms 11 ms 9 ms 172.22.60.230
4 9 ms 13 ms 11 ms 172.22.60.230
5 9 ms 11 ms 9 ms 68.10.8.225
6 16 ms 16 ms 15 ms 68.1.4.246
7 14 ms 15 ms 17 ms 209.48.42.61
8 18 ms 18 ms 15 ms 207.88.15.54.ptr.us.xo.net [207.88.15.54]
9 16 ms 18 ms 17 ms 206.111.0.90.ptr.us.xo.net [206.111.0.90]
10 89 ms 87 ms 87 ms cr2.wswdc.ip.att.net [12.122.81.250]
11 87 ms 95 ms 89 ms cr1.cgcil.ip.att.net [12.122.18.21]
12 90 ms 83 ms 87 ms cr2.dvmco.ip.att.net [12.122.31.85]
13 89 ms 87 ms 87 ms cr1.slkut.ip.att.net [12.122.30.25]
14 88 ms 92 ms 87 ms cr2.la2ca.ip.att.net [12.122.30.30]
15 84 ms 110 ms 84 ms gar20.la2ca.ip.att.net [12.122.128.181]
16 83 ms 155 ms 98 ms 12.122.251.190
17 87 ms 86 ms 86 ms 206.16.68.46
18 85 ms 85 ms 90 ms 12.129.199.178
19 85 ms 87 ms 87 ms 12.129.209.68

Trace complete.

Pathping:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 ThomasBailey-PC [192.168.1.3]
1 192.168.1.1
2 10.4.144.1
3 172.22.60.230
4 172.22.60.230
5 68.10.8.225
6 68.1.4.246
7 209.48.42.61
8 207.88.15.54.ptr.us.xo.net [207.88.15.54]
9 206.111.0.90.ptr.us.xo.net [206.111.0.90]
10 cr2.wswdc.ip.att.net [12.122.81.250]
11 cr1.cgcil.ip.att.net [12.122.18.21]
12 cr2.dvmco.ip.att.net [12.122.31.85]
13 cr1.slkut.ip.att.net [12.122.30.25]
14 cr2.la2ca.ip.att.net [12.122.30.30]
15 gar20.la2ca.ip.att.net [12.122.128.181]
16 12.122.251.190
17 206.16.68.46
18 12.129.199.178
19 12.129.209.68

Computing statistics for 475 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.1.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.4.144.1
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 172.22.60.230
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 172.22.60.230
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% 68.10.8.225
0/ 100 = 0% |
6 21ms 0/ 100 = 0% 0/ 100 = 0% 68.1.4.246
0/ 100 = 0% |
7 18ms 0/ 100 = 0% 0/ 100 = 0% 209.48.42.61
0/ 100 = 0% |
8 17ms 0/ 100 = 0% 0/ 100 = 0% 207.88.15.54.ptr.us.xo.net [207.88.15.54]
0/ 100 = 0% |
9 21ms 0/ 100 = 0% 0/ 100 = 0% 206.111.0.90.ptr.us.xo.net [206.111.0.90]
1/ 100 = 1% |
10 --- 100/ 100 =100% 99/ 100 = 99% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
11 --- 100/ 100 =100% 99/ 100 = 99% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
13 --- 100/ 100 =100% 99/ 100 = 99% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
14 --- 100/ 100 =100% 99/ 100 = 99% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
15 --- 100/ 100 =100% 99/ 100 = 99% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
16 --- 100/ 100 =100% 99/ 100 = 99% 12.122.251.190
0/ 100 = 0% |
17 --- 100/ 100 =100% 99/ 100 = 99% 206.16.68.46
0/ 100 = 0% |
18 --- 100/ 100 =100% 99/ 100 = 99% 12.129.199.178
0/ 100 = 0% |
19 86ms 1/ 100 = 1% 0/ 100 = 0% 12.129.209.68

Trace complete.
Been on for a bit with no disc (fingers crossed). I'm on Cox in the Midwest.
The problem is DNS related. I switched from Cox DNS servers to GoogleDNS and everything works fine.

Here's how to switch to Google DNS :

http://bit.ly/1pGvMMl

I'm also including my info as you requested

Location (City, State): Fort Walton Beach, FL

Traceroute to server:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.17.8.1
3 10 ms 8 ms 7 ms ip68-1-11-228.at.at.cox.net [68.1.11.228]
4 16 ms 8 ms 8 ms ip68-1-11-212.at.at.cox.net [68.1.11.212]
5 38 ms 37 ms 37 ms 68.1.2.111
6 30 ms 29 ms 26 ms 207.86.210.9
7 25 ms 25 ms 25 ms 207.88.15.50.ptr.us.xo.net [207.88.15.50]
8 48 ms 47 ms 47 ms

Pathping to server:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Beast_3 [192.168.1.3]
1 192.168.1.1
2 10.17.8.1
3 ip68-1-11-228.at.at.cox.net [68.1.11.228]
4 ip68-1-11-212.at.at.cox.net [68.1.11.212]
5 68.1.2.111
6 207.86.210.9
7 207.88.15.50.ptr.us.xo.net [207.88.15.50]
8 192.205.36.101
9 cr2.dlstx.ip.att.net [12.122.100.90]
10 cr2.la2ca.ip.att.net [12.122.28.178]
11 gar29.la2ca.ip.att.net [12.122.129.241]
12 12-122-254-238.attens.net [12.122.254.238]
13 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 12.129.199.178
15 12.129.209.68

Computing statistics for 375 seconds...
^
It's been stuck there for a long time now.
COX Norfolk VA It has been a hour or so and I have not experienced any disconnect problems in Diablo 3
03/31/2014 02:10 PMPosted by Jurannok
Hello,

Thank you for the reports and information. We've been in contact with our networking peers and shared the information. The issue is being worked on but it may take time to be resolved. We appreciate your patience during this time and will keep this thread updated as soon as we have more information.

______________________________
Monday - Friday, 7am - 4pm Pacific Time
Rate me! [url="https://www.surveymonkey.com/s/Jurannok"]Click here![/url]


Thanks for the update! It makes a frustrating issue a little less of a problem, at least for me.
COX Bentonville- Arkansas
For what it's worth:

http://us.battle.net/d3/en/forum/topic/12329703313#1

...pretty much killed the game for me now, most likely will stop playing.
This topic has reached its post limit. You may no longer post or reply to posts for this topic.

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]