- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
It seems that Oregon and possibly other NW Verizon customers are unable to connect to sites in California. The issue was brought to light by people not able to connect to World of Warcraft. There are tons of users with the same problem.
Here is a thread full of verizon NW customers unable to connect to CA sites on the technical support forums over at blizzard. http://forums.worldofwarcraft.com/thread.html?topicId=24038610145&sid=1 . Many more traceroutes and other info there.
Blizzard says its a Verizon issue. Those that have called Verizon tech support say they say it is a Blizzard issue. Typical.
Here is my tracert to us.logon.battle.net, the primary logon portal... Obviously a problem, but with who, and why?
Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 15 ms 24 ms 7 ms L100.PTLDOR-VFTTP-19.verizon-gni.net [96.253.170.1]
3 5 ms 4 ms 4 ms 184.19.244.34
4 10 ms 9 ms 9 ms 108.57.128.160
5 9 ms 9 ms 9 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
6 10 ms 12 ms 12 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
7 11 ms 12 ms 12 ms POS6-0.BR1.SEA1.ALTER.NET [152.63.105.17]
8 12 ms 12 ms 12 ms 192.205.33.121
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 43 ms 42 ms 42 ms cr84.la2ca.ip.att.net [12.123.30.249]
13 41 ms 39 ms 39 ms gar5.la2ca.ip.att.net [12.122.129.25]
14 42 ms 42 ms 42 ms 12.122.255.74
15 42 ms 42 ms 42 ms 12.129.193.246
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having the same issues.
EDIT: Started last night at approximately 9:00 Pacific
"http://forums.worldofwarcraft.com/thread.html?topicId=24038610145&sid=1&pageNo=1" that is a thread on the warcraft forums with people having the same issue, all are around the Portland area
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having exactly the same problem.
traceroute to us.logon.battle.net (12.129.206.130), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 0.731 ms 0.361 ms 0.320 ms
2 l100.ptldor-vfttp-26.verizon-gni.net (74.107.138.1) 4.393 ms 4.327 ms 4.940 ms
3 184.19.244.104 (184.19.244.104) 4.970 ms 4.279 ms 4.993 ms
4 108.57.128.162 (108.57.128.162) 22.468 ms 21.817 ms 22.415 ms
5 0.xe-2-2-0.br3.sjc7.alter.net (152.63.1.249) 22.255 ms 21.683 ms 22.528 ms
6 uu-gw.sffca.ip.att.net (192.205.36.61) 25.005 ms 24.216 ms 24.979 ms
7 cr1.sffca.ip.att.net (12.122.114.18) 34.991 ms 34.155 ms 35.155 ms
8 * * *
9 cr83.la2ca.ip.att.net (12.123.30.109) 34.383 ms 34.189 ms 34.817 ms
10 gar5.la2ca.ip.att.net (12.122.128.25) 35.017 ms 34.092 ms 34.962 ms
11 12.122.255.74 (12.122.255.74) 35.006 ms 34.193 ms 34.959 ms
12 mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 34.968 ms
mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 33.337 ms
mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 33.746 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
This is Blizzard's latest response:
We are trying to do what we can from our end. As of right now the issue appears to be on their end. We are collecting data from customers that are having issues in a couple of threads. Hopefully, this will help determine the actual issue so it can get resolved ASAP."
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Windows 7 Ultimte 64
Windows Firewall (Ports open)
Marvell Yukon 88e8056 PCI-E Gigabit
Actiontec MI424-WR Hardware Version D
Verizon FIOS
Wired
Portland, OR
racing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 10.40.0.17
3 2 ms 1 ms 1 ms 184.19.244.88
4 18 ms 18 ms 18 ms 108.57.128.162
5 20 ms 20 ms 20 ms 0.xe-1-2-0.BR3.SJC7.ALTER.NET [152.63.1.149]
6 23 ms 23 ms 23 ms uu-gw.sffca.ip.att.net [192.205.36.61]
7 33 ms 33 ms 32 ms cr1.sffca.ip.att.net [12.122.114.10]
8 * * * Request timed out.
9 * * * Request timed out.
10 32 ms 32 ms 32 ms gar5.la2ca.ip.att.net [12.122.128.25]
11 33 ms 33 ms 33 ms 12.122.255.74
12 * * * Request timed out.
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having issues with Godaddy.com also.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having same issue, not only with us.logon.worldofwarcraft.com but also with us.battle.net website directly as well as with anything involving logging on with a battle.net account.
Blizzard entertainment claims it to be on verizons end, while verizon seems to be claiming it is on blizzards end, both have been notified and both of them better be talking to each other as if this is not fixed I will be wanting something from both verizon and blizzard as compensation.
For us.logon.worldofwarcraft.com
racing route to us.logon.worldofwarcraft.com [12.129.224.111]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 8 ms 7 ms 7 ms L100.PTLDOR-VFTTP-14.verizon-gni.net [98.108.159.1]
3 8 ms 6 ms 6 ms 184.19.244.26
4 12 ms 11 ms 11 ms 108.57.128.160
5 62 ms 14 ms 12 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
6 14 ms 14 ms 15 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
7 15 ms 14 ms 14 ms POS4-0.BR1.SEA1.ALTER.NET [152.63.105.81]
8 13 ms 14 ms 14 ms 192.205.33.121
9 * * * Request timed out.
10 * * * Request timed out.
11 43 ms 42 ms 41 ms cr2.la2ca.ip.att.net [12.122.31.133]
12 44 ms 41 ms 41 ms cr84.la2ca.ip.att.net [12.123.30.249]
13 43 ms 41 ms 42 ms gar5.la2ca.ip.att.net [12.122.129.25]
14 42 ms 42 ms 42 ms 12.122.255.74
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.
for us.battle.net :
Tracing route to battle.net [12.129.242.40]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 8 ms 7 ms 7 ms L100.PTLDOR-VFTTP-14.verizon-gni.net [98.108.159.1]
3 7 ms 6 ms 7 ms 184.19.244.84
4 23 ms 22 ms 21 ms 108.57.128.162
5 26 ms 36 ms 25 ms 0.xe-1-2-0.BR3.SJC7.ALTER.NET [152.63.1.149]
6 28 ms 27 ms 27 ms uu-gw.sffca.ip.att.net [192.205.36.61]
7 38 ms 37 ms 36 ms cr1.sffca.ip.att.net [12.122.114.14]
8 36 ms 36 ms 38 ms cr1.la2ca.ip.att.net [12.122.3.122]
9 36 ms 37 ms 36 ms cr83.la2ca.ip.att.net [12.123.30.109]
10 * * * Request timed out.
11 37 ms 37 ms 37 ms 12.122.255.74
12 * * * Request timed out.
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.
This is most likely been caused by the earthquake and is on verizons end, verizon should make sure that all of its hubs are working properly in california as the hops seem to ALWAYS end in california.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So there are a few traceroutes from oregon customers... Verizon tech support going to chime in on this or no?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Im seeing the same issue heres my traceroute info
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
tracert us.logon.battle.net
Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 9100EM.iniquity [192.168.1.1]
2 13 ms 14 ms 7 ms L100.PTLDOR-VFTTP-17.verizon-gni.net [98.108.130
.1]
3 6 ms 6 ms 7 ms 184.19.244.88
4 25 ms 24 ms 25 ms 108.57.128.162
5 25 ms 24 ms 25 ms 0.xe-1-2-0.BR3.SJC7.ALTER.NET [152.63.1.149]
6 27 ms 27 ms 27 ms uu-gw.sffca.ip.att.net [192.205.36.61]
7 * * * Request timed out.
8 * * * Request timed out.
9 40 ms 39 ms 39 ms cr84.la2ca.ip.att.net [12.123.30.249]
10 38 ms 36 ms 37 ms gar5.la2ca.ip.att.net [12.122.129.25]
11 39 ms 39 ms 69 ms 12.122.255.74
12 * * * Request timed out.
13 * * * Request timed out.
14 * 12.129.211.36 reports: Destination net unreachable.
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hopefully soon, I know there are a few more people on the other forums that hasn't posted here and I havn't been able to post on the blizzard website because of this problem, thankfully I was able to e-mail them.
The problem seems to be around california and started shortly after the quake so Verizon should be looking into that to see if there is any damage in there lines/hardware.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This also affect dreamhost hosted sites. Also having problems loading verizon.net