Request for information: ISPs and P2P throttling

[SionDurant]

SE, if this isn't fixed after today I'm finding a lawyer. You have an obligation to maintain a service you've taken money from people for, and you're not fulfilling it. This latency thing is simple, you have messed up certain NA players and they're getting way too many hops. You keep locking threads wherein educated individuals keep pointing out raw factual data and comparisons between JP/NA/EU servers.

In every test I've seen JP servers plot just fine in a ping test.

Also I've called my ISP Brighthouse Networks and they say I have absolutely no packet loss, and that they are absolutely not throttling my connection, or classifying you as any kind of malicious P2P, so you can stop with that lie.

My average test results across all sites:
15 MS 46 MBPS Down 2.36 MBPS Up.

This has been the absolute Worst experience I've ever had trying to play an MMORPG. Take a lesson from Bluehole studios with Tera Online, they let issues like this linger and it killed their game before they could get around to addressing the content gap.

ps. Inferring that ISP's are the source of your issues can lead to serious repercussions, as many large providers would take this as slander in the right dosage and take you to court over it. Not to mention this all is very bad customer service to us.

I don't care about new content, I want working servers that we all can enjoy.

[Skab]

Update: Seemed fixed last Sunday (as others are reporting), and now it's back, maybe even worse than before. Lucky if I can stay on for 5 minutes, VPN or not. All other sites/programs work fine - speed test (ran during a disconnect) yielded 32mbps down, 7 up.

[Neutronstar1989]

BT
United Kingdom
Used to occur during evenings but now happens in the late morning too

[Jacin]

Verizon DSL, Baltimore, Maryland

I had posted in here previously, reposting to add some ping and tracert info.

Lag started Friday, has continued since then. I can be all by myself with no one in visual range, I can be solo questing and fighting a mob, sitting in town, or in the Duty Finder and I will lag. At all times during the day. Got 90000'd a couple of times Friday in addition to the lag, but no disconnects since then, just strange inconsistent lagging. *VERY* small periods of normal gameplay, and then BAM.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Jason>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=60ms TTL=53
Reply from 184.107.107.176: bytes=32 time=138ms TTL=53
Reply from 184.107.107.176: bytes=32 time=77ms TTL=53
Reply from 184.107.107.176: bytes=32 time=63ms TTL=53

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 138ms, Average = 84ms

C:\Users\Jason>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=60ms TTL=53
Reply from 184.107.107.176: bytes=32 time=61ms TTL=53
Reply from 184.107.107.176: bytes=32 time=61ms TTL=53
Reply from 184.107.107.176: bytes=32 time=61ms TTL=53

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 61ms, Average = 60ms

C:\Users\Jason>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 33 ms 34 ms 31 ms 10.4.42.1
3 32 ms 64 ms 34 ms G0-9-4-0.DLLSTX-LCR-22.verizon-gni.net [130.81.1
94.190]
4 33 ms 33 ms 33 ms so-1-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.2]
5 72 ms 34 ms 33 ms 0.ae1.BR3.IAD8.ALTER.NET [152.63.7.81]
6 50 ms 50 ms 50 ms ix-20-0.tcore1.AEQ-Ashburn.as6453.net [66.198.15
4.53]
7 60 ms * 67 ms if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1
]
8 66 ms 67 ms 61 ms if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.1
38]
9 59 ms 62 ms 60 ms if-4-4.tcore2.NYY-NewYork.as6453.net [66.198.111
.18]
10 60 ms 61 ms 67 ms if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226
.13]
11 62 ms 82 ms 62 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
12 63 ms 228 ms 153 ms 64.86.31.42
13 61 ms 62 ms 109 ms te8-3.dr10.mtl.iweb.com [67.205.127.238]
14 62 ms 60 ms 60 ms 72.55.128.44
15 64 ms 63 ms 62 ms 184.107.107.176

Trace complete.

EDIT: Saw mention of a program called Ping Zapper in a locked lag thread, tried it, and it does indeed work (at least for me). Downloaded, installed, and set up. 30 mins straight of lag-free playing. Logged off and closed Ping Zapper, and then logged back on. Immediate lag. Ran Ping Zapper again, launched XIV, lag-free. It's on a trial account at the moment, which limits you to 1 hour of game time before it stops working. I don't know if that's "1 hour, stops working, close program and reopen and it works fine", or "1 hour every 24 hours". I'd assume the latter, but I don't know. Don't have the time to test the trial account limit because I need to get some sleep before I go to work. But Hallelujah, it works flawlessly. If I lagged during my time using it, I could not tell. I'll see if tonight's maintenance fixes the problem, and if not, I'll be buying some prepaid Ping Zapper time tomorrow. My RAAAAAAAAAGE at having to possibly pay for a 3rd party tunneling program to make this game playable is mostly tempered by the fact that it's pretty damned cheap, and I'm still on my free time. Of course, tomorrow, if the lag persists outside of using it, I'll be dropping the four bucks for 30 days of Ping Zapper time; however, I can't say that I'll be completely happy doing it.

[Replica9]

- Name of ISP : Omantel
- Country of Residence : Oman
- When does the problem occur : Always , cannot log in , shows errors 2002 (can connect fine with vpn)

[Yuengling]

Name of ISP: Verizon FiOS
Character name: Yuengling Light
Country of Residence: Fairfax County, Northern Virginia, United States

Same issue. Constant 5 second freezes.

I've isolated the issue down to one of these hops:

3 28 ms 14 ms 10 ms G0-9-2-6.WASHDC-LCR-21.verizon-gni.net [130.81.97.106]
4 9 ms 8 ms 8 ms ae1-0.RES-BB-RTR1.verizon-gni.net [130.81.209.206]
5 11 ms 12 ms 11 ms 0.ae5.XL1.IAD8.ALTER.NET [152.63.8.121]
6 9 ms 8 ms 8 ms 0.xe-10-0-1.GW9.IAD8.ALTER.NET [152.63.33.161]
7 * 14 ms 14 ms tinet-gw.customer.alter.net [152.179.50.30]
8 41 ms 39 ms 37 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 41 ms 37 ms 40 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 47 ms 41 ms * 192.34.76.2
11 47 ms 41 ms 42 ms 199.91.189.234
12 37 ms 39 ms 38 ms 199.91.189.74

Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=37ms TTL=250
Request timed out.
Request timed out.
Reply from 216.221.156.110: bytes=64 time=40ms TTL=250
Reply from 216.221.156.110: bytes=64 time=34ms TTL=250
Reply from 216.221.156.110: bytes=64 time=33ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=32ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=35ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=42ms TTL=250


I tried getting Verizon to look into it, but they are blaming the "game provider". (0)

[Ecksdee]

Name of ISP: Verizon FiOS
Character name: Yuengling Light
Country of Residence: Fairfax County, Northern Virginia, United States

Same issue. Constant 5 second freezes.

I've isolated the issue down to one of these hops:

3 28 ms 14 ms 10 ms G0-9-2-6.WASHDC-LCR-21.verizon-gni.net [130.81.97.106]
4 9 ms 8 ms 8 ms ae1-0.RES-BB-RTR1.verizon-gni.net [130.81.209.206]
5 11 ms 12 ms 11 ms 0.ae5.XL1.IAD8.ALTER.NET [152.63.8.121]
6 9 ms 8 ms 8 ms 0.xe-10-0-1.GW9.IAD8.ALTER.NET [152.63.33.161]
7 * 14 ms 14 ms tinet-gw.customer.alter.net [152.179.50.30]
8 41 ms 39 ms 37 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 41 ms 37 ms 40 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 47 ms 41 ms * 192.34.76.2
11 47 ms 41 ms 42 ms 199.91.189.234
12 37 ms 39 ms 38 ms 199.91.189.74

Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=37ms TTL=250
Request timed out.
Request timed out.
Reply from 216.221.156.110: bytes=64 time=40ms TTL=250
Reply from 216.221.156.110: bytes=64 time=34ms TTL=250
Reply from 216.221.156.110: bytes=64 time=33ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=32ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=35ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=42ms TTL=250


I tried getting Verizon to look into it, but they are blaming the "game provider". (0)

They are so sick of hearing from me / I have the same provider and they sent me a new router cause they cant fix the problem.

[dublincore]

- Name of ISP: Cox Communications
- Country of Residence: USA, Nebraska
- When does the problem occur: Always, or at least at the times when I'm generally on. (8:00 pm - 12:00 am CST, Sunday-Thursday.) I'd say it occurs once every 10 minutes or so, with the effect lasting anywhere from 20 seconds up to a minute. Seems to occur more frequently in dungeons (or perhaps it's just more readily noticeable in dungeons), with it sometimes happening every pull.

[Anova]

Name of ISP: Comcast
Character Name: Deneb Algiedi
Country of Residence: Berkeley, California, United States

[andur]

Name of ISP: http://www.oktv.se
- Country of Residence: Sweden
- When does the problem occur: Starts in the evening around 8-9pm.