dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
954
Rakeesh
join:2011-10-30
Phoenix, AZ

Rakeesh

Member

Cox peering

Well it finally died. I always have connectivity issues with wow, but now it finally just dropped completely, and as far as I can tell being on Cox is entirely to blame.

»www.mmo-champion.com/thr ··· ng/page2

I'm still able to talk to people in my teamspeak/ventrilo servers, and access this site, but can't connect to wow, and everybody in the teamspeak server has no problems at all.

Thinking this might be a youtube kind of thing where I'll have to use a VPN just to play the game. Kind of bad that I have to subscribe to third party services just to use services that are normally available to most internet users - the price I'm paying to both them and Cox is starting to not be worth it.
Rakeesh

Rakeesh

Member

Traceroute:

C:\Users\jjd>tracert 12.129.242.40
 
Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  router.lan [192.168.1.1]
  2     8 ms     9 ms     7 ms  10.48.96.1
  3     9 ms    11 ms     9 ms  172.21.0.172
  4    13 ms    22 ms    12 ms  chndcorc01-pos--0-3-0-0.ph.ph.cox.net [70.169.72
.48]
  5     9 ms     8 ms    10 ms  chndsysc01-te-8-4.ph.ph.cox.net [70.169.72.201]
 
  6    12 ms    11 ms    11 ms  ae56.bar1.Phoenix1.Level3.net [4.31.188.61]
  7    15 ms    14 ms    12 ms  ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]
 
  8    21 ms    25 ms    26 ms  ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
 
  9    26 ms    30 ms    25 ms  ae-72-72.csw2.LosAngeles1.Level3.net [4.69.137.2
2]
 10    21 ms    19 ms    19 ms  ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5
]
 11    20 ms    18 ms    22 ms  ae-6-6.ebr1.Tustin1.Level3.net [4.69.153.222]
 12    20 ms    19 ms    18 ms  ae-108-3508.bar2.Tustin1.Level3.net [4.69.158.11
0]
 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     *        *     ^C
 
Rakeesh

Rakeesh

Member

More info:

»www.reddit.com/r/wow/com ··· rs_down/

CoxVegas
join:2011-07-25
Las Vegas, NV

CoxVegas to Rakeesh

Member

to Rakeesh
Reading through that reddit post (and looking at your traceroute), it looks like it was an issue between Level3 and AT&T - not much Cox can do about it.

Blizzard could change route advertisements around to direct people to come into backup connections (if they have them, I honestly don't know), but from our side, we're just routing traffic where we're told to.
Maltz
join:2011-01-08
Fayetteville, AR

Maltz

Member

I don't know details, but I did see something about some pretty heavy-hitting DoS attacks on several online games last night. WoW may have been one of them.

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA
Nokia BGW320-505

odog to Rakeesh

Premium Member

to Rakeesh
said by Rakeesh:

Well it finally died. I always have connectivity issues with wow, but now it finally just dropped completely, and as far as I can tell being on Cox is entirely to blame.

Blame the internet.

c:\Users\xxxxxxx\Desktop>tracert 12.129.242.40
 
Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  10.11.xx.
  2     1 ms     1 ms     1 ms  10.xx.xx.184
  3     1 ms     1 ms     1 ms  10.xx.xx.175
  4     3 ms     1 ms     3 ms  10.xx.xx.12
  5     3 ms     2 ms     2 ms  24.248.74.2
  6     3 ms     2 ms     2 ms  68.1.0.4
  7     3 ms     3 ms     3 ms  maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
  8     4 ms     3 ms     3 ms  ge-6-22.car1.Atlanta4.Level3.net [4.53.232.5
  9     4 ms     3 ms     4 ms  vlan51.ebr1.atlanta2.level3.net [4.69.150.62
 10    40 ms     4 ms     5 ms  4.69.159.37
 11    23 ms    23 ms    22 ms  att-level3.atlanta2.level3.net [4.68.62.226]
 12    40 ms    43 ms    42 ms  cr1.attga.ip.att.net [12.122.141.234]
 13    44 ms    41 ms    39 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 14    37 ms    37 ms    37 ms  12.123.249.221
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7

Member

Maybe the system is down?

»www.youtube.com/watch?v= ··· qsuww6lw

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA
TP-Link TD-8616
Asus RT-AC66U B1
Netgear FR114P

NormanS to Rakeesh

MVM

to Rakeesh
Have a trace route from another ISP:
Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  Chihiro [192.168.102.1]
  2    30 ms    30 ms    30 ms  173-228-7-1.dsl.static.sonic.net [173.228.7.1]
  3    31 ms    30 ms    30 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    31 ms    30 ms    30 ms  0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
  5    31 ms    31 ms    31 ms  te0-0-0-15.ccr21.sjc04.atlas.cogentco.com [38.104.141.81]
  6    60 ms    31 ms    31 ms  be2017.mpd21.sfo01.atlas.cogentco.com [154.54.2.165]
  7    44 ms    46 ms    44 ms  be2104.mpd21.lax01.atlas.cogentco.com [154.54.74.157]
  8    45 ms    48 ms    44 ms  be2179.ccr23.lax05.atlas.cogentco.com [154.54.41.82]
  9    48 ms    45 ms    45 ms  att.lax05.atlas.cogentco.com [154.54.13.150]
 10    47 ms    43 ms    47 ms  cr1.la2ca.ip.att.net [12.123.132.138]
 11    43 ms    42 ms    42 ms  12.122.90.29
 12     *        *        *     Request timed out.
 ...
 ...
 30     *        *        *     Request timed out.
 
Trace complete.
 

Because I don't play Blizzard games, I can't assess the "reachability" of 'us.battle.net'; but trace route time outs do not, necessarily, prove a site is unreachable, only that it is not responding to diagnostic packets.
Ameth
join:2011-07-20
ARRIS eXtreme SB6120
Asus RT-AC66

Ameth to Rakeesh

Member

to Rakeesh
The thing about Wow is that while you first log into Los Angeles, their servers are in 4 regional data centers. Also your game play can change you from one server to another just by walking into an instance.

I know when my server use to be hosted in Texas there were some issues where traffic in VA wasnt getting there but since its been in Chicago its been much cleaner save a few cogentco issues...

I'm on Ruin Battle group.

If you can get passed the authentication server in Los Angeles but get hung up loading your characters on your server try to reach your Data Center.

»www.wowwiki.com/US_realm ··· tacenter

I took a look at your MMO Champ thread and noted on the 1st page

"Located in Australia and I'm unable to connect either. So it's not isolated to US users. "

and

"Not Cox, have Sudden Link."

Kett2000
Premium Member
join:2002-04-23
Lilburn, GA

Kett2000 to Rakeesh

Premium Member

to Rakeesh
Here's the trace route I get from another ISP:

Tracing route to us.battle.net [12.129.242.40] over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  gw-condo.domain.home.bivek.net [192.168.1.1]
  2    16 ms    34 ms    19 ms  rtr-sjo.domain.home.bivek.net [50.117.26.108]
  3    24 ms    22 ms    24 ms  bivek-networks-llc.gige.egihosting.com [50.117.2
6.97]
  4    18 ms    17 ms    18 ms  xe-0-6-0-29.r07.snjsca04.us.bb.gin.ntt.net [129.
250.200.197]
  5    19 ms    19 ms    37 ms  192.205.37.57
  6    30 ms    31 ms    30 ms  cr2.sffca.ip.att.net [12.122.149.138]
  7    31 ms     *       29 ms  cr2.la2ca.ip.att.net [12.122.31.133]
  8    28 ms    31 ms    28 ms  gar29.la2ca.ip.att.net [12.122.129.241]
  9    67 ms   202 ms   396 ms  12-122-254-234.attens.net [12.122.254.234]
 10    31 ms    29 ms    29 ms  mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15  ^C]
 

ikyuaoki
join:2011-04-12
Wichita, KS

ikyuaoki to Rakeesh

Member

to Rakeesh
same here, my tracert is not reaching the us.battle.net server so I believe that ping/tracert/pingpath commands that uses the ICMP packets, so that us.battle.net of the firewall barrier that blocked the ICMP packets completely by dropping the ICMP packets on the floor infinite but us.battle.net only allows the TCP SYN/ACK packets through without problems.

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 10.32.32.1
3 8 ms 7 ms 7 ms 70.183.70.185
4 15 ms 15 ms 15 ms 70.183.69.6
5 14 ms 15 ms 20 ms 70.183.71.16
6 26 ms 25 ms 26 ms 68.1.5.140
7 28 ms 28 ms 26 ms 207.86.210.9
8 26 ms 25 ms 25 ms 207.88.15.50.ptr.us.xo.net [207.88.15.50]
9 29 ms 31 ms 30 ms 192.205.36.101
10 63 ms 64 ms 63 ms cr2.dlstx.ip.att.net [12.122.100.90]
11 65 ms 63 ms 64 ms cr2.la2ca.ip.att.net [12.122.28.178]
12 62 ms 61 ms 61 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 60 ms 59 ms 60 ms 12-122-254-238.attens.net [12.122.254.238]
14 62 ms 62 ms 63 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 ^C

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7

Member

Because of the safeguards that protect our Battle.net servers, you may notice later hops in your trace route failing with an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. You may also see inflated latency numbers. You can ignore any error messages you receive after contacting our servers as they do not indicate a problem with your internet connection. To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net.

»us.battle.net/support/en ··· aceroute

ikyuaoki
join:2011-04-12
Wichita, KS

ikyuaoki to odog

Member

to odog
Blame the internet? just blame us.battle.net and that's about it, not just blaming the internet. I believe that us.battle.net gateway guard barrier as firewall side as that blocks the ICMP packets.