FIX THE LAG and 90000 Errors petition!

[Ravnis]

Honestly, I have had zero lag until patch 2.1 and their latency fix. prior to that I made 3 hops to their server, 3 , with a total time of 15ms. Now after the patch I make 15 hops and time out or throttle in between. Reality is they changed it to allow people who were getting bad transmissions to have an easier time and rolled the others over to the bad.

I live in NJ, on FioS, 50down 35up. Ping any server on any game in at most 50ms. I ping Korean servers in 73ms. Montreal, which is maybe 5 hours away is 315ms now.

I picked up a few latency fix programs and now it seems my BEST route is to Los Angeles and then over to fix my packet movement. It's obviously not their fault that suddenly ping routes completely changed for most players after a patch to fix latency.

Reality is the change has caused serious problems for quite a number of players and needs to be addressed. Whether you see it as our ISP or theirs; something is breaking down our packet routes AFTER a patch to fix these issues.

If there is something that changed it it's pretty obvious when all the problems started simultaneously after one change. I understand how the internet works, but there is something more than a little suspicious about these events, when nothing has changed for any other game I have played.

[Raist]

Honestly, I have had zero lag until patch 2.1 and their latency fix. prior to that I made 3 hops to their server, 3 , with a total time of 15ms. Now after the patch I make 15 hops and time out or throttle in between. Reality is they changed it to allow people who were getting bad transmissions to have an easier time and rolled the others over to the bad.

I live in NJ, on FioS, 50down 35up. Ping any server on any game in at most 50ms. I ping Korean servers in 73ms. Montreal, which is maybe 5 hours away is 315ms now.

I picked up a few latency fix programs and now it seems my BEST route is to Los Angeles and then over to fix my packet movement. It's obviously not their fault that suddenly ping routes completely changed for most players after a patch to fix latency.

Reality is the change has caused serious problems for quite a number of players and needs to be addressed. Whether you see it as our ISP or theirs; something is breaking down our packet routes AFTER a patch to fix these issues.

If there is something that changed it it's pretty obvious when all the problems started simultaneously after one change. I understand how the internet works, but there is something more than a little suspicious about these events, when nothing has changed for any other game I have played.

That's most likely because either your ISP or their partner is routing you differently. You may have changed routing partners, or you may be coming into a different entry point or something else that is causing you to route differently along either your ISP's segments or their partner's (or maybe even both).

Before my last routing change, I was using Cogent to get into Canada and it was 16 hops. They changed me to Level3 back around the middle of the month, and since then I have been hitting 19 hops. All those changes came BEFORE the Ormuco segments. Those hops have remained the same, at 3 hops once I got there: 192.34.76.10, then 192.91.189.242, then the final IP for the game server that I was using at the time (.74, .31, and lately .25).

The only thing SE has been changing is that final IP--everything else that has changed has been either in my TWC/RR segments, or their routing partner. This has been changing every 2-3 weeks since near the end of September when I first fingered Cogentco as the culprit and contacted my ISP's Network Operations Center with tracerts to get them to investigate it. Since then, TWC has been bouncing me all over different corridors from the DC/VA area, to the Great Lakes, to LA, up through Seatle, down to Atlanta---been all over the map with my routing, and used TATA, Cogent, and now Level3. All this time, it's been consistent at the Ormuco/SE end, and their latency has been pretty consistent at their hops (within about 20-30 ms variance). But the latency along the way has been gradually improving. My worst hops hover around the 130ms during primetime now--it was hitting the 300 mark frequently when we first started. Now, if we could just shave off some more of the packet loss it would be good to go... still likes to flirt with the 20% line periodically. A lot better than the 40+ we were tracking, but still a lot of room for improvement.

The point is... all the changes in routing aren't coming from SE, per se. SE may have changed your endpoint IP (mine changed from .31 to .25), and that may have resulted in some changes in your route--but SE didn't make that change. The ISP's that are carrying your data have negotiated those route changes based on specific traffic characteristics and what they've determined is best for getting you from point A to point B.