Request for information: ISPs and P2P throttling

[Valkaria]

- Name of ISP : Bouygues Telecom
- Country of Residence : France
- When does the problem occur : always

[Outinet]

- Name of ISP : Bouygues Telecom
- Country of Residence : France
- When does the problem occur : always

[SyrenKhan]

Verizon FIOS

Daily

Level3 Montreal ormuco massive packet loss and then level3 massive ping spikes at 4.whatever which I go through twice.

this sooooo much.

[Suggestion]

My isp info turned out to be faulty so now all this stuff below me don't mean jack S***

This is a tracer route from us to Zalera server (not comfortable posting my ip address)

This was at 11:19 am 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 4 ms 4 ms 3 ms L100.DLLSTX-VFTTP-58.verizon-gni.net [173.71.9.1]
3 9 ms 6 ms 9 ms G0-5-0-6.DLLSTX-LCR-22.verizon-gni.net [130.81.107.128]
4 * * * Request timed out.
5 6 ms 7 ms 6 ms 0.ae2.BR2.DFW13.ALTER.NET [140.222.225.53]
6 7 ms 6 ms 7 ms ix-20-0.tcore1.DT8-Dallas.as6453.net [66.110.56.17]
7 53 ms 51 ms 51 ms 64.86.78.5
8 52 ms 51 ms 52 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
9 48 ms 49 ms 49 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
10 50 ms 49 ms 48 ms 66.198.96.50
11 54 ms 52 ms 63 ms 192.34.76.2
12 50 ms 50 ms 48 ms 199.91.189.234
13 * * * Request timed out.

I willl post a trace during peak hours for comparison

This is at 5:09 pm 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 3 ms 4 ms 3 ms L100.DLLSTX-VFTTP-58.verizon-gni.net [173.71.9.1]
3 11 ms 12 ms 11 ms G0-5-0-6.DLLSTX-LCR-22.verizon-gni.net [130.81.107.128]
4 * * * Request timed out.
5 9 ms 6 ms 9 ms 0.ae2.BR2.DFW13.ALTER.NET [140.222.225.53]
6 12 ms 11 ms 12 ms ix-20-0.tcore1.DT8-Dallas.as6453.net [66.110.56.17]
7 52 ms 51 ms 50 ms 64.86.78.5
8 57 ms 56 ms 61 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
9 50 ms 58 ms 53 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
10 50 ms 48 ms 48 ms 66.198.96.50
11 96 ms 51 ms 51 ms 192.34.76.2
12 50 ms 52 ms 51 ms 199.91.189.234
13 * * * Request timed out.
14 * * * Request timed out.
15 *

[Suggestion]

My isp information turned out to be faulty so now this all below me doesnt mean squat.

This is at 5:09 pm 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 3 ms 4 ms 3 ms L100.DLLSTX-VFTTP-58.verizon-gni.net [173.71.9.1]
3 11 ms 12 ms 11 ms G0-5-0-6.DLLSTX-LCR-22.verizon-gni.net [130.81.107.128]
4 * * * Request timed out.
5 9 ms 6 ms 9 ms 0.ae2.BR2.DFW13.ALTER.NET [140.222.225.53]
6 12 ms 11 ms 12 ms ix-20-0.tcore1.DT8-Dallas.as6453.net [66.110.56.17]
7 52 ms 51 ms 50 ms 64.86.78.5
8 57 ms 56 ms 61 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
9 50 ms 58 ms 53 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
10 50 ms 48 ms 48 ms 66.198.96.50
11 96 ms 51 ms 51 ms 192.34.76.2
12 50 ms 52 ms 51 ms 199.91.189.234
13 * * * Request timed out.
14 * * * Request timed out.
15 *

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.

[SyrenKhan]

joining suggestion

at 5:55 pm PST

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 2 ms 2 ms 3 ms Wireless_Broadband_Router.home [000.000.0.0]
2 5 ms 5 ms 6 ms L100.LSANCA-VFTTP-92.verizon-gni.net [173.51.43.
1]
3 9 ms 11 ms 11 ms G0-9-3-2.LSANCA-LCR-22.verizon-gni.net [130.81.1
85.10]
4 * * * Request timed out.
5 12 ms 8 ms 10 ms 0.ae6.BR1.LAX15.ALTER.NET [140.222.225.137]
6 7 ms 7 ms 10 ms ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
7 98 ms 93 ms 93 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

8 94 ms 93 ms 93 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

9 93 ms 93 ms 93 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
10 113 ms 93 ms 90 ms 192.34.76.10
11 94 ms 100 ms 111 ms 199.91.189.242
12 91 ms 90 ms 90 ms 199.91.189.30

[Padders]

- Name of ISP : Telstra
- Country of Residence : Australia, SA
- When does the problem occur : During Japan server peak hours

[frendy]

- Name of ISP : Bouygues Telecom
- Country of Residence : France
- When does the problem occur : always since 1/08/2015 nothing before that

[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

[rellyrell83]

ISP - TimeWarner Cable
Country - USA (NC)
Occurrence - Daily

I've opened a case with TWC and provided them with my graphs showing the recurring packet loss and corresponding latency that I'm seeing pretty much every day. Here's a few of them.

14 day view



2 day view



Zoomed in to a single event



PingPlotter view of same event showing hop detail

What program is that you use in the first three pics?