This is a straight up lie.
Your IP whois reports "NTT America, Inc. (NTTAM-1)"
https://www.whois.com/whois/204.2.229.10
This is a straight up lie.
Your IP whois reports "NTT America, Inc. (NTTAM-1)"
https://www.whois.com/whois/204.2.229.10
Good Morning,
I would like to ask if anyone is still having this issue? If your issue was resolved please let us know when it was resolved. We are continuing to monitor this issue.
Thank you for playing Final Fantasy XIV!
I mean, I still have this issue. I'm not with Cox ISP though. My ISP is Sky. Nothing has changed since the 4.06a patch almost 4 months ago. Plenty of rubber-banding still going on no matter what I'm doing in-game.
Riko_Futatabi,
We would like to suggest creating your own thread regarding your issue. We would like to assist you in a more direct manner.
Thank you for playing Final Fantasy XIV!
I am still having the same issues today. I haven't received any emails from you guys regarding this yet either.
cox player aswell but no problems at all.
Seems to have gotten better, but I am hesitant to say that since the holidays may be affecting the issue.
This is not a week to ask for issues. Due to it being the holidays. Please ask again after Jan 3rd, 2018.
It's the nodes on the way to the server to California. Honestly the only way SE will ever fix this issue is to move the servers to a more central location in NA since they have no control over the nodes along the way to the state.
I get constant issues during prime time as well from Comcast.
Yes my ports are forwarded.
Yes the game is the only program running.
No it's not my ISP's fault.
It's the server location.
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. -_-
I was experiencing the issue last night around 6:30pm still.
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.
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.
Any updates on this Ariellendera?
Good Morning,
Is everyone still experiencing this issue? Chortle did you receive a email from us?
- 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.
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.
¡The same problem happens to me, it happened today and continue!
-Increase of ping: 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): Movistar
- State/Country: Colombia
- 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=316ms TTL=49
Respuesta desde 204.2.229.9: bytes=32 tiempo=307ms TTL=49
Respuesta desde 204.2.229.9: bytes=32 tiempo=328ms TTL=49
Respuesta desde 204.2.229.9: bytes=32 tiempo=318ms TTL=49
Estadísticas de ping para 204.2.229.9:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Traceroute
Code:
Traza a 204.2.229.9 sobre caminos de 30 saltos como máximo.
1 3 ms 6 ms 10 ms 192.168.1.1
2 38 ms 43 ms 34 ms 10.7.120.198
3 36 ms 33 ms 38 ms 10.7.120.197
4 56 ms 54 ms * 176.52.253.235
5 57 ms 58 ms 55 ms 176.52.253.234
6 107 ms 94 ms 103 ms 5.53.3.191
7 132 ms 130 ms 150 ms 94.142.126.170
8 * * 200 ms 94.142.118.238
9 207 ms 200 ms 212 ms 94.142.117.67
10 212 ms 209 ms 211 ms 5.53.3.20
11 213 ms 219 ms 318 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolution
s.com [213.140.53.97]
12 215 ms 213 ms 214 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.1
46]
13 217 ms 209 ms 215 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.1
62]
14 332 ms 266 ms * ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.
237]
15 266 ms 263 ms 257 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.
121]
16 259 ms 259 ms 258 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.5
8]
17 274 ms 271 ms 272 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.
250.195.42]
18 274 ms 265 ms 304 ms 204.2.229.242
19 260 ms 260 ms 253 ms 204.2.229.9
Traza completa.
:o:confused:
Thank you for your reply Chortle,
It seems to be the issue has subsided. I would suggest doing some of the trouble shooting steps now that the "big issue" has been taken care of. If you are still having issue please let us know so I can escalate this again.
hope to be of assistance.
Akross I apologize. I have corrected the original post to reflect your correct platform. Please try the steps.
Hope to be of assistance.
- Type of Issue/Feedback: Ping goes up from 190/210ms before of 31 december , now 02-01-2018 i have 300/320ms.
- Name of your Internet Service Provider (ISP): Movistar
- State/Country: Coquimbo, Chile.
- World Name: Lamia
- Frequency: All the time
Haciendo ping a 204.2.229.9 con 32 bytes de datos:
Respuesta desde 204.2.229.9: bytes=32 tiempo=303ms TTL=47
Respuesta desde 204.2.229.9: bytes=32 tiempo=321ms TTL=47
Respuesta desde 204.2.229.9: bytes=32 tiempo=284ms TTL=47
Respuesta desde 204.2.229.9: bytes=32 tiempo=285ms TTL=47
Traza a 204.2.229.9 sobre caminos de 30 saltos como máximo.
1 25 ms 19 ms 19 ms 192.168.8.1
2 * * * Tiempo de espera agotado para esta solicitud.
3 10.179.65.129 informes: Red de destino inaccesible.
Hello Callinon, Thank you for posting on the Final Fantasy XIV Technical Support Forums.
Can you elaborate on the kind of disconnect you are having?
Please provide:
- When the disconnects started occurring
- Platform (PC, PS4, Mac)
- Any error codes or messages you receive upon disconnect (if any)
- Type of connection (wired or wireless)
- Other programs running while the game is playing (if any)
- Frequency at which disconnect occurs
- Where you are booted to after disconnect (Desktop, Start Screen, Character Select)
What Server/Data Center are you on? It may be possible that going to more populated sections may result in the disconnections for you (by exacerbating existing connection issues), however this is only speculation.
Hope we can be of assistance.
Sure
- Disconnects last night started around 6 or 7pm CST and that seems to be the general time when latency spikes tend to occur as well. This lasts until about midnight or so but I'll generally give up well before then.
- PC
- 90002
- Wired
- I mean it's a PC... there's other stuff going on. What kinds of things are you looking for here? I wasn't doing anything bandwidth intensive like downloading a game or something if that's what you mean.
- Disconnects last night occurred quite frequently, between 3 and 10 minutes apart before I just gave up entirely.
- Booted to title screen. My understanding is this is the common result of a 90002 error (as opposed to a lobby server failure)
I'm on Ultros (Primal). This isn't a high population server but frankly, even if it were, "there are a lot of people playing the game" is not a good reason for frequent disconnects in an MMORPG.
Thanks
Im from Lima Peru. Having the same issues with Telefonica (Movistar)
- Type of Issue/Feedback: Ping goes up from 180ms before of 31 december , now 02-01-2018 i have 250/265ms.
- Name of your Internet Service Provider (ISP): Telefónica Peru (Movistar)
- State/Country: Lima-Peru
- World Name: Hyperion
- Frequency: All the time
Traza a 204.2.229.9 sobre caminos de 30 saltos como máximo.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 24 ms 22 ms 22 ms 10.115.7.47
3 25 ms 22 ms 22 ms 10.113.5.226
4 23 ms 23 ms 24 ms 10.111.5.165
5 24 ms 23 ms 23 ms 84.16.11.245
6 91 ms 83 ms 83 ms 94.142.97.163
7 149 ms 116 ms 115 ms 213.140.37.184
8 223 ms 194 ms 197 ms 94.142.117.231
9 204 ms 204 ms 205 ms 213.140.35.1
10 201 ms 199 ms 199 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
11 214 ms 203 ms 202 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
12 214 ms 213 ms 213 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
13 260 ms 258 ms 257 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
14 258 ms 259 ms 259 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
15 259 ms 263 ms 258 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
16 262 ms 262 ms 261 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
17 263 ms 262 ms * 204.2.229.242
18 262 ms 262 ms 266 ms 204.2.229.9
Traza completa.
Thanks for your help.
No disconnects tonight but still had those bad latency spikes during evening activities. Ever try healing a dungeon when your ping is 360 ms? I don't recommend it.
Im still getting pretty bad rubber banding in evening still, for me I'm actually disconnecting more
Good Morning,
I would like to correct my previous statement. I looked into this and the issue is still being investigated by Japan. We would still like to collect information from players in Arizona experiencing this issue. Please let us know here that you are still having this issue, report the issue to the ISP, get a confirmation code or reference number from contact with ISP. DO NOT post personal information here, once we get enough reports to send out emails again we will. Again I apologize for my post above.
Hope to be of assistance!
Good Morning Callinon, Thank you for posting on the Final Fantasy XIV Technical Support Forums.
Have you tried running the game with no other programs running simultaneously? Try going to the startup tab on the task manager and disabling all of the programs. Then restart your PC. This should start the PC without any background applications. Then run the game without any other programs (Discord, Pingzapper, Geforce Experience, etc.). It's possible that one of these programs may be interfering with the game just enough to disconnect you only some of the time.
Please let us know if this solves your issue so we can better assist other players who may have the same problem.
Thank you for playing Final Fantasy XIV! Hope to see you online.
Good Morning and Thank you all for posting here in the Technical Support Forums,
We will be begin to monitor this issue.
Hope to be of assistance.
I didn't see this thread until now but I've been having the same issues and I'm in Arizona with Cox as my ISP. It's extremely frustrating because it happens during the evening after I'm off work which basically renders the game unplayable. The past few weeks haven't been as bad as earlier in December but it's still unacceptable. I sent a ticket to support but I'm not sure what other details, if any, are needed.
Running FFXIV in what is essentially safe mode didn't work, nor would it be an acceptable solution even if it had.
I did notice one strange thing tonight.
https://i.imgur.com/ytPpWII.png
Two connections to the same IP address (the FFXIV remote server) with nearly double the latency between them. Obviously these two connections should be taking the same route to each other so why such a sharp difference? Server problems maybe? If the remote server took a long time to respond to the ping request it would be the same as a network node taking a long time to respond.
Hello Callinon Thank you for your reply,
We are going to be monitoring this issue. In the mean time, have you tried contacting your ISP? We suggest you report the issue to them and obtain a reference/ticket number from them. Thank you for your understanding while we try and get this issue resolved.
Thank you for playing Final Fantasy XIV! Hope to see you online.
Yeah, I noticed something was up, when me and my roomates would play, and only 1 of the 3 of us would get kicked.
Every time it happened.
Plus we can see what the other sees, and theres no actual lag when we get kicked most of the time.
And when I've set up 2 FF14s running on my PC, one using the keyboard, the other using a controller, either my account or my friends account would be DCed, but not the other.
(Remember, same computer, just 2 different accounts. And which one gets DCed is random.)
Just wanted to update and say I am still having this issue as an Arizona resident with Cox as my ISP in the evenings. It has gotten so bad that Astragalos is unplayable.
Connection problems have affected my live stream tonight on Twitch. I have been inundated with 90Ks and 3Ks tonight. You guys need to lift, Square. If you need to deliver a hotfix and put the servers on maintenance do it now and do it quick.