Child Item

Site Totals

61487 Questions Answered 271 Categories

Verizon Oregon Customers Can Not Connect to CA Sites - Including us.logon.battle.net

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.

Comments

Iyenrith

Having the same issues.

EDIT: Started last night at approximately 9:00 Pacific

OS: Win7 64 Bit

Firewall: Windows basic one

3x Different routers none work

Location: Forest Grove, OR

Internet Provider: Verizon Fios and basic DSL (Neither work)

tracert 12.129.206.130 > c:\output.txt

Tracing route to 12.129.206.130 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1

2 65 ms 24 ms 24 ms L200.PTLDOR-DSL-02.verizon-gni.net [70.104.254.1]

3 24 ms 24 ms 23 ms 184.19.244.248

4 55 ms 48 ms 40 ms 108.57.128.162

5 121 ms 42 ms 42 ms 0.xe-1-2-0.BR3.SJC7.ALTER.NET [152.63.1.149]

6 107 ms 44 ms 43 ms uu-gw.sffca.ip.att.net [192.205.36.61]

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 54 ms 54 ms 54 ms gar5.la2ca.ip.att.net [12.122.128.25]

11 * * * Request timed out.

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 12.129.211.36 reports: Destination net unreachable.

Trace complete.

"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

brianah

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:

"Blitzurteil,

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."

It is obviously a Verizon/Blizzard problem and one would hope that they would get together and sort it out. I know there are at least 20 Oregonians trying to log on to Blizzard via Verizon that can't.

Bizzo

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.

Bizzo

Having issues with Godaddy.com also.

shananigan

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.

Blitzurteil

So there are a few traceroutes from oregon customers... Verizon tech support going to chime in on this or no?

wags_ithyliri

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.

shananigan

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.

archer75

This also affect dreamhost hosted sites. Also having problems loading verizon.net

Blitzurteil

Says right at top its a "peer to peer" forum... just read that... so verizon tech support probably doesn't even read it. Typical. I tried to do live chat so I could copy/paste my tracert info and got this:

"We apologize for the inconvenience, however Verizon Live Chat is currently unavailable. We are either experiencing high customer volume or the center is closed for the day. Our hours are 7 Days a week: 8:00 AM - 12:00 AM ET."

So the only option is call them, so they can blow you off or put you on hold for 2 hours just to say, "It's blizzards problem". I hate comcast, or xfinity or whatever they're called now but I may be back soon.

John_Wolf

FIOS Customer in Beaverton, OR

tracert to us.battle.net:

1 1 ms 1 ms 1 ms 192.168.1.1
2 5 ms 4 ms 4 ms 10.40.0.3
3 5 ms 38 ms 7 ms 184.19.244.0
4 11 ms 14 ms 19 ms 108.57.128.160
5 9 ms 21 ms 14 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
6 30 ms 14 ms 12 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
7 11 ms 14 ms 22 ms POS6-0.BR1.SEA1.ALTER.NET [152.63.105.17]
8 11 ms 17 ms 19 ms 192.205.33.121
9 36 ms 37 ms 37 ms cr1.st6wa.ip.att.net [12.122.146.46]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 45 ms 41 ms 38 ms gar5.la2ca.ip.att.net [12.122.129.25]
14 * * * Request timed out.
15 58 ms 37 ms 38 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
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

Started for me at around 9 p.m. PST Sunday night. I can get to www.worldofwarcraft.com as of about 8 a.m. PST this morning and forums.battle.net(although very slow to respond) I cannot get to www.battle.net or us.battle.net as of this morning and am unable to login to battle.net.

shananigan

Well, I e-mailed verizon directly as well as blizzard, blizzard had better be at least opening communications with verizon because both companies enjoy blaming others and wont do any actual work, if they actually talked to each other this would be resolved in a fews hours most likely...... **bleep** corperations not giving a **bleep** about customers.

CheckingOutForu

Verizon can blame Blizzard. Blizzard can blame verizon. Both can sit around and pretend there is no issue, but trust this won't go on for long.

Websites that are down also:

- www.worldofwarcraft.com

- www.blizzard.com

- www.battle.net

idk if it's a block, or a cable, or who's side it's on, but if there are seriously 11million people getting blocked, this 'will' get resolved when mom & dad get home. 🙂

mail4ta

Having issues as well - first noticed last night around 10pm. I cannot access severeal sites today - but can access others just fine.

However - email is also seemingnly involved - as I am all of a suddeen today also having email issues.

Unfortunetely, one site that I cannot connect to today and also cannot seem to get email going (POP3 issues) is my own business website (www.idestdesign.com).

Further, I cannot access webmail for it (stranger still).

This would normally point to a hosting issue - so went to hosting provider Bluehost website --- oddly, I can get to their site but it only partically loads, like its loading in old defunct cache of the site.

I had another person I know using Fios check - she was unable to see several of the same sites I cannot, but actually could see a few that were timing out for me.

I have these same connectivity issues with a client website - I cannot access it www.myfoodmyhealth.com, nor am I receiving emails from the email account I have off that domain. This site is hosted in Salt Lake City (so its not a CA site).

Not sure if any of this helps anyone.

Verdi

I play Everquest 2 and I'm having the same issue. Started having problems last night while playing. I contacted SOE and they are saying it's Verizon's issue. I've been trying to contact Verizon FiOs phone support and have been on hold for like a half hour.

brianah

I just spent half an hour on hold with Verizon waiting to talk to tech support. Finally gave up. I seem to be able to log on to the WoW community sight alright, although it's glitchy, but can't log on to WoW or The Armory.

Think I'll try the email route for contacting Verizon. Hopefully the problem of not being able to contact a live person is because they are being barraged by calls from those of us who can't connect with Blizzard.

keefpdx

Same problems.

Cannot connect to world of warcraft or any related world of warcraft site.

This needs to be resolved, you're going to lose a lot of customers. It's not a blizzard issue, it's a verizon issue. We have other options as far as ISPs, the only reason I even chose fios was I figured it would have better speeds for gaming, but zero connectivity doesn't do me much good so...

Verdi

Hey, give them a break...at least they acknowledge there's a problem. I had Comcast before this and their support was pretty horrific compared to anything I'vd had to deal with with Verizon. FiOs has been rock solid for me before this...unlike my Comcast experience so I feel I can cut Verizon some slack. But hey, do what you feel you must but I don't recommend Comcast! lol

spacedebris

Well in this case, its NOT a Blizzard issue and it is also NOT a Verizon issue. It a problem with an isp between Verizon and where the servers are located. Verizon has absolutely no control over them. All they can do, like yourself, is contact them and hope they fix it. Verizon has tracked down the problem, let us know that they found the problem, and have notified the proper people. Now they are not telling us who is at fault, but we can tell by the tracerts posted. The problem is with att.net. But since the problem is with routers that Verizon has no control over, there is not much that can be done from their end.

covertcycle

Here's another trace route, from Hillsboro...

Tracing route to us.logon.worldofwarcraft.com [12.129.232.109]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]

2 6 ms 6 ms 7 ms L100.PTLDOR-VFTTP-19.verizon-gni.net [96.253.170.1]

3 9 ms 6 ms 6 ms 184.19.244.92

4 25 ms 24 ms 24 ms 108.57.128.162

5 25 ms 24 ms 24 ms 0.xe-2-2-0.BR3.SJC7.ALTER.NET [152.63.1.249]

6 30 ms 29 ms 29 ms uu-gw.sffca.ip.att.net [192.205.36.61]

7 * * * Request timed out.

8 39 ms 37 ms 39 ms cr2.la2ca.ip.att.net [12.122.31.133]

9 40 ms 39 ms 39 ms cr84.la2ca.ip.att.net [12.123.30.249]

10 * * * Request timed out.

11 40 ms 38 ms 39 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.

Spector666

Yep guess you are right, its not Verizon's problem nope I don't pay them for internet or anything, hope they refund some money for lost game time and tell my guildies why I cant make raids. I never had any issues like this with Comcast way to put the blame on someone else Virizon, way to go....

archer75

Actually it's true. Your ISP provides connectivity from them to you. Beyond their network they have no control. At least no direct control. A bad hop or router that they don't own they can't fix. They can only pass the info on to who does control it. And for those of us in Oregon, Verizon is no longer our ISP, frontier took over.

No ISP owns the entire network from your house to the it's final destination for who hosts that server.

We had quite a few issues with comcast this past year when we had them. Things happen sometimes. There could be a good chance that the recent quake caused some damage to the lines.

A traceroute easily shows you where the problem lies. The first hop or two are your house. The next one or two is verizons network, after that you are out on the internet going through various hops/router/hubs etc.

Hypertoken

Same issues here. Cant login to World of warcraft or access www.worldofwarcraft.com.

My nextdoor neighboor has Verizon DSL and I was able to use her connection to login to Warcraft... partialy, I was able to access an eastcoast server, however not my normal realm, which is west coast, and I was able to read forums.worldofwarcraft.com, not login. And I still was unable to access www.worldofwarcraft.com at all. The armory seems to be working fine.

I am having intermittent issues with other sites as well. I'm assuming the issue is related to CA sites

I ran tracert to us.logon.battle.net and got::

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

  1     5 ms     1 ms     1 ms  192.168.0.1
  2     4 ms     1 ms     1 ms  myrouter.home [192.168.1.1]
  3     9 ms    16 ms     7 ms  L100.PTLDOR-VFTTP-18.verizon-gni.net [98.108.131.1]
  4    11 ms    10 ms    11 ms  184.19.244.90
  5    27 ms    25 ms    24 ms  108.57.128.162
  6    28 ms    27 ms    27 ms  0.xe-1-2-0.BR3.SJC7.ALTER.NET [152.63.1.149]
  7    30 ms    32 ms    29 ms  uu-gw.sffca.ip.att.net [192.205.36.61]
  8    40 ms    39 ms    42 ms  cr2.sffca.ip.att.net [12.123.15.162]
  9    40 ms    39 ms    39 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    41 ms    39 ms    40 ms  mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
 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.

Which looks like a lot of the other tracert others have posted.

PLEASE VERIZON QUIT PUSHING THIS OFF ON BLIZZARDS SERVERS > MY BROTHER ON COMCAST HAS NO PROBLEM LOGING INTO OUR SERVER!!!!!!!!!

kyleforeman

I haven't been able to login to crystaltech.com hosted domains which are located in Arizona today.

Can connect to them fine using comcast.

lynnfredricks

This is also affecting DSL service. I cannot access critical parts of Intuit's website.

Any previous problem Ive had with verizion was solved in just a few minutes. But no matter what or who Verizon blames, Verizon is at fault for providing horrible customer service.

Check out my blog post about it here:

http://www.lynnfredricks.com/2010/04/05/verizon-internet-epic-fail-for-customers-in-oregon-lesson-in-bad-customer-support/

I can't really blame them if our traffic is being routed outside of their control. But I can blame them for:

- It taking over 1.5 hours to reach telephone support (speaker phone of course)

- The tech support guy being unable to locate this thread

- The tech support guy being poorly informed about the problem (notes here about network? He didn't know it)

- The Contact Us form, which selecting "Internet" + "Get Technical" support automatically forwards you to the FAQ page rather than allowing you to complete the form

Finally....

No system status page of any kind that I can find. If there is an acknowledged problem, then let people know about it, so we don't waste ours and Verizon's time taking useless phone calls.

Id really like to see some acknowledgement from Verizon about this.

You can see my miserable TraceRoute below.

TraceRoute to 12.149.161.229 [payroll.intuit.com]

Hop (ms) (ms) (ms)
IP Address Host name 1 20 11 18
72.249.0.65 - 2 37 15 21
8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net 3 27 15 15
4.69.145.140 ae-3-80.edge2.dallas3.level3.net 4 27 15 19
4.68.111.174 - 5 26 46 24
152.63.96.86 0.ge-1-1-0.xl4.dfw7.alter.net 6 58 56 58
152.63.117.25 0.so-2-0-0.xl2.sdg2.alter.net 7 68 56 51
152.63.114.249 509.atm7-0.gw4.sdg2.alter.net 8 Timed out Timed out Timed out

- 9 Timed out Timed out Timed out

- 10 Timed out Timed out Timed out

- 11 Timed out Timed out Timed out

-

Trace aborted.

kyleforeman

Ya, I wasn't going to hold out for the estimated wait time of 30 MINTUES!

Good to see others on here describing the same problems we are experiencing.

Faii

I have had similar issues with multiple sites via Verizon since early this morning. I am able to hit these same sites from a Qwest Internet connection. The common element seems to be Los Angeles and Verizon. Peering issue?

I had issues with AISO.net earlier, but that appears resolved now.

cp.fonality.com (Hosted VoIP PBX management)

traceroute to cp.fonality.com (74.115.96.11), 64 hops max, 52 byte packets
1 myrouter (192.168.1.1) 2.497 ms 0.747 ms 0.710 ms
2 l100.ptldor-vfttp-17.verizon-gni.net (98.108.130.1) 6.666 ms 6.824 ms 7.366 ms
3 184.19.244.30 (184.19.244.30) 9.732 ms 6.733 ms 7.042 ms
4 108.57.128.160 (108.57.128.160) 12.882 ms 11.081 ms 13.105 ms
5 0.so-7-1-0.xt1.sea7.alter.net (152.63.105.57) 12.562 ms 11.766 ms 13.076 ms
6 0.so-2-0-0.xt1.sea1.alter.net (152.63.104.225) 15.007 ms 14.437 ms 14.732 ms
7 pos4-0.br2.sea1.alter.net (152.63.106.9) 15.094 ms 16.228 ms 17.994 ms
8 204.255.169.22 (204.255.169.22) 14.755 ms 14.234 ms 15.695 ms
9 ae-32-52.ebr2.seattle1.level3.net (4.68.105.62) 26.438 ms 26.763 ms 18.734 ms
10 ae-1-100.ebr1.seattle1.level3.net (4.69.132.17) 15.961 ms 23.987 ms 17.096 ms
11 * ae-7-7.ebr2.sanjose1.level3.net (4.69.132.49) 37.997 ms 29.540 ms
12 * * *
13 * * *
14 xe2-0.cr01.lax01.mzima.net (4.71.136.2) 57.717 ms 39.752 ms 42.036 ms
15 * * *
16 fe1-fonality.cust.lax02.mzima.net (72.37.172.182) 42.434 ms 41.400 ms 44.958 ms
17 gi1-2.cs1.lax1.fonality.com (74.115.96.210) 42.596 ms 41.431 ms 42.419 ms
18 * * *

us.logon.battle.net

traceroute to us.logon.battle.net (12.129.206.130), 64 hops max, 52 byte packets
1 myrouter (192.168.1.1) 1.909 ms 1.080 ms 0.972 ms
2 l100.ptldor-vfttp-17.verizon-gni.net (98.108.130.1) 10.269 ms 11.250 ms 8.726 ms
3 184.19.244.88 (184.19.244.88) 7.789 ms 8.972 ms 7.357 ms
4 108.57.128.162 (108.57.128.162) 22.903 ms 26.921 ms 22.091 ms
5 0.xe-1-2-0.br3.sjc7.alter.net (152.63.1.149) 25.279 ms 26.711 ms 24.944 ms
6 uu-gw.sffca.ip.att.net (192.205.36.61) 27.567 ms 28.772 ms 27.453 ms
7 cr2.sffca.ip.att.net (12.123.15.166) 40.369 ms 38.797 ms 39.952 ms
8 cr2.la2ca.ip.att.net (12.122.31.133) 39.949 ms 36.819 ms 37.964 ms
9 * * *

azatru

I am a verizon FiOS customer who lives in Beaverton, OR and this is the results of my traceroute on my windows PC.

Tracing route to 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 8 ms 6 ms 7 ms L100.PTLDOR-VFTTP-18.verizon-gni.net [98.108.131.1]
3 9 ms 9 ms 9 ms 184.19.244.90
4 63 ms 24 ms 24 ms 108.57.128.162
5 30 ms 25 ms 26 ms 0.xe-2-2-0.BR3.SJC7.ALTER.NET [152.63.1.249]
6 31 ms 30 ms 31 ms uu-gw.sffca.ip.att.net [192.205.36.61]
7 * * * Request timed out.
8 40 ms 39 ms 39 ms cr2.la2ca.ip.att.net [12.122.31.133]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 40 ms 39 ms 39 ms 12.129.193.246
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * 12.129.211.36 reports: Destination net unreachable.

Trace complete.

I am able to connect to us.battle.net and WoW (game) using my Blackberry as an IP Modem, but the latency is so high i get disconnected in WoW rather quickly.

I attempted setting up a http tunnel through a West coast proxy server, and I can connect using Http-Tunnel, and a socks5 proxy server, but again, the latency is so high i get disconnected.

at first i thought my IP was baned for logging in and out so much over easter sunday, and then i came to realize its just that verizon NW customers cant connect.

way to go verizon..........2 hours on hold with tech support to be told its a blizzard issue, and I figured out myself its not a blizzard or a verizon issue, its the AT&T routers in/around San Jose, CA.

somegirl

Has anyone tried changing their DNS server to see if you get a different route that's not affected? I'm in Texas or I'd test myself.

prisaz

@somegirl wrote:
Has anyone tried changing their DNS server to see if you get a different route that's not affected? I'm in Texas or I'd test myself.

Not a bad idea. I am in Maryland and all works great here. Seems like a West coast thing. CA is having issue along with Oregon. Hey perhaps it's all those new IPads.

jaster386

Same issue here as well. I am using Verizon FiOS.

Here is my trace route.

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

1 1 ms 1 ms 1 ms myrouter.home [192.168.1.1]
2 8 ms 7 ms 10 ms L100.PTLDOR-VFTTP-24.verizon-gni.net [98.108.149.1]
3 8 ms 10 ms 8 ms 184.19.244.100
4 29 ms 28 ms 28 ms 108.57.128.162
5 32 ms 24 ms 28 ms 0.xe-1-2-0.BR3.SJC7.ALTER.NET [152.63.1.149]
6 30 ms 28 ms 28 ms uu-gw.sffca.ip.att.net [192.205.36.61]
7 42 ms 39 ms 38 ms cr1.sffca.ip.att.net [12.122.114.14]
8 38 ms 38 ms 38 ms cr1.la2ca.ip.att.net [12.122.3.122]
9 * * * Request timed out.
10 42 ms 39 ms 38 ms gar5.la2ca.ip.att.net [12.122.128.25]
11 39 ms 38 ms 39 ms 12.122.255.74
12 39 ms 37 ms 39 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
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 * 12.129.211.36 reports: Destination net unreachable.

Trace complete.

Some websites like www.penny-arcade.com can't be accessed either. The funny thing about it is, I can log into other realms and play, but not onto the ones where i have my main toon.

concrnd_netizen

Hey Lynn,

Interesting blog update. I'm also a FIOS user. I would make some comments about this to perhaps provide an interesting perspective, but I'd prefer to keep it private. I'd comment on your blog, but I don't see how to get an account.

Blitzurteil

Why private? Im sure everyone in this thread would enjoy some verizon insight at this point.

Oregonian

I am fios customer, not able to connect to www.regence.com from beaverton, OR

Tracing route to regence.com [204.80.161.103]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 9 ms 9 ms L100.PTLDOR-VFTTP-17.verizon-gni.net [98.108.130.1]
3 8 ms 7 ms 7 ms 184.19.244.30
4 13 ms 89 ms 12 ms 108.57.128.160
5 83 ms 12 ms 11 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
6 17 ms 16 ms 15 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
7 51 ms 14 ms 14 ms POS6-0.BR1.SEA1.ALTER.NET [152.63.105.17]
8 74 ms 14 ms 15 ms 192.205.33.121
9 * * * Request timed out.
10 * * * Request timed out.
11 59 ms 56 ms 58 ms cr1.slkut.ip.att.net [12.122.30.25]
12 * * * Request timed out.
13 54 ms 57 ms 56 ms 12.127.106.50
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

concrnd_netizen

Blitzurteil, I sent you and Lynn a private message. Feel free to respond privately if you want.

cyberfreak

I too am in Oregon and cannot connect to worldofwarcraft.com (or login)

Weird thing is if I use my verizon cell and tether my system then I can connect fine- so clearly there's something going on with FIOS/DSL.

Here's another tracert-

C:\tracert worldofwarcraft.com

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

1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 7 ms 9 ms 7 ms L100.PTLDOR-VFTTP-18.verizon-gni.net [98.108.131
.1]
3 9 ms 9 ms 10 ms 184.19.244.32
4 16 ms 15 ms 14 ms 108.57.128.160
5 15 ms 15 ms 14 ms 0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
6 16 ms 17 ms 17 ms 0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
7 17 ms 17 ms 17 ms POS6-0.BR1.SEA1.ALTER.NET [152.63.105.17]
8 16 ms 17 ms 17 ms 192.205.33.121
9 * * * Request timed out.
10 * * * Request timed out.
11 45 ms 44 ms 45 ms cr2.la2ca.ip.att.net [12.122.31.133]
12 * * * Request timed out.
13 45 ms 44 ms 45 ms gar5.la2ca.ip.att.net [12.122.129.25]
14 44 ms 44 ms 45 ms 12.122.255.74
15 48 ms 45 ms 44 ms 12.129.193.242
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.

concrnd_netizen

I'd be interested in seeing that same trace performed while you're tethered to your cell...

LunabeanMedia

I'm in Portland and I've had trouble connecting to a few sites today. First was Amazon...which is still on and off. Second is a site that we built and were going to launch today...of course we can't because of this, and the client is concerned as they don't understand why we can't connect to it. Oy.

Anyway, I did call Verizon and got a message saying they were aware of this problem, it's not their fault but that of an undisclosed third party, and it will be taken care of soon. This was several hours ago.

brianah

Lynn - I am unable to connect to your blog using that link. wonder if it is connected to the same problem.

Blitzurteil

Undisclosed 3rd party eh... {please keep it relevant} My guess is it will either A) never be fixed or it will magically start working again and we'll never know the true reason why.

azatru

Normal Verizon FiOS Traceroute: me to 12.129.206.130: Command enetered: tracert 12.129.206.130 >tracert.txt

Tracing route to 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 6 ms 6 ms 7 ms L100.PTLDOR-VFTTP-18.verizon-gni.net [98.108.131.1]
3 12 ms 9 ms 8 ms 184.19.244.90
4 25 ms 29 ms 24 ms 108.57.128.162
5 26 ms 27 ms 28 ms 0.xe-2-2-0.BR3.SJC7.ALTER.NET [152.63.1.249]
6 28 ms 29 ms 29 ms uu-gw.sffca.ip.att.net [192.205.36.61]
7 * * * Request timed out.
8 41 ms 40 ms 41 ms cr2.la2ca.ip.att.net [12.122.31.133]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 39 ms 39 ms 39 ms 12.129.193.246
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 12.129.211.36 reports: Destination net unreachable.

Trace complete.

Traceroute when Tethered to my Blackberry (T-Mobile): my cell to 12.129.206.130:

Tracing route to 12.129.206.130 over a maximum of 30 hops

1 723 ms 481 ms 341 ms 136.80.176.10.in-addr.arpa [10.176.80.136]
2 339 ms 359 ms 520 ms 181.80.176.10.in-addr.arpa [10.176.80.181]
3 298 ms 357 ms 299 ms 130.80.176.10.in-addr.arpa [10.176.80.130]
4 339 ms 444 ms 418 ms 169.6.176.10.in-addr.arpa [10.176.6.169]
5 348 ms 539 ms 341 ms 181.6.176.10.in-addr.arpa [10.176.6.181]
6 335 ms 375 ms 341 ms 209.96.176.10.in-addr.arpa [10.176.96.209]
7 332 ms 342 ms 376 ms 220.96.176.10.in-addr.arpa [10.176.96.220]
8 365 ms 299 ms 342 ms GigabitEthernet6-3.ar5.SEA1.gblx.net [64.215.25.129]
9 437 ms 373 ms 360 ms ge5-0-0-1000M.ar4.SEA1.gblx.net [67.17.73.41]
10 349 ms 341 ms 336 ms 192.205.33.237
11 772 ms 360 ms 400 ms cr1.st6wa.ip.att.net [12.122.146.46]
12 355 ms 317 ms 360 ms cr2.sffca.ip.att.net [12.122.31.194]
13 336 ms 320 ms 360 ms cr2.la2ca.ip.att.net [12.122.31.133]
14 347 ms 337 ms 358 ms cr84.la2ca.ip.att.net [12.123.30.249]
15 333 ms 317 ms 382 ms gar5.la2ca.ip.att.net [12.122.129.25]
16 369 ms 395 ms 365 ms 12.122.255.74
17 1346 ms 419 ms 377 ms 12.129.193.242
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 * 12.129.211.36 reports: Destination net unreachable.

Trace complete.

this tells me that the destination is unreachable either way, so it "could" theoretically be a blizzard problem, except that I am able to connect to us.battle.net/us.logon.worldofwarcraft.net through my blackberry browser.

what this DOES show for certain is that somewhere down in california, amongst all of the AT&T routers and switches is a machine, or server farm not working correctly.

Is it verizon at fault - no, not except for poor customer service *cough cough TERRIBLE customer service* Under no circumstances should a customer service rep EVER hang up on a customer for any reason.

Fenn

Yup its been out since last night. Portland, OR here. I thought it was just a general blip, but we are now nearing on 24 hours of connectivity loss.

Basically any site hosted on the lower west coast is unresponsive due to att.net servers it looks like. This includes not just ALL online games (I tried wow, eq1, eq2, warhammer and mabinogi), but several banks and business websites as well.

Here is my traceroute to us.logon.battle.net

traceroute to us.logon.battle.net (12.129.206.130), 30 hops max, 40 byte packets

1 Wireless_Broadband_Router (192.168.1.1) 1.212 ms 0.853 ms 0.683 ms

2 L100.PTLDOR-VFTTP-24.verizon-gni.net (98.108.149.1) 5.817 ms 4.763 ms 5.004 ms

3 184.19.244.42 (184.19.244.42) 4.958 ms 4.313 ms 4.838 ms

4 108.57.128.160 (108.57.128.160) 10.121 ms 9.336 ms 9.910 ms

5 0.so-7-1-0.XT1.SEA7.ALTER.NET (152.63.105.57) 10.638 ms 9.320 ms 9.961 ms

6 0.so-2-0-0.XT1.SEA1.ALTER.NET (152.63.104.225) 12.443 ms 12.008 ms 12.293 ms

7 POS4-0.BR1.SEA1.ALTER.NET (152.63.105.81) 12.509 ms 11.527 ms 12.719 ms

8 192.205.33.121 (192.205.33.121) 12.459 ms 11.923 ms 12.386 ms

9 * * *

10 cr2.sffca.ip.att.net (12.122.31.194) 42.168 ms 39.408 ms 39.977 ms

11 cr2.la2ca.ip.att.net (12.122.31.133) 41.683 ms 45.115 ms 39.274 ms

12 cr84.la2ca.ip.att.net (12.123.30.249) 44.550 ms 39.859 ms 39.900 ms

13 gar5.la2ca.ip.att.net (12.122.129.25) 39.765 ms 39.893 ms 39.948 ms

14 * * *

15 mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 144.212 ms mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 39.853 ms mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 162.340 ms

16 * * *

17 * * *

18 * * *

19 * * *

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *

29 * * *

30 * * *

lynnfredricks

@concrnd_netizen wrote:
Hey Lynn,
Interesting blog update. I'm also a FIOS user. I would make some comments about this to perhaps provide an interesting perspective, but I'd prefer to keep it private. I'd comment on your blog, but I don't see how to get an account.

Howdy,

You should be able to comment on my blog via the Facebook connector (if you have Facebook).

I was actually able to reach some pages by using kproxy, one of those anonymous proxy sites. That really makes me wonder about the claims of not being able to do something. Likewise, I use a lot of services in Europe and not one problem there. I have an application though I cant reroute through one of those sites or services so Im screwed.

But, it makes me wonder why if I can "retraffic" myself using an anonymous proxy site why Verizon isn't able to direct traffic through their system using another path, rather than the dead zone between here and California.

Blitzurteil

Most recent tracert...

Tracing route to 12.129.206.130 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 4 ms 4 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 23 ms 12 ms 14 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 11 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 42 ms 42 ms 39 ms gar5.la2ca.ip.att.net [12.122.129.25]
14 41 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.

Gam3r_Gal

I have been unable to connect to the WoW forums, fan art site and support site. Just recently I also found out that I have the same issue with hot topic.

Does anyone know the best way to keep updated on this issue?

SpankedAllDay

This has been the ONLY place i can connect to that has ANY info that I can find.

Thanks to those of you who have spent any time at all trying to contact service providers.

No Thanks to Verizon.

Blitzurteil

Be sure you are trying to get to the forums using http://forums.worldofwarcraft.com ... that is working for me, though nothing else is. There are a couple threads in the customer service forum, plus this one... thats really all there is.

yakyma

Yeah not even that works for me....and i cant log into my bank, or several other places still. Gave up on verizion after 45 mins on hold...i just wish we could get some kind of status update.

ElizabethS

Just a reminder folks that this a peer to peer support forum and as such, no Verizon tech employees are monitoring it. Occasionally some may participate as users, but the intent of the forum is to allow users to share information about Verizon prorducts and services, and solutions to problems they may have with them.

For technical issues you need to contact Verizon directly through the Contact Us feature on the main forum page.

John_Wolf

@ElizabethS wrote:
Just a reminder folks that this a peer to peer support forum and as such, no Verizon tech employees are monitoring it. Occasionally some may participate as users, but the intent of the forum is to allow users to share information about Verizon prorducts and services, and solutions to problems they may have with them.

For technical issues you need to contact Verizon directly through the Contact Us feature on the main forum page.

Yeah that works like a champ. Have YOU actually tried to use that link? I get this when I hit it:

We're sorry....
We are not able to process your request. To continue, please select
one of the following options:

I can't even get to sites that I was able to get to last night/this morning. It appears that the whole issue has gotten worse.

ghecko

That contact us link is a joke. It won't connect to chat support, it won't launch an email application, and it won't give me the phone number. Verizon customer service is easily the worst I've ever dealt with. I spent 40 minutes on hold to request a new box to get yet another one that cuts audio in and out on non-HD channels. But that is all beside the point, I don't play WoW, but am highly frustrated with this situation. I am unable to reach any websites based off the lower west coast. My tracert seems to lose connection in Phoenix. I am wondering if it's not based on the earthquake down in the area and it has hurt the backbone verizon uses.

Hypertoken

So.... still no workey =/

Hey Verizon clear your DNS cache and your routing tables for 12.129.193.*

Here is the tracert from my Verizon FiOS:

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

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     9 ms     7 ms     6 ms  L100.PTLDOR-VFTTP-18.verizon-gni.net [98.108.131.1]
  3    12 ms    10 ms     9 ms  184.19.244.90
  4    31 ms    24 ms    24 ms  108.57.128.162
  5    29 ms    26 ms    27 ms  0.xe-1-2-0.BR3.SJC7.ALTER.NET [152.63.1.149]
  6    32 ms    29 ms    30 ms  uu-gw.sffca.ip.att.net [192.205.36.61]
  7    41 ms    39 ms    39 ms  cr2.sffca.ip.att.net [12.123.15.162]
  8    41 ms    39 ms    39 ms  cr2.la2ca.ip.att.net [12.122.31.133]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    43 ms    41 ms    42 ms  mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
 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.

And this is from my neighbor on her Verizon DSL:

Tracing 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    14 ms     8 ms     7 ms  L100.PTLDOR-VFTTP-18.verizon-gni.net [98.108.131.1]
  3    15 ms    17 ms    14 ms  184.19.244.32
  4    23 ms    16 ms    15 ms  108.57.128.160
  5    19 ms    16 ms    17 ms  0.so-7-1-0.XT1.SEA7.ALTER.NET [152.63.105.57]
  6    18 ms    18 ms    17 ms  0.so-2-0-0.XT1.SEA1.ALTER.NET [152.63.104.225]
  7    27 ms    18 ms    17 ms  POS4-0.BR1.SEA1.ALTER.NET [152.63.105.81]
  8    22 ms    19 ms    19 ms  192.205.33.121
  9    48 ms   189 ms   201 ms  cr1.st6wa.ip.att.net [12.122.146.46]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    48 ms    44 ms    46 ms  12.122.255.74
 15    48 ms    47 ms    49 ms  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
 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.

Hope it helps....

BTW... I'm able to connect to some of the sites like http://forums.worldofwarcraft.com with the DSL connection, and not the FiOS connection.

Hypertoken

According to http://www.wowwiki.com/US_realm_list_by_datacenter

Los Angeles datacenter

Please note that the Los Angeles servers are located in 2 separate datacenters, and as such the battlegroups are grouped oddly.

When doing a traceroute to servers in Los Angeles, the last hop should be one of the following:

12.129.193.242
12.129.193.246

Both of these IP addresses are the last hop on my tracert's

Gam3r_Gal

It'd be nice if a moderator of this forum could contact a higher up about this problem, seeing as how a fair amount of us are unable to contact them.

wrohdejr

i am in gresham and i can not connect to evony.com i can connect to craigslist and wow and newegg but can not connect to evony.com here is the tracert

Tracing route to evony.com [64.156.194.11]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 8 ms 6 ms 7 ms L100.PTLDOR-VFTTP-32.veriz
.1]
3 9 ms 6 ms 7 ms 184.19.244.54
4 12 ms 11 ms 13 ms 108.57.128.160
5 17 ms 16 ms 17 ms 0.so-7-1-0.XT1.SEA7.ALTER.
6 14 ms 39 ms 16 ms 0.so-6-0-0.BR1.SEA7.ALTER.
7 15 ms 14 ms 13 ms 206.111.7.125.ptr.us.xo.ne
8 23 ms 19 ms 16 ms te0-3-2-0.rar3.seattle-wa.
93]
9 * * * Request timed out.
10 41 ms 41 ms 41 ms te-3-0-0.rar3.la-ca.us.xo.
11 * * * Request timed out.
12 * * * Request timed out.
13 42 ms 42 ms 43 ms 216.55.27.6
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.

Blitzurteil

I hope this gets fixed fast... I just logged into Star Trek: Online... Help.

kyleforeman

Everything is working for me now, looks like they fixed the issue. 🙂

Update 9:47. Sites are not working again.

yakyma

For all of you WoW gamers out there...i am in the hillboro area and just got logged into wow, and the forums seem to be back up for me. I havent checked the other sites i couldnt connect to, and im a bit laggy, but it seems to be comming to a resolution for now. Good luck.

John_Wolf

@Blitzurteil wrote:
I hope this gets fixed fast... I just logged into Star Trek: Online... Help.

LOL, I just checked and the blizzard domains appear to be up, for how long, who knows. I got battle.net to respond about an hour ago and it died before I could refresh it. Let's hope this latest success is a little more permanent.

Edit: and just like that, down again 😞

mikeflynn23

I called the Oregonian and the Tech Reporter is going to respond in the morning. When I contacted the news desk they said "I don't see anything on the Verizon site mentioning a problem." I replied "That's the whole point." I couldn't even log into the Verizon site to find out A. What's going on? B. When it will be fixed? I just find it so frustrating they say that you need to report problems to customer service when you can't contact them as they are online and can't access the web site. Then for the people we pay roughly $1200 a year for cable/internet to say it's not their problem! I also let paper know they are losing revenue due to ad's not seen, and a fantastic expose idea on where the money your monthly bill really goes since they only buy time/access on other networks which they can't "help you with".

jbbrown

To me it seem to be a communication between the two network, check all naming services and other middle services. I trace routed from both computer and Iphone and both providers use different naming services.

Looks like there is an issue at ALTER.NET some where, might be worth looking at.

lynnfredricks

@ElizabethS wrote:
Just a reminder folks that this a peer to peer support forum and as such, no Verizon tech employees are monitoring it. Occasionally some may participate as users, but the intent of the forum is to allow users to share information about Verizon prorducts and services, and solutions to problems they may have with them.

For technical issues you need to contact Verizon directly through the Contact Us feature on the main forum page.

Hi Elizabeth,

If you read my blog you'd know that I (and Im sure others) tried to do exactly that.

There are two drop-down menus that you use on the page. When I selected BOTH Internet and Get Technical Support options, the page's script action takes you back to the the Help landing page in a kind of weird loop. I couldnt even fill in the explanatory field.

The technical support person I spoke with after that 1.5 + hour wait could not even locate this thread. When I offered to send him the URL, he flat out told me that, at least at his level, they had not direct access to internet services like outside email. He also admitted that the long wait I experienced was abnormal and he didnt understand why the queue was so long.

Some service providers provide ongoing network status indicators so that customers are assured someone is looking into the problem and also, provide the company with respite from a constant barrage of expensive support calls. It is too bad there isn't such a thing we can access.

jbbrown

Ok, question here.

Seems to me that main website and forums site use the address and port, but you can access only one or the other. All traces still point to the same common address.

So with the internet connection is it a port issue or the whole connection?

Did some just add a rule to the system not to allow connect to one or more areas?

It just has me bugged why some still have access at all, even when the connection to the backbone and the destination of the backbone are working just fine.

I now see a new set of connection pop up from ATT atm, maybe it fixed

JohnMcA

Started working for me again at 10:43. All unavailable sites (my bank, craigslist, etc.) now seem to work atm. only 24+ hours! Verizon, why did you not route around the issue once your customers started complaining? Way to go.

ssgoodri

Yay! Finally can get into WoW and on myspace.com.... "knock on wood" that it stays up and running!

Fenn

And its down again 😕

Hypertoken

It was working for about an hour and a half or so..... now its not again.

Smiley Sad

Honetsugi

Different MMO, same/similar issues. Two friends and I are having issues connecting and staying connected to FFXI. Started at about 9PM Sunday night (04/04/2010) and continued through last night. Seeing same issue with it being fine for a little while then getting disconnected.

Also having some problems with Aion, though not as bad.

schwarztrader

I just got off the phone with Verizon Fios billing to discuss the matter with them and ask for them to "at least" compensate me for the loss of service since I am a Fios business customer. I don't want to go into specifics, although Verizon definitely went above and beyond to make me happy in regards to this aggravating issue.

I highly suggest all of you call them (even if you have to wait the 30-60 mins) to get to the right place so they can rectify your situation.

Hypertoken

Seems to be up again....we'll see how long it lasts... Smiley Mad

azatru

WoW just went down again, like 30 seconds ago 11:36pm PST

Iyenrith

Yup... down again as of 2-3 minutes ago (11:36PM)

Child Item