Category: Technology Author : Duncan Riley Posted: December 19, 2008
Tags : comcast, comcast customer service, comcast outage, comcast phone number, comcast world of warcraft, world of warcraft
Comcast issues block World of Warcraft Users

Issues with the Comcast Cable network are blocking and disconnecting users of popular online game World of Warcraft.
It’s not clear at the time of writing what was causing the issue, with a notice on the World of Warcraft forums noting only that Blizzard was aware of the issue, and was attempting to contact “appropriate sources” for further information. There may be more details on this thread, but at 133 pages long at the time of writing it’s difficult to tell. The thread also notes that Verizon customers may also be affected.
The news comes on the same day widespread internet issues were reported across Asia and the Middle East after three major cables were severed, however despite Blizzard’s strong Asian presence it has over 200 servers (“realms”) located in the United States for local World of Warcraft users.
Comcast’s Phone Number for those wishing for direct details is 1-800-COMCAST (1-800-266-2278).
More if we get it.




![Cloaked UFO Spotted Near Mercury Is Actually Mercury [Video]](http://www.inquisitr.com/wp-content/2011/12/cloaked-ufo-100x100.png)


Dec 20, 2008
This is NOT a Comcast issue. The troubleshooting data from our customer base and in the WoW forums consistently shows latency introduction in Savvis / AT&T hops. You will see this in the traceroutes provided by people. Latency has not been demonstrated coming from any parts of the Comcast network. The forum data also shows similar performance problems with several other providers customers trying to reach Blizzard, such as Verizon. Please correct the story.
We invite our users to post in our support forums at .
Jason
Comcast
National Engineering & Technical Operations
Dec 20, 2008
If ComCast blocks me from World Of WarCraft,than than Comcast will have to go!
Dec 20, 2008
We're not blocking you…
Dec 20, 2008
For as much as Comcast has screwed me over (including damaging our neighborhood's road by running cable underneath improperly), JL is right. I'm no network engineer but I can tell from my traceroute that it was an AT&T issue.
With that said, what's with the naming convention, Comcast? “…wv.bad.comcast…” “…va.bad.comcast….” “md.bad.comcast….” Just validating what we knew all along?
Dec 20, 2008
“There may be more details on this thread, but at 133 pages long at the time of writing *it’s easier to blame Comcast*. The thread also notes that Verizon customers may also be affected.”
Fixed that for you
Dec 20, 2008
if they close world of warcraft il have nothing to do at all and im lvl 80!
Dec 22, 2008
Relax guys its not Comcast's or Blizzard's fault. There is a third party server midway between Blizzard and Comcast's servers.