3/31: Cox Disconnections

Technical Support
1 2 3 26 Next
Hello,

We're seeing reports of players using Cox getting disconnected when connecting to their realm.

We'd like to get some more information on what's going on. If you use Cox and are getting disconnected, please provide the following:

Can you post some network information?

  • Location (City, State):
  • Traceroute to realm:
  • Pathping to realm:
  • ______________________________
    Monday - Friday, 7am - 4pm Pacific Time
    Rate me! Click here!
    i use cox i live in okaloosa county, FL. Don't know that other stuff. getting disconnected like crazy though as of 14:12 3/31/14
    Me too, I have cox connection in San Diego, California. Please explain how to do traceroute and pathping.
    Manhattan, Kansas. It's doing it to Diablo as well.

    Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
    over a maximum of 30 hops:

    1 7 ms 7 ms 7 ms 10.37.36.1
    2 7 ms 6 ms 7 ms 70.183.70.64
    3 8 ms 7 ms 7 ms ip70-183-65-94.ks.ks.cox.net [70.183.65.94]
    4 30 ms 19 ms 20 ms ip70-183-65-13.ks.ks.cox.net [70.183.65.13]
    5 18 ms 19 ms 19 ms wichsysr02.rd.ks.cox.net [70.183.71.10]
    6 26 ms 27 ms 34 ms 68.1.2.109
    7 28 ms 31 ms 27 ms 207.86.210.9
    8 27 ms 27 ms 27 ms 207.88.15.50.ptr.us.xo.net [207.88.15.50]
    9 30 ms 31 ms 32 ms dls-bb1-link.telia.net [213.248.81.237]
    10 59 ms 59 ms 59 ms ash-bb3-link.telia.net [80.91.252.121]
    11 159 ms 159 ms 228 ms ffm-bb1-link.telia.net [213.155.135.56]
    12 159 ms 157 ms 169 ms ffm-b10-link.telia.net [62.115.137.139]
    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.
    Pathping -

    Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
    over a maximum of 30 hops:
    0 sophie-PC [192.168.0.4]
    1 10.37.36.1
    2 70.183.70.64
    3 ip70-183-65-94.ks.ks.cox.net [70.183.65.94]
    4 ip70-183-65-13.ks.ks.cox.net [70.183.65.13]
    5 wichsysr02.rd.ks.cox.net [70.183.71.10]
    6 68.1.2.109
    7 207.86.210.9
    8 207.88.15.50.ptr.us.xo.net [207.88.15.50]
    9 dls-bb1-link.telia.net [213.248.81.237]
    10 ash-bb3-link.telia.net [80.91.252.121]
    11 ffm-bb1-link.telia.net [213.155.135.56]
    12 ffm-b10-link.telia.net [62.115.137.221]
    13 * * *
    Computing statistics for 300 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 sophie-PC [192.168.0.4]
    0/ 100 = 0% |
    1 8ms 0/ 100 = 0% 0/ 100 = 0% 10.37.36.1
    0/ 100 = 0% |
    2 14ms 0/ 100 = 0% 0/ 100 = 0% 70.183.70.64
    0/ 100 = 0% |
    3 12ms 1/ 100 = 1% 1/ 100 = 1% ip70-183-65-94.ks.ks.cox.net [70.183.65.94]
    0/ 100 = 0% |
    4 22ms 2/ 100 = 2% 2/ 100 = 2% ip70-183-65-13.ks.ks.cox.net [70.183.65.13]
    0/ 100 = 0% |
    5 21ms 1/ 100 = 1% 1/ 100 = 1% wichsysr02.rd.ks.cox.net [70.183.71.10]
    0/ 100 = 0% |
    6 35ms 4/ 100 = 4% 4/ 100 = 4% 68.1.2.109
    0/ 100 = 0% |
    7 31ms 0/ 100 = 0% 0/ 100 = 0% 207.86.210.9
    0/ 100 = 0% |
    8 24ms 1/ 100 = 1% 1/ 100 = 1% 207.88.15.50.ptr.us.xo.net [207.88.15.50]
    0/ 100 = 0% |
    9 34ms 3/ 100 = 3% 3/ 100 = 3% dls-bb1-link.telia.net [213.248.81.237]
    0/ 100 = 0% |
    10 63ms 0/ 100 = 0% 0/ 100 = 0% ash-bb3-link.telia.net [80.91.252.121]
    0/ 100 = 0% |
    11 172ms 0/ 100 = 0% 0/ 100 = 0% ffm-bb1-link.telia.net [213.155.135.56]
    0/ 100 = 0% |
    12 156ms 0/ 100 = 0% 0/ 100 = 0% ffm-b10-link.telia.net [62.115.137.221]

    Trace complete.
    Cox Communications in Omaha NE. Same issues. DC constantly.
    OKC, OK
    I called them about 10 minutes ago, They are looking into it too =)
    Cox san diego..... everything works fine except wow, did you ban a cox tech recently?? Joking btw... And they just put the fees up
    I use cox, and I am in Roanoke, va. I am getting disconnected constantly. Realm is locking up and then disconnecting.
    Cox communications Hampton Roads, Virginia. Same Issues. DC every 2 minutes
    I have Cox. Been getting disconnected for the past 30 minutes or so. When i log back in sometimes my characters wont even show!
    Wichita, KS
    Tracing route to 63.240.104.93 over a maximum of 30 hops

    1 3 ms 1 ms 2 ms 192.168.1.1
    2 11 ms 13 ms 10 ms 10.33.236.1
    3 54 ms 73 ms 104 ms 70.183.70.225
    4 18 ms 19 ms 18 ms 70.183.69.6
    5 18 ms 19 ms 20 ms



    Tracing route to 63.240.104.93 over a maximum of 30 hops

    0 BrandyNorris-PC [192.168.1.6]
    1 192.168.1.1
    2 10.33.236.1
    3
    Hey there, I'm not a Cox client, but I am having the same issues in northern British Columbia Canada, really high world latency, difficulties logging into any game, dc'ing when I do manage to get in.
    Niceville, FL with Cox.

    I can't traceroute or pathping because your websites won't load for me right now and I have zero idea how to do it without your link!
    I am having the same problem with all my Blizzard games.. I have cox and I live in Oceanside CA.
    Sometimes I can log in and get disconnected a few minutes later or I can't log in at all.

    Also everything else I use internet for is working fine, except the battle.net website.
    cox
    chandler, arizona

    constant dc ~03sec to 1min after login
    was working fine lastnight
    Phoenix, Arizona

    Tracing route to 206.18.148.180 over a maximum of 30 hops

    1 1 ms <1 ms 12 ms RKWIRE [192.168.1.1]
    2 7 ms 19 ms 37 ms 10.128.96.1
    3 8 ms 31 ms 8 ms 172.21.1.64
    4 14 ms 23 ms 29 ms 70.169.75.248
    5 8 ms 27 ms 21 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
    6 10 ms 12 ms 29 ms ae56.bar1.Phoenix1.Level3.net [4.31.188.61]
    7 11 ms 24 ms 18 ms ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]
    8 23 ms 24 ms 19 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
    9 19 ms 25 ms 33 ms ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.30]
    10 21 ms 37 ms 30 ms ae-93-93.ebr3.LosAngeles1.Level3.net [4.69.137.45]
    11 20 ms 30 ms 19 ms ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
    12 22 ms 21 ms 39 ms ae-206-3606.bar2.Tustin1.Level3.net [4.69.158.118]
    13 27 ms 43 ms 38 ms 192.205.37.145
    14 61 ms 76 ms 71 ms cr1.la2ca.ip.att.net [12.122.128.102]
    15 72 ms 75 ms 106 ms cr1.slkut.ip.att.net [12.122.30.29]
    16 63 ms 79 ms 71 ms cr2.dvmco.ip.att.net [12.122.30.26]
    17 65 ms 71 ms 81 ms cr1.cgcil.ip.att.net [12.122.31.86]
    18 60 ms 60 ms 69 ms gar18.cgcil.ip.att.net [12.122.99.21]
    19 61 ms 69 ms 79 ms 12.122.251.18
    20 61 ms 67 ms 74 ms 63.240.130.206
    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.

    Pathping:

    Tracing route to 206.18.148.180 over a maximum of 30 hops

    0 Elizabeth-PC.ph.cox.net [192.168.1.111]
    1 RKWIRE [192.168.1.1]
    2 10.128.96.1
    3 172.21.1.64
    4 70.169.75.248
    5 chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
    6 ae56.bar1.Phoenix1.Level3.net [4.31.188.61]
    7 ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]
    8 ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
    9 ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.30]
    10 ae-93-93.ebr3.LosAngeles1.Level3.net [4.69.137.45]
    11 ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
    12 ae-206-3606.bar2.Tustin1.Level3.net [4.69.158.118]
    13 192.205.37.145
    14 cr1.la2ca.ip.att.net [12.122.128.102]
    15 cr1.slkut.ip.att.net [12.122.30.29]
    16 cr2.dvmco.ip.att.net [12.122.30.26]
    17 cr1.cgcil.ip.att.net [12.122.31.86]
    18 gar18.cgcil.ip.att.net [12.122.99.21]
    19 12.122.251.18
    20 63.240.130.206
    21 * * *
    Computing statistics for 500 seconds...

    Drops in the same spot every time.
    Having the same problem. I'm in Mesa, Arizona.
    Tulsa Oklahoma, Can't get on hearthstone Diablo 3 or Wow
    Oklahoma City, Oklahoma

    Traceroute:
    Microsoft Windows [Version 6.3.9600]

    C:\WINDOWS\system32>tracert 12.129.209.68

    Tracing route to 12.129.209.68 over a maximum of 30 hops

    1 * 2 ms 1 ms 192.168.2.1
    2 * * * Request timed out.
    3 12 ms 11 ms 21 ms COX-68-12-8-200-static.coxinet.net [68.12.8.200]

    4 16 ms 10 ms 14 ms COX-68-12-10-70-static.coxinet.net [68.12.10.70]

    5 39 ms 40 ms 38 ms maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
    6 137 ms 107 ms 108 ms ATLIX-56M1.BB.Peach.Net [198.32.132.17]
    7 * 37 ms 38 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]
    8 38 ms 36 ms 36 ms ae-104-3504.edge5.Atlanta2.Level3.net [4.69.159.
    45]
    9 58 ms 64 ms 56 ms att-level3.atlanta2.level3.net [4.68.62.226]
    10 89 ms 85 ms 92 ms cr1.attga.ip.att.net [12.122.141.234]
    11 87 ms 86 ms 87 ms cr2.dlstx.ip.att.net [12.122.28.174]
    12 92 ms 88 ms 88 ms cr2.la2ca.ip.att.net [12.122.28.178]
    13 100 ms 86 ms 90 ms gar29.la2ca.ip.att.net [12.122.129.241]
    14 91 ms 85 ms 86 ms 12-122-254-238.attens.net [12.122.254.238]
    15 91 ms 92 ms 88 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
    9.193.254]
    16 89 ms 88 ms 87 ms 12.129.209.68

    Trace complete.

    Pathping:

    Tracing route to 12.129.209.68 over a maximum of 30 hops

    0 Michael-PC.Atiyeh [192.168.2.4]
    1 192.168.2.1
    2 * * *
    Computing statistics for 25 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Michael-PC.Atiyeh [192.168.2.4]
    0/ 100 = 0% |
    1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1

    Trace complete.
    I live in Tucson, Arizona. I just did a tracert but nothing unusual, over 26 hoops, 15ms average. I keep getting dc every 1 min, using Cox also.

    Join the Conversation

    Return to Forum