City Of Heroes: Connectivity Issues Answers (for Verizon and some)

Well this has even effected me so I'll cut the chit chat so you can read what Case from NCsoft Tech Support had to say:

We, here in Tech, have received multiple submittals from customers (you all ) that have either Comcast or Verizon as your ISPs &/or are situated in & around "the East Coast" of North America (though not specific to).

I have verified that there have been issues with Comcast's Backbone Services. This occurred approximately @ 4:30PM CST (04.07.05). We were given the "All Clear" ~ (Comcast stating that this issue was resolved) ~ @ Exactly 5:23PM CST (04.07.05).

Unfortunately, they were not specific in regards to what happened. Though, since this issue was directly related to Comcast's Backbone Services, it is logical to presume this is affecting any network/ISP that relies on Comcast's servers for proper direction. I suspect that Comcast's routing tables needed to be updated after their issue was resolved. This would attribute to some people's lengthy connectivity issues. Shado_Shryke is exactly right in stating that this is a situation of patience. It's simply a matter of time for the routers to re-propagate the correct information. Of-course when an issue like this occurs the results are frustrating.

Your best chance of resolving this issue if you are not included in the immediate "downed" network would be to flush your Windows DNS Resolver Cache. Of course if you are a customer of an ISP that has the network outage or relies on the "out-ed" network due to being a subsidiary of the faulting network, you will, more than likely, simply have to wait out the trouble.

To Flush your, DNS:

Windows XP/2k

Start>Run>CMD
At the Command Prompt type "ipconfig /flushdns" with out the quotes
Windows ought to report back "Successfully flushed the DNS Resolver Cache."

Example:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:>

Often times you may need to flush your resolver cache several times to resolve the issue. I recommend minimizing the Command Prompt dialogue box, between tries.
Windows 98/ME

Start>Run>Command
At the Command Prompt type "ipconfig /flushdns" with out the quotes
Windows ought to report back "Successfully flushed the DNS Resolver Cache."

Any questions please let me know...

Oh well hopefully this conenctivity issue will be fixed shortly everywhere.