Request for information: ISPs and P2P throttling

[Kaeshi]

- Name of ISP: City10
- Country of Residence: Brazil
- When does the problem occur: All the time while playing, lagspikes.

Started just after the first maintenance update after patch 2.3 was released. The game was running smoothly and now I just can't duty or even quest sometimes.

[Hachuurui]

Verizon FIOS
USA, Havertown, PA
Constantly since Patch 2.3. Game is nearly unplayable.

[Rattleh3ad]

Verizon FIOS
Rhode Island, USA
Always happens at night time, during prime time.

I've run numerous connection tests and they all show okay results.

[Dogz1]

Verizon FIOS
California, USA,
Prime Time (13:00 - 21:00)

[Legardi]

Name of ISP: Verizon FIOS
Country of Residence: California, USA
When does the problem occur: Any time between 12:00 PM to 6:00 PM, and persists until 10-11 PM.

[Venaire]

Name of ISP: ATT Uverse
Country of Residence: Wisconsin, USA
When it occurs: Always, Sending and Recieving constantly rollercoasters from 0 to 3000+ and back.

[KouPuff]

Name of ISP: DSL Extreme
Country of Residence: California, USA
When it occurs: Always. I started this game about 20 days ago, and I've yet to experience more than a few minutes (Max: 5 minutes) of smooth gameplay. I am noticing that it seems to be mostly in combat, though.

[Ranmyaku]

Name of ISP: Fidelity Communications, LTD
Country of Residence: Oklahoma, USA
When it occurs: Intermittently throughout the night the connection will drop to receiving 0. Nothing else is having issues (100 megabit down connection stays steady with everything else)wd

[elvynd_]

Hi,

I've been experiencing CONSTANT lags/delays (on Carbuncle Server) after a recent update and this has seriously affected my quality of play recently. It was fine so far until about 1-2 weeks ago where I've been experiencing upwards of 200-500ms (sometimes even 1k) of latencies instead of ~80ms that I've experienced in the past.

More details:

ISP: ViewQwest
Country: Singapore
Frequency: Always, all the time as long as I am connected.

I have also raised this issue with my ISP, (with a tracert) and they have gotten back to me regarding this. They mentioned that all the forward routing is done directly through NTT, and that the return routing is 'messed up' so I will have to take it to you guys to communicate with NTT for the return route optimization. On their end, they have tried re-routing several times but they all show the same return route via a further provider, therefore it's outside of their control.

Here's a copy of the traceroute to my server (Carbuncle):

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Elvynd>tracert 124.150.157.32

Tracing route to 124.150.157.32 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms 1 ms 1 ms 192.168.0.1
3 2 ms 1 ms 1 ms fnet1-f104-access.vqbn.com.sg [202.83.104.1]
4 2 ms 1 ms 1 ms V-TR-EQX-01.vqbn.com [202.73.37.232]
5 88 ms 2 ms 2 ms switch.equinix.vqbn.com [202.73.47.6]
6 * * * Request timed out.
7 228 ms 226 ms 225 ms 116.51.26.165
8 218 ms 219 ms 221 ms as-3.r21.sngpsi02.sg.bb.gin.ntt.net [129.250.3.5
7]
9 218 ms 219 ms 216 ms as-6.r23.tokyjp01.jp.bb.gin.ntt.net [129.250.4.1
50]
10 216 ms 218 ms 221 ms ae-9.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.3.1
59]
11 236 ms 231 ms 234 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
162]
12 241 ms 245 ms 251 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
13 249 ms 305 ms * 219.117.144.66
14 197 ms 193 ms 196 ms 219.117.144.53
15 185 ms 185 ms 191 ms 219.117.144.41
16 185 ms 186 ms 185 ms 219.117.147.194
17 228 ms 227 ms 223 ms 124.150.157.32

Trace complete.

C:\Users\Elvynd>tracert 124.150.157.32

Tracing route to 124.150.157.32 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 10 ms 1 ms 11 ms 192.168.0.1
3 2 ms 2 ms 1 ms fnet1-f104-access.vqbn.com.sg [202.83.104.1]
4 2 ms 1 ms 2 ms V-TR-EQX-01.vqbn.com [202.73.37.232]
5 * * * Request timed out.
6 * * * Request timed out.
7 183 ms 183 ms 183 ms 116.51.26.165
8 183 ms 183 ms 183 ms as-3.r21.sngpsi02.sg.bb.gin.ntt.net [129.250.3.5
7]
9 183 ms 183 ms 184 ms as-6.r23.tokyjp01.jp.bb.gin.ntt.net [129.250.4.1
50]
10 183 ms 189 ms 184 ms ae-9.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.3.1
59]
11 185 ms 185 ms 184 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
162]
12 184 ms 184 ms 184 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
13 185 ms 185 ms 185 ms 219.117.144.66
14 221 ms 218 ms 221 ms 219.117.144.53
15 248 ms 243 ms 244 ms 219.117.144.41
16 246 ms 240 ms 239 ms 219.117.147.194
17 237 ms 238 ms 239 ms 124.150.157.32

Trace complete.

This issue has been bugging me constantly from 1-2 weeks ago every second on my game time, so I hope your guys can resolve this ASAP. Thanks!

Edit: The ridiculous thing is that I have raised a support ticket with SE Support, Ticket No.: 4046382 and what I've received is a "If you're unable to connect, try this this and that" kind of a message. I mean do you guys even read the issues that we raise using the support e-mails or are your tech support staff paid to copy-and-paste work? It was immediately obvious that my issue (and also what some others here have experienced) is not that we're unable to connect, but that we're experiencing increased latency and lag simply because SE's server's return network route aren't optimized, please don't assume we can be simply brushed off with a copy-and-paste message and expect us to accept it as it is. Would appreciate if you guys can do something about it and not just give generic replies, I mean what kind of a support is that?

[skAnarky]

Hi there,

-Distributel (uses infrastructure of Rogers)
-Canada (toronto)
- As far as I can tell at night, but I don't play often during the day.
- Havent contected my ISP yet, will update if I do