Request for information: ISPs and P2P throttling

[Hierovasuki]

- Name of ISP: Cox Communications
- Country of Residence: United States (Phoenix, AZ)
- When does the problem occur: Always
- Reference number from your ISP: None

When I log in, skills do nothing, monsters won't take damage, etc. After a minute or two, I get booted out of the game with error 90000. This happens every single time without fail and during every time possible (early mornings, afternoons, evenings, in the dead of night, you name it) which makes the game virtually unplayable for me. The problem is fixed if I use a VPN service, however I lag too much to play because using the VPN program causes me to have a lot of latency.

[Marishi-Ten]

I get the feeling that there are two separate issues going on:

1.) ISP's may be throttling back some users as they think that the Final Fantasy XIV client is Peer To Peer (P2P) sharing. Some ISP's do this to stop gap large sharing clients (BitTorrent) causing latency in their networks.

2.) There are massive latency spikes on the server end causing "rubber banding" and delays when executing actions and movement.

If the ISP is throttling the actual client, one wouldn't see low ping rates followed by some extremely high latency followed by a drop to normal again. Throttling would be a low connection all the time with little to no jumping around (see my post here for reference http://forum.square-enix.com/ffxiv/t...ottling/page76 )

"Rubber Banding" is a symptom of packet loss and poor end point connection. When the server (Square) has to send the client (Player) packets there has to be an acknowledgement of the data on the client end and a confirmation of the data being received on the server end (Think MD5 checksum). If the packets are incomplete, the client can't confirm with the server it received all of the data so it tries again. In the meantime, all data stops parsing (the flow of data is interrupted). Once the packets are confirmed, the server and client then have to double down to send data and present them visually while syncing their clocks together (the speed up and all of the logs spilling in at once).

Hopefully Square can set up another sticky for the second issue (Easily duplicated. I've even set up a template for users if need be) so we can store aggregate values there and not clutter up an existing issue.

In the end, it may not be necessary as the "rubber banding" issue seems to stem from the MPLS (Ormuco) and rack (Tata) end. Until the MPLS circuits are upgraded to accommodate more bandwidth and the server ports are expanded and prioritized, latency and route paths will be impacted.

[june23]

This issue went away for 3 days after the major patch. It then came back. Unplayable. Connection is still unstable at all time of the day. Now I am getting more 90000 error than before.

I saw a SE thread saying 90000 is fixed ...

[Onisesshomaru]

- Time Warner Cable
- United States
- Always - Most noticed within Duty Finder - R0 Random skips and freezes.
- No Reference Number.

[Conana]

ISP: Comcast XFinity
Country/Region: San Francisco, USA
Occur time: Throughout the day and night

No problem with the internet as I can browse other stuff without any problem. All routers/etc are up to date.

[deklyn]

ISP Shaw Cable
Country/Region: West Coast Canada
Time of occurrence: always since the last patch
Have not called ISP regarding issue as of yet

[Ecksdee]

I get the feeling that there are two separate issues going on:

1.) ISP's may be throttling back some users as they think that the Final Fantasy XIV client is Peer To Peer (P2P) sharing. Some ISP's do this to stop gap large sharing clients (BitTorrent) causing latency in their networks.

2.) There are massive latency spikes on the server end causing "rubber banding" and delays when executing actions and movement.

If the ISP is throttling the actual client, one wouldn't see low ping rates followed by some extremely high latency followed by a drop to normal again. Throttling would be a low connection all the time with little to no jumping around (see my post here for reference http://forum.square-enix.com/ffxiv/t...ottling/page76 )

"Rubber Banding" is a symptom of packet loss and poor end point connection. When the server (Square) has to send the client (Player) packets there has to be an acknowledgement of the data on the client end and a confirmation of the data being received on the server end (Think MD5 checksum). If the packets are incomplete, the client can't confirm with the server it received all of the data so it tries again. In the meantime, all data stops parsing (the flow of data is interrupted). Once the packets are confirmed, the server and client then have to double down to send data and present them visually while syncing their clocks together (the speed up and all of the logs spilling in at once).

Hopefully Square can set up another sticky for the second issue (Easily duplicated. I've even set up a template for users if need be) so we can store aggregate values there and not clutter up an existing issue.

In the end, it may not be necessary as the "rubber banding" issue seems to stem from the MPLS (Ormuco) and rack (Tata) end. Until the MPLS circuits are upgraded to accommodate more bandwidth and the server ports are expanded and prioritized, latency and route paths will be impacted.

I am definitely experiencing the 2nd issue more than the 1st. Is there a viable fix and is it something on the end of the user or is it something that SE needs to fix?

[prymortal]

- Vodafone New Zealand (Priviously Telstra Clear)
- New Zealand
- Most times very frequent
- To hard to get ahold of.

[CMV]

- Comcast Xfinity
- USA
- Early morning, I'll get the 90000 error and my internet connection will go out, around 5am PST, but now I'm having latency issues that are affecting me in-game
- They didn't have an answer, as my modem doesn't show anything out of the ordinary, and my connection will come back in a few minutes, but nothing I do makes it any faster like resetting the modem, router, and PC

EDIT: Just went out while I was playing, at 1AM PST, right after I left a dungeon, waaaay too close.

[DriftingFable]

- AT&T U-verse
- Central coast, Baton Rouge, Lousiana. United States
- "Early morning" typically I will start experiencing random 90000s during around 1 -2 AM CST. I've experienced this Tuesday morning and Wednesday morning.