Cannot connect to WoW or any Blizzard website.

[amartche]

Am I crazy, or did the whole thing go under? I asked a few people and they confirmed that they can visit the wow.com website. I can't. I can't visit Blizzard.com or Wow-Europe even! Anything by Blizzard I try, does not respond. This was working just fine a few hours ago, there were no changes made to my computer. Its a windows vista and my firewall does not block WoW. Never did and I don't think thats the problem.

Is it down or am I doing something wrong?
Cheers :)

[Tanitha]

I can reach Blizzard and login (Using a US account though). There were problems like that about two or three weeks ago, Thursday for me, but it was one of Xtra's routers that had kicked the bucket and would not route to Blizzard at all. (Everywhere else was fine though!)

Try running a tracert from the command line:

e.g.

"tracert blizzard.com"

to see where it begins failing. Or even a pathping (pathping blizzard.com).

[amartche]

Thanks for your reply Tanitha.

I did a tracert on the worldofwarcraft.com and it went through the first 5 hops conneting to the server, then after that Request Timed Out. Sorry for the big quote. I am running on a wireless cable internet. No firewalls in between straight connection. It was just working a few hours ago, went for my finals came back and couldn't visit anything.

Tracing route to worldofwarcraft.com [12.129.217.201]
over a maximum of 30 hops:

1 26 ms 26 ms 29 ms 74.210.18.1
2 26 ms 27 ms 28 ms gw01.wlfdle.phub.net.cable.rogers.com [66.185.93
.81]
3 26 ms 28 ms 27 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.
142]
4 26 ms 28 ms 28 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.80.1
70]
5 46 ms 50 ms 49 ms igw01.ny8th.phub.net.cable.rogers.com [66.185.81
.13]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.

[Tanitha]

That certainly looks as if it's dying on the cable.rogers.com network. Do you have any other connection method available to test with - like an old dialup account you can get on, or something like that?

Given that I can login to the US servers (Just checked again right now, can login with my main so I assume it's ok) I'm guessing that there is an issue with cable.rogers.com.

Maybe give them a call - depending on how helpful / efficient their support is. Alternatively, you could simply wait a day or so - all depends on how much you want to play WoW right now :grin:

[amartche]

That certainly looks as if it's dying on the cable.rogers.com network. Do you have any other connection method available to test with - like an old dialup account you can get on, or something like that?

Given that I can login to the US servers (Just checked again right now, can login with my main so I assume it's ok) I'm guessing that there is an issue with cable.rogers.com.

Maybe give them a call - depending on how helpful / efficient their support is. Alternatively, you could simply wait a day or so - all depends on how much you want to play WoW right now :grin:

I am pretty patient :)
I live in college residence, I will try their connection. The only thing it DOESN'T let me do is actually play WoW. Which sucks :(

Thanks for the help, I will let ya know how it goes :thumbsup:

[amartche]

Yep. As soon as I got on the college network the website works. It is just confusing me how, on Rogers, EVERY site but Blizzard ones work. I am just going to have to give them a call and see whats the deal there hehe.

Take care :flowers:

[sackmaster]

the roger's whatever could have a dead link to enable routing to the passpoint of the wow site.

E.X. router A recieves a packet from a node, it then looks at the address to see where it should go. All depending on the router protocol the router could know where wow is or it could just know the next hop it needs to send the packet to, to get to wow.

E.X.2 router a recieves the packet, however does not see blizzard as one of its connected links, however it knows to send the packet to router C because C knows how to get it to wow.

E.X.3 Router C recieves the Packet from router a, and sees that WOW is not connected to any of its links, however C knows that it can send a packet to router H, and router H, will send it to blizzard servers, however router C can also see that if the packet is meant for the website and not the server persay then router C will send the packet out to router J (because C knows that J can get to the website and H can't)

This keeps happening until the packet reaches its destination. However if one of the links to one of the servers is down. that could be the problem.

Yes, I also know that there is a lot more to it than this, I just don't want to go into my CCNA classes again.

[Clavina]

That certainly looks as if it's dying on the cable.rogers.com network. Do you have any other connection method available to test with - like an old dialup account you can get on, or something like that?


Not necessarily, tracerts to wow servers will appear to time out as soon as they hit blizzard's servers as the ping will not be returned.

To me this looks like a normal tracert to a blizz server. That being said I play on EU servers so I'm not sure at what stage the US ones will start to show timeouts.

[sackmaster]

Not necessarily, tracerts to wow servers will appear to time out as soon as they hit blizzard's servers as the ping will not be returned.

To me this looks like a normal tracert to a blizz server. That being said I play on EU servers so I'm not sure at what stage the US ones will start to show timeouts.

Yes you are right it will dye when the requests hit blizzards servers, however you normally don't go just from your isp straight to blizzard, there are usually other hops that you need to take past your isp in order to get to blizzard. EX going over a wan backbone link. Heres the heirarchy. POP then to NAP, then to backbone (or another nap), then reverse the order once on backbone, go go down to blizzards servers. (yes I know this is extremely abbrivated, but i don't want to write a huge list). So he would at least see more points than he is seeing in his tracert.

Here is an example:
of when I try to ping microsoft.

1 <10 ms <10 ms <10 ms *.*.*.* All internal network
2 <10 ms <10 ms <10 ms domian.domain.com [*.*.*.*] |
3 36 ms 37 ms 36 ms ip address here |
4 35 ms 36 ms 36 ms ip address here
5 36 ms 35 ms 35 ms ip address here
6 37 ms 37 ms 37 ms ip address here
7 36 ms 36 ms 35 ms ip address here
8 36 ms 49 ms 39 ms ip address here
9 38 ms 36 ms 36 ms ip address here
10 39 ms 39 ms 39 ms ip address here
11 105 ms 105 ms 105 ms gbr1-p70.cb1ma.ip.att.net [12.123.40.162]
12 106 ms 109 ms 106 ms tbr2-p013502.cb1ma.ip.att.net [12.122.5.57]
13 107 ms 107 ms 107 ms tbr2-cl5.cgcil.ip.att.net [12.122.10.106]
14 107 ms 108 ms 109 ms tbr1-cl22.cgcil.ip.att.net [12.122.9.133]
15 109 ms 108 ms 108 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
16 107 ms 111 ms 107 ms 12.122.81.101
17 * * * Request timed out.
18 * * ^C

Now see the att is the nap and backbone routers, but I can still reach them. He is having a problem even reaching the backbone routers. Like I said before it is probably because his isp thinks that it can get to blizz servers a certain way, and in fact they can't.