I'm under Spectrum myself (through Charter) and getting 100% packet loss. This is the only game having this issue. Outside of that with both Xbox and Playstation systems, multiplayer and checking stats for Overwatch (on PC), I'm not experiencing on any problems. It's specifically this game and its servers. Kinda annoying. Not sure I want to resub further after my sub lapses out soon if I can't even run OS3/OS4 without my connection deciding to sling during raid nights. -_-
-
12-29-2017, 02:12 PMElkanah
-
12-29-2017, 02:41 PMAsurasYes, I'm still having the issue. Evening hours and mean lag spikes. It's so bad that I don't even raid much anymore during the evening.Quote:
Originally Posted by Ariellendera
-
12-29-2017, 10:57 PMChortle
I was experiencing the issue last night around 6:30pm still.
-
12-31-2017, 01:26 PMCallinonUpdate: High latency - Now with more 90k!
Server: Ultros (US-Primal)
I'm getting around 200-300ms latency in the evenings. Traceroutes suggest this is linked to the server's ISP or their backbone (whatever ntt is, I've never heard of it). Normal latency through the rest of the day is around 60ms. Actually was in an instance earlier tonight and spiked up above 400ms. Obviously this creates a borderline unplayable game during these times (roughly any time after 5pm CST).
Any chance of whacking your ISP with a 2x4 or something so I can play when my FC is playing?
Thanks. -
01-02-2018, 11:24 AMCallinon
Well now we're graduating back up to 90002 errors. This is what caused me to unsub for several months last time. I had 3 of them during an Expert run tonight and then a couple more afterward after which I simply gave up trying to play the game for the evening.
Running a pathping now for some stats, will edit when it's done.
As much as I love to blame Comcast for everything from global warming to hair loss, I can't help but notice their 4% total packetloss versus NTT's combined 19% packetloss along the route. 19% packetloss is an enormous figure in the best of circumstances, but combined with how badly FFXIV handles this phenomenon it makes the game literally unplayable.Code:C:\Users\Jon>pathping 204.2.229.97
Tracing route to 204.2.229.97 over a maximum of 30 hops
0 Lapis [192.168.1.54]
1 RT-AC68U-5570 [192.168.1.1]
2 96.120.28.53
3 te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
4 68.85.183.142
5 be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
6 be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
14 xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
15 * 204.2.229.242
16 204.2.229.97
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Lapis [192.168.1.54]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% RT-AC68U-5570 [192.168.1.1]
0/ 100 = 0% |
2 9ms 1/ 100 = 1% 1/ 100 = 1% 96.120.28.53
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% 68.85.183.142
0/ 100 = 0% |
5 12ms 1/ 100 = 1% 1/ 100 = 1% be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
0/ 100 = 0% |
6 13ms 0/ 100 = 0% 0/ 100 = 0% be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
0/ 100 = 0% |
7 11ms 2/ 100 = 2% 2/ 100 = 2% be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
0/ 100 = 0% |
8 15ms 1/ 100 = 1% 1/ 100 = 1% ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
0/ 100 = 0% |
9 122ms 7/ 100 = 7% 7/ 100 = 7% ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
0/ 100 = 0% |
10 125ms 5/ 100 = 5% 5/ 100 = 5% ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
0/ 100 = 0% |
11 68ms 0/ 100 = 0% 0/ 100 = 0% ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
0/ 100 = 0% |
12 64ms 1/ 100 = 1% 1/ 100 = 1% ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
0/ 100 = 0% |
13 76ms 4/ 100 = 4% 4/ 100 = 4% ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
0/ 100 = 0% |
14 72ms 1/ 100 = 1% 1/ 100 = 1% xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
0/ 100 = 0% |
15 67ms 0/ 100 = 0% 0/ 100 = 0% 204.2.229.242
3/ 100 = 3% |
16 73ms 3/ 100 = 3% 0/ 100 = 0% 204.2.229.97
Trace complete.
-
01-02-2018, 11:08 PMChortle
Any updates on this Ariellendera?
-
01-03-2018, 04:21 AMAriellendera
Good Morning,
Is everyone still experiencing this issue? Chortle did you receive a email from us? -
01-03-2018, 04:24 AMChortleI still experience this issue although it has been not as bad (have not disconnected) as it was previously. Still most notably around the same time frame.Quote:
Originally Posted by Ariellendera
I received an e-mail and replied with all my information. -
01-03-2018, 05:36 AMAkrossHigh ping again - ISP: Telefonica del Sur/ Movistar / Vivo (Telefonica)
- Type of Issue/Feedback: Ping goes up from 190/200ms before of 31 december , now 02-01-2018 i have 290/300ms.
- Name of your Internet Service Provider (ISP): Telefónica del Sur
- State/Country: Chillán, Chile.
- World Name: Lamia
- Frequency: All the time
Ping 1:
Code:Haciendo ping a 204.2.229.9 con 32 bytes de datos:
Respuesta desde 204.2.229.9: bytes=32 tiempo=296ms TTL=48
Respuesta desde 204.2.229.9: bytes=32 tiempo=292ms TTL=48
Respuesta desde 204.2.229.9: bytes=32 tiempo=292ms TTL=48
Tiempo de espera agotado para esta solicitud.
Estadísticas de ping para 204.2.229.9:
Paquetes: enviados = 4, recibidos = 3, perdidos = 1
(25% perdidos),
Traceroute
Code:Traza a 204.2.229.9 sobre caminos de 30 saltos como máximo.
1 2 ms 2 ms 2 ms 192.168.0.1
2 2 ms 2 ms 2 ms 192.168.2.1
3 15 ms 15 ms 16 ms 10.29.64.1
4 105 ms 91 ms 93 ms reverso.190.211.0.operaciones.gtdinternet.com [190.211.0.1]
5 24 ms 28 ms 20 ms 192.168.4.53
6 29 ms 28 ms 26 ms 192.168.4.54
7 * * * Tiempo de espera agotado para esta solicitud.
8 216 ms 155 ms 158 ms mia2.be1.100.scl2.gtdinternet.com.63.196.190.in-addr.arpa [190.196.63.134]
9 * * 158 ms 7-2-9.ear4.Miami2.Level3.net [4.15.159.161]
10 * * * Tiempo de espera agotado para esta solicitud.
11 171 ms 179 ms 225 ms NTT-level3-80G.Miami.Level3.net [4.68.127.54]
12 * 318 ms 330 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
13 233 ms 212 ms 202 ms ae-4.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.184]
14 237 ms 218 ms 242 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
15 358 ms * 368 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
16 354 ms 359 ms 339 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
17 321 ms * 365 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
18 314 ms 335 ms 360 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
19 362 ms 378 ms 337 ms 204.2.229.242
20 * 294 ms 295 ms 204.2.229.9
Traza completa.
I hope this message is seen, this problem prevents me from playing. -
01-03-2018, 06:54 AMAriellendera
Hello Akross, Thank you for posting on the Final Fantasy XIV Technical Support Forums.
I am going to provide you some troubleshooting steps, please try them all. Contact your ISP if they do not work, and let them know what is going on.
The issue you are describing is most associated with interference with the game data. Most of the time, it results from certain security/privacy changes on PSN web browser. Please make sure that "Cookies" and "JavaScript" are ENABLED on the PSN Browser. This can be done by going to the web browser on the PS4, press the options button, then go to settings. The options for Cookies and Javascript will most likely be checked, uncheck them and then recheck them.
The fault may also lie with the "Date & Time" settings on your PlayStation 4. We would advise to please follow the provided steps to adjust your console's clock to assure it is accurate and up-to-date:
Close the FINAL FANTASY XIV game/application.
Go to [SETTINGS] on your PS4.
Select [Date and Time], and "Set via Internet". (Please do not manually set the date and time.)
Once, the date and time settings have been updated, please restart your PlayStation 4 console.
Once your console has fully restarted, please start the FINAL FANTASY XIV game/application.
Please make sure all other internet-enabled devices (including smartphones, laptop/desktop PCs, tablets, etc.) have been disabled and/or turned OFF to minimize game interference.
If the suggestions provided above do not resolve the issue, then there is a communication error. (Not the same as a connection error.)
Check the following Port Ranges on your router/modem to ensure that the following Port Ranges have been opened/forwarded/triggered:
▼TCP
54992 through 54994,
55006 through 55007,
55021 through 55040
*This can be done by visiting www.portforward.com, locate your specific Router/Modem Brand and Model Number from the 'List of Routers', and you will find a step-by-step guide on how to access your ports.
If you have properly configured your router, and you are still experiencing these issues, our next suggestion is to bypass the router, and connect your console directly to your modem. Please ensure that you power down both the modem and the console for at least five minutes before attempting to connect to FINAL FANTASY XIV.
If you continue to receive these same errors when you are connected directly to the modem, then the problem lies with your ISP. We would recommend contacting them and advising them that one or more of the ports previously provided to you are being blocked or filtered, and that you do need access on these ports.
Thank you for playing Final Fantasy XIV! We hope to be of assistance.