90002 error even while using VPN "WTFast"?

[Khemorex]

Ive didnt have much of a trouble with this sort of stuff , until the last patch , i doubt its the your or my internet , its SE .. or some overloaded Server-node just before SE.

WTB real EU server for 3.0 pls :P

[NocX7]

Ive didnt have much of a trouble with this sort of stuff , until the last patch , i doubt its the your or my internet , its SE .. or some overloaded Server-node just before SE.

WTB real EU server for 3.0 pls :P

It used to be just the 90002 error but even though I still disconnect every hour,now I sometimes get the 90003 error instead of 90002.I have not found any info on the 90003 error.Nothing on it on google,game forums or this game's reddit page.

Just what is required for this game to run properly when every other game runs fine?

[Lemage]

It used to be just the 90002 error but even though I still disconnect every hour,now I sometimes get the 90003 error instead of 90002.I have not found any info on the 90003 error.Nothing on it on google,game forums or this game's reddit page.

Just what is required for this game to run properly when every other game runs fine?

This game requires a bit more of a stable connection than 2 cans tied by string. I'm willing to bet your disconnections are due to a line stability issue, most people who ask me about their disconnections end up having more packet loss and line jitter than your average copper cabled ADSL connection wired by a monkey on stilts with coke bottle glasses.

[NocX7]

This game requires a bit more of a stable connection than 2 cans tied by string. I'm willing to bet your disconnections are due to a line stability issue, most people who ask me about their disconnections end up having more packet loss and line jitter than your average copper cabled ADSL connection wired by a monkey on stilts with coke bottle glasses.

And I'd agree with you were it not for the fact my this error happens every hour on the dot while no other MMO disconnects ever.I may be wrong but instability shouldn't be so predictable which is why I still think there could be other reasons for this error to be happening literally like clockwork.

Don't get me wrong though I very much still think my ISP is to blame which is why I've been yelling at them for over a week now and am close to just changing my ISP.

[ElHeggunte]

And I'd agree with you were it not for the fact my this error happens every hour on the dot while no other MMO disconnects ever.I may be wrong but instability shouldn't be so predictable which is why I still think there could be other reasons for this error to be happening literally like clockwork.

Don't get me wrong though I very much still think my ISP is to blame which is why I've been yelling at them for over a week now and am close to just changing my ISP.

The way you describe your problem points to something else besides your ISP. It's sounds like there's a problem with one of the hops you take to get to the servers. Since other MMOs and services aren't going to take the exact same internet path to their own servers, it's not unusual that they aren't affected while FFXIV continues to have problems. If you can predict the issue a you say, do a traceroute while you're having an episode and share that information with your ISP. If it really is a bad node it might be possible for them to have you switched over to a different route to see if it alleviates the problem. Saying "Internet broke, you fix" won't get you anywhere if you can't show your ISP where to look. Otherwise it's like asking a construction worker to search a million miles of road for a pothole to fill instead of just telling him exactly where the hole is.

[NocX7]

The way you describe your problem points to something else besides your ISP. It's sounds like there's a problem with one of the hops you take to get to the servers. Since other MMOs and services aren't going to take the exact same internet path to their own servers, it's not unusual that they aren't affected while FFXIV continues to have problems. If you can predict the issue a you say, do a traceroute while you're having an episode and share that information with your ISP. If it really is a bad node it might be possible for them to have you switched over to a different route to see if it alleviates the problem. Saying "Internet broke, you fix" won't get you anywhere if you can't show your ISP where to look. Otherwise it's like asking a construction worker to search a million miles of road for a pothole to fill instead of just telling him exactly where the hole is.

I have already done multiple traceroutes and have sent them to my ISP via email twice but they insist there is nothing wrong and refuse to look further into it.All they care about is that the internet in general is working and this is why I said I might be switching to a different ISP soon.When even the administrators refuse to help thats when I start thinking of switching.

And for anyone that can read a traceroute here: (this was done 2 minutes after a disconnect just now)

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 12 ms 12 ms 10.1.1.161
4 13 ms 12 ms 12 ms 10.1.0.129
5 14 ms 12 ms 11 ms 10.1.0.18
6 18 ms 12 ms 12 ms 10.1.0.210
7 13 ms 12 ms 12 ms 213.140.51.249
8 47 ms 34 ms 31 ms xe4-1-3-0-grtmiabr4.priv.red.telefonica-wholesal
e.net [94.142.119.93]
9 35 ms 48 ms 39 ms 84.16.14.191
10 33 ms 34 ms 35 ms et2-0-0-0-grtmiana2.red.telefonica-wholesale.net
[84.16.14.189]
11 34 ms 35 ms 35 ms hu-0-11-0-0-grtmiana4.net.telefonicaglobalsoluti
ons.com [84.16.12.238]
12 35 ms 35 ms 83 ms if-7-2.tcore1.AEQ-Ashburn.as6453.net [66.198.154
.177]
13 85 ms 85 ms 86 ms 64.86.85.1
14 87 ms 86 ms 85 ms if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.
33]
15 84 ms 86 ms 115 ms if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.
33]
16 84 ms 83 ms 86 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.2
5]
17 79 ms 79 ms 79 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.61]
18 93 ms 93 ms 92 ms 192.34.76.2
19 93 ms 93 ms 92 ms 199.91.189.234
20 82 ms 82 ms 92 ms 199.91.189.234
21 80 ms 79 ms 82 ms 199.91.189.74

Trace complete.