Request for information: ISPs and P2P throttling

I know you are probably busy, but is there an update as to if or when this is going to be fixed?

BT
- South of England ( United Kingdom )
- All the time.

Virgin
South England UK
And it's affecting both PS4 and PC randomly every few minutes. Combat and loading new areas seem to be the most common causes, but not always. Also experiencing frequent lags. Appears to be worse since yesterday's maintenance too, as before I was getting it every 30 mins or more and now it's every 5 mins or less! Up to patch 3.05, we had no errors or d/c at all.

Time Warner Cable
Milwaukee, WI USA
Ever since the expansion anytime of day

Please get this resolved.

- Name of ISP: Verizon FIOS
- Country of Residence: USA (Virginia)
- When does the problem occur: Randomly started around 6pm-Midnight, EST

I have Verizon Fios and I have really bad spike lag from the hours of 7-12 Pm EST.
This is a very annoying ongoing issue which renders the game unplayable :(

I fixed the issue guys. For those interested, it was simple. I called FiOS told them I am cancelling my service, come pick up your equipment. I also called a competitor, told them to come set up their equipment and now, no lag.

- Telstra Cable
- Australia, QLD
- Usually every few minutes.

-Verizon fios
-USA, NYC, NY
-Mostly peak hours but been happening earlier, and earlier

Quote:

---

Originally Posted by ninjaneji

-Verizon fios
-USA, NYC, NY
-Mostly peak hours but been happening earlier, and earlier

---

PLEASE FIX THIS. THE GAME IS UNPLAYABLE during raiding hours!

this is stupid, 229 pages nothing done. My friend who, I want to play with uses a ps4 there's no way to get around the verizon lag on that

- Name of ISP: Rogers
- Country of Residence: Canada
- When does the problem occur: Always but the frequency at which it happens varies. Yesterday evening a few times whereas today 90001 errors every 10 minutes

ISP - Telstra Cable
Country - Australia, NSW
Occurrence - Every minute or less

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
https://lh3.googleusercontent.com/-a...tros-14day.PNG


2 day view
https://lh3.googleusercontent.com/-E...ltros-2day.PNG


Zoomed in to a single event
https://lh3.googleusercontent.com/-w...ltros-live.PNG


PingPlotter view of same event showing hop detail
https://lh3.googleusercontent.com/--...20redacted.png

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

On the verge of quitting no fixes

Name of ISP: Verizon
time of day: Peak hours Central 5pm-12pm Every evening as of 7/30/15, unable to perform within game standards to raid, open world, craft, teleport, etc.
Location: NA (Tx)

All trace below was faulty

Quote:

---

Originally Posted by Sub22

Name of ISP: Verizon
time of day: Peak hours Central 5pm-12pm Every evening as of 7/30/15, unable to perform within game standards to raid, open world, craft, teleport, etc.
Location: NA (Tx)

---

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

I'm getting dropped on my 5th hop, so I think that, regardless of where you are, if you have Verizon they are purposely dropping data through different routing points. All it seems to be affecting is FFXIV, so whether or not Verizon will change this for a single game is to be determined.

Verizon FIOS

Daily

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

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

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

Quote:

---

Originally Posted by Mika_Stoneheart

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.

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

Quote:

---

Originally Posted by Suggestion

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 *

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

Quote:

---

Originally Posted by Suggestion

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.

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

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

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

Quote:

---

Originally Posted by Suggestion

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

Quote:

---

Originally Posted by Virtguy

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
https://lh3.googleusercontent.com/-a...tros-14day.PNG


2 day view
https://lh3.googleusercontent.com/-E...ltros-2day.PNG


Zoomed in to a single event
https://lh3.googleusercontent.com/-w...ltros-live.PNG


PingPlotter view of same event showing hop detail
https://lh3.googleusercontent.com/--...20redacted.png

---

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

Name of ISP Verizon FIOS
- Country of Residence New York, USA
- When does the problem occur (always, only during specific times?) Usually during the evening hours in EST.

Name of ISP: CenturyLink
Country of residence: Virginia, USA
Occurring lag all day (always)

Name of ISP: Unitymedia
Country of residence: Frankfurt, Germany
Occurring lag: all day for the past two weeks.

The game will randomly freeze and then fast forward 3 seconds later making it almost impossible to play. :( I never had this issue before but for the past one and a half weeks it's been unbearable.

ISP:BT
Country:Nothern Ireland
Type: Constant delay, everything I try to attempt to avoid or active has at least a 0.5-1.0 second delay not matter what I do or what time of day I play at.

I saw a thread about this two years back and with heavensward they promised upgraded servers and am very sad to say they did not deliver. I have attempted on multiple occasions to correct this issue on my end but everything is green.

Quote:

---

Originally Posted by Morphic224

ISP:BT
Country:Nothern Ireland
Type: Constant delay, everything I try to attempt to avoid or active has at least a 0.5-1.0 second delay not matter what I do or what time of day I play at.

I saw a thread about this two years back and with heavensward they promised upgraded servers and am very sad to say they did not deliver. I have attempted on multiple occasions to correct this issue on my end but everything is green.

---

Just pulled them up on the downdetecter.com site, and followed links for their social media and support site. Looks like BT has been having a lot of issues in general lately. London has been knackered up bad this past week (they made announcements about investigating issues with sites not loading and such). Note that London is home to major exchanges---strong chance you may be sent there to get on transit to the your server's region. They've been getting complaints on Twitter and Facebook for a while now... and their own forums have lots of complaints about the quality of connections and such.

You may want to go through your ISP's support options to see if something is up. BT found issues roughly a year ago with routing and they made changes to address them...not unreasonable to expect they will be open to investigating things again. You may find you fair better with online support methods than the phone though. If they want to know some addresses for investigation, give them the lobby services addresses so you can be sure they are testing known and active services:

Canada:
neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com

Japan:
neolobby01.ffxiv.com
neolobby03.ffxiv.com
neolobby05.ffxiv.com


Some of you guys posting from other ISP's may want to check to see if there is a page for your ISP on the downdetector.com companies page. The main site is for North America, but at the bottom of the page they provide links that focus on specific regions like the UK, Australia etc. These pages will usually have social media feeds, possibly outage maps, and links to the support sites for lots of services on the internet--not just ISP's, but also content services like Netflix, Hulu, PSN, XBL, etc. and even things like ebay, banking services...even some specific game services as well.

Quote:

---

Originally Posted by Raist

Just pulled them up on the downdetecter.com site, and followed links for their social media and support site. Looks like BT has been having a lot of issues in general lately. London has been knackered up bad this past week (they made announcements about investigating issues with sites not loading and such). Note that London is home to major exchanges---strong chance you may be sent there to get on transit to the your server's region. They've been getting complaints on Twitter and Facebook for a while now... and their own forums have lots of complaints about the quality of connections and such.

You may want to go through your ISP's support options to see if something is up. BT found issues roughly a year ago with routing and they made changes to address them...not unreasonable to expect they will be open to investigating things again. You may find you fair better with online support methods than the phone though. If they want to know some addresses for investigation, give them the lobby services addresses so you can be sure they are testing known and active services:

Canada:
neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com

Japan:
neolobby01.ffxiv.com
neolobby03.ffxiv.com
neolobby05.ffxiv.com


Some of you guys posting from other ISP's may want to check to see if there is a page for your ISP on the downdetector.com companies page. The main site is for North America, but at the bottom of the page they provide links that focus on specific regions like the UK, Australia etc. These pages will usually have social media feeds, possibly outage maps, and links to the support sites for lots of services on the internet--not just ISP's, but also content services like Netflix, Hulu, PSN, XBL, etc. and even things like ebay, banking services...even some specific game services as well.

---

I will certainly give this a look into but I've had this issue since release. Drives me up the wall when I get blamed for dying to aoe crap when there's a lot of the times it was due to this delay that I got shafted.

- Name of ISP - Cogeco Internet (Cable)
- Country of Residence - Canada
- When does the problem occur (always, only during specific times?) Always

Name of ISP: Time Warner Cable
Country of residence: California ( Orange County )
Occurring lag on actions almost 100% of the time ( engaging mobs and waiting for all the actions done to process, crafting lag, and regular disconnections from instances )

-Name of ISP: Century Link
-Country : US (Arizona)
-Occurrence: All the time (just started in the past week or two)

-Name of ISP: ATT Uverse
-Country : US (Illinois)
-Occurrence: alll the time