Request for information: ISPs and P2P throttling

[Defuge]

Verizion FIOS

Baltimore, MD United States

Has started happening the day immediately after the ISP Maintenance (before the patch) starting at about 8pm EST EVERY DAY SINCE I get insane lag and packet loss in this game and this game only.

[Reinth]

China Telecom

Beijing, China

The same issue as everyone who posted here. I have even changed ISP 3 times, feeling horrible for spending so much money on internet just to get a stable connection to play this game, yes this game only. I'm on Tonberry Server.

[ThinkPInk]

Verizon Fios
Maryland.

This lag has been terrible since the 1st 3.0 patch. It started out as just lag in dungeons making most fights unbearable. Literally freezing and then jumping ahead. Now after this NA ISP maintenance I'm lagging in the open world. The game is becoming unplayable.

[Rythulian]

Virgin Media
UK (South East England)
Problem occurs throughout the day with no specific times.

[Bentozzi]

UPC
Poland
Do something!

[ShutupCup]

ISP: Verizon FiOS
Country: Maryland, USA
When: Occurs anytime but most frequently during peak time, instances, and large group fates
Reference: N/A

[Noxica]

ISP : Numéricable
Country : Tours, France.
When: Since patch 3.05. I had no problems at all since you released it.

[Sugis]

- AT&T Uverse
- United States (California)
- Peak time and sometimes in the early morning.

[Kiteu]

- Bright House Networks
- USA
- Peak Hours

[Palladion]

- verison fios
- usa (texas)
- all throughout the day. it's a hit or miss if i get lag spikes in the late evenings, which is when i'm forced to play since its damn near unplayable for me during the afternoon and peak hours in the late afternoon

i've pinged the north american servers and 1 of 4 attempts i time-out everytime. i thought changing from a wired to a wireless connection would help since support loves to ask that question but to no avail: i'm still getting lag spikes and 0 received packets in-game consistently. is this thread just a way to contain these complaints instead of address them? i've had this problem since 2.0 launched.