Request for information: ISPs and P2P throttling

[Raist]

Last little trace post, dont care if it aint helping ill feel better LOL

This was at 7:30 PM ish central time

Tracing route to 199.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [000.000.0.0]
2 51 ms 5 ms 10 ms L100.DLLSTX-VFTTP-58.verizon-gni.net [173.71.9.1]
3 13 ms 8 ms 6 ms G0-5-0-6.DLLSTX-LCR-22.verizon-gni.net [130.81.107.128]
4 * * * Request timed out.
5 7 ms 5 ms 8 ms 0.ae2.BR2.DFW13.ALTER.NET [140.222.225.53]
6 17 ms 10 ms 5 ms ix-20-0.tcore1.DT8-Dallas.as6453.net [66.110.56.17]
7 66 ms 67 ms 65 ms 64.86.78.5
8 69 ms 76 ms 69 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
9 65 ms 65 ms 65 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
10 68 ms 65 ms 65 ms 66.198.96.50
11 69 ms 67 ms 80 ms 192.34.76.2
12 71 ms 67 ms 65 ms 199.91.189.234
13 * * * Request timed out.

That 199.91.189.57 address hasn't hosted a world service since the end of March. Our assigned IP's have changed several times over the past year or so. Either capture the IP your client actually uses when fully logged into the game (resmon or netstat will give it to you), or use the registered DNS names for the lobby servers:

neolobby01.ffxiv.com through neolobby06.ffxiv.com with odd numbers forJapan and even for Canada.


It is interesting to note that we continually see the exchange points to Verizon's peering partners not responding to ICMP ECHO. Perhaps they are still refusing to upgrade their bandwidth at those border routers...intentionally restricting throughput in an attempt to force third party CDN's to peer directly or in other words, sort of "pay-to-play".


Verizon’s Accidental Mea Culpa