Red spike lag back with a revenge since 05/24 patch

Seemingly hitting only a few instances/zones, and not always the same for the (unfortunately for us who are affected, few) players who are hit by this lag, but it's there.

I know the official answer on this was "it's some data center between our servers and your internet provider and we can't do anything about it", but how come this lag always comes back *right* after a patch?

I've seen the pattern maybe a dozen times now, as I play during the day and often get to play right before a patch. Before patch - everything fine. After patch - red spikes all over the netgraph. It's hard to believe that evil noname data center somehow always start lagging right after City of Heroes patches, but hey.

I'm not yelling at the devs or anything, as a matter of fact this lag was introduced with the I8 release, so the people responsible for it may not even be in the current team... Just venting.

Now in the tradition of "I lag!" threads, feel free to post that the game is smooth for you and that you have absolutely no problem, as always.

I've had these problems recently as well.

On Sunday I was going to join the MA Superteam on Virtue to play som AE arcs in the RWZ. The RWZ zone was fine, but as soon as we entered a mission my netgraph turned into a blood-splattered hedgehog. Outside of missions I saw receiving/sending values of 2500-5000, inside missions it surged to 10000-15000. I don't know what these numbers signify or if they have anything to do with the way the netgraph had red spikes all over it, but there we go.

/signed

Please do something about the red lag spikes. The game is nearly unplayable right now, and it all started on 24/5, right after the patch.

Edit: EU player here

The french board has a topic discussing this specific issue (that many french players seem to have), we gather some data, but no one at NC seems to care. As far as I'm concerned, I tried on different locations, different computers, diffrent ISPs, the result is always the same : red spikes, crashing on BAF.

So yeah, fix it. Please. Quickly. Pretty please.

Something strange just happened to me, related to this. I was on a BAF where my netgraph was solid red with a few bits of green here and there (in other words, terrible lag). My client crashed. When I came back, I rejoined the BAF and... The lag was gone.

I've also seen times where other players report the red spike lag, whereas it's smooth for me.

So it's seemingly not tied to the instance alone but to the individual connection? Would have to test more, but if restarting the client is enough to get rid of the lag for a particular instance, that could alleviate the problem.

I am indeed living in France, and it seems the lag is actually much worse than the usual red spike lag, with huge blocks of red as seen in the screenshots posted in the french topic ; not to mention I haven't seen US players mentioning unusual lag. Meh. Seems like we're screwed, as always they'll pretend it's something on our end, even though the connections used worked perfectly fine before 05/24 and work perfectly fine for everything else.

French thread if you're interested. Usually, restarting the game, or even just zoning could resolve the issue. It doesn't work for everyone though (me for example).

We petitioned it, made a thread about it, asked Avatea about it, and all we got is "Check with your ISPs". Yeah, I guess every french ISP decided to add red spikes for half of their CoH players following 5/24 patch.

Or, depending on how the worldwide ISPs route connections, you guys could be getting that region routed through a faulty data-center. Just a thought.

I am not French and the game has been completely unplayable since this update. I am fighting lag spikes, loading time issues, and not responding signs. If this does not get fixed I will have to drop this game after 7 years and not because of desire but because of a tech bug?

I live in norway and I'm having the same issue. For the last week, red spikes are frequent, but recently (when everyone else on the network isn't "active") it clears out a while after leaving wentworth. Wentworth seems to overload some connection somewhere *shrug*