Request for information: ISPs and P2P throttling

[Helban]

-Toya
-Poland
-Always, takes forever for the NPC's to appear, the abilities are going off, but the sound effects/everything else comes late etc.

[OrangeChaffinch]

-Neostrada
-Poland
-Always, not a problem when not doing something that needs quick reaction time. But every time there is a need to dodge fast i always get hit by something i ran out of 1-3 seconds ago.
Sometimes also stuff freezes and resumes after 5-10 seconds.

[SoulEcho]

- Axxess/Afrihost
- South Africa
- 18:00 to 21:00 GMT+2 ( get cosntant lag spikes and delay)

[WindDaburr]

-Optimun Online (Subsidiary of Time Warner Cable)
-United States
-Recently 24 hours a day, was only on weekends before.
-Have not

[Ashdam]

- Name of ISP: Jazztel
- Country of Residence: Spain
- When does the problem occur (always, only during specific times?): Always
- Reference number from your ISP, if you raised this matter with them

[Brannigan]

Time Warner Cable (Desert Cities)
United States
Used to be intermittently, now getting rubberbanding 24/7

When I use the program Pingzapper and go through Los Angeles, this problem disappears. Unfortunately, with a trial account I can only stay connected for an hour before having to relog, and I don't really want to use their service for just FFXIV.

[AnAntiSocialCat]

-Entanet
-England, UK
-Randomly all day, constantly during peak hours. Freezes, takes 3-5secs and all catches up. AoE impossible. (Only started on 10th October, was perfect before then)

[Bloodwillow]

- Name of ISP - Comcast
- Country of Residence - United States - Pennsylvania
- When does the problem occur (always, only during specific times?) - Always on weekends. Weekdays ususally after 5pm EST
- Reference number from your ISP, if you raised this matter with them - Pffft they say nothing is wrong. No matter what I bring up

I've done tracert to even the Lodestone or a server in Japan and I constantly time out or the ping is off the charts. Totally unacceptable.

[LordRakirian]

- T3
- Sweden
- Sometimes during the day. Every evening and night, as peak time comes closer so does the latency/lag spikes 3-5 sec to 10-20 sec.

[sirbranedamuj]

Xfinity/Comcast
DC, USA
Always occurs.

It's usually very brief instances of extreme lag during which everything int he world stops moving, then quickly resumes once the connection is re-established. The IP I'm using is one of the server IPs as listed on the unofficial ARR server status page.

C:\Users\Zach>ping -t 199.91.189.39

Pinging 199.91.189.39 with 32 bytes of data:
Reply from 199.91.189.39: bytes=32 time=117ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=102ms TTL=243
Reply from 199.91.189.39: bytes=32 time=105ms TTL=243
Reply from 199.91.189.39: bytes=32 time=94ms TTL=243
Reply from 199.91.189.39: bytes=32 time=110ms TTL=243
Reply from 199.91.189.39: bytes=32 time=104ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=112ms TTL=243
Reply from 199.91.189.39: bytes=32 time=90ms TTL=243
Reply from 199.91.189.39: bytes=32 time=101ms TTL=243
Reply from 199.91.189.39: bytes=32 time=108ms TTL=243
Reply from 199.91.189.39: bytes=32 time=98ms TTL=243
Reply from 199.91.189.39: bytes=32 time=105ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=108ms TTL=243
Reply from 199.91.189.39: bytes=32 time=106ms TTL=243
Reply from 199.91.189.39: bytes=32 time=98ms TTL=243
Reply from 199.91.189.39: bytes=32 time=105ms TTL=243
Request timed out.
Request timed out.
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=94ms TTL=243
Reply from 199.91.189.39: bytes=32 time=103ms TTL=243
Reply from 199.91.189.39: bytes=32 time=107ms TTL=243
Reply from 199.91.189.39: bytes=32 time=116ms TTL=243
Reply from 199.91.189.39: bytes=32 time=96ms TTL=243
Reply from 199.91.189.39: bytes=32 time=108ms TTL=243
Reply from 199.91.189.39: bytes=32 time=102ms TTL=243
Reply from 199.91.189.39: bytes=32 time=101ms TTL=243
Reply from 199.91.189.39: bytes=32 time=106ms TTL=243
Reply from 199.91.189.39: bytes=32 time=100ms TTL=243

Ping statistics for 199.91.189.39:
Packets: Sent = 32, Received = 30, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 117ms, Average = 103ms

C:\Users\Zach>tracert 199.91.189.39

Tracing route to 199.91.189.39 over a maximum of 30 hops

1 3 ms 3 ms 2 ms 10.0.0.1
2 38 ms 30 ms 15 ms c-69-143-232-1.hsd1.md.comcast.net [69.143.232.1
]
3 12 ms 12 ms 12 ms xe-4-1-0-32767-sur01.hyattsville.md.bad.comcast.
net [68.85.147.37]
4 12 ms 26 ms 10 ms ae-23-0-ar04.capitolhghts.md.bad.comcast.net [68
.85.114.113]
5 16 ms 12 ms 16 ms he-5-2-0-0-10-cr01.ashburn.va.ibone.comcast.net
[68.86.90.241]
6 14 ms 14 ms 31 ms be-16-pe04.ashburn.va.ibone.comcast.net [68.86.8
4.226]
7 11 ms 13 ms 14 ms xe-7-0-2.was10.ip4.tinet.net [77.67.71.193]
8 116 ms 97 ms 107 ms xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
9 104 ms 104 ms 102 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 106 ms 94 ms 96 ms 192.34.76.2
11 107 ms 106 ms 110 ms 199.91.189.234
12 105 ms 106 ms 108 ms 199.91.189.39

Trace complete.