90002 error even while using VPN "WTFast"?

I don't use any extra services but I've been experiencing this about every 1-2 hours for the last 2 days. As someone that plays at least 5+ hours a day you could see how this would get very annoying very quickly

Quote:

---

Originally Posted by ElHeggunte

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.

Just like I noted in the other traces you posted in another 9002 thread, you have too much jitter on Telefonica. There are signs of issues they need to address, pure and simple.

Nothing unusual about your TraceRT that I can see other than Step 2 * * * Request timed out.

But if it does that all the time, that could be normal for that gateway to not return a response, even though it's receiving the info.

-----------------------------------------------------------

Not sure if this is helpful, but on my laptop if I play FFXIV on battery power then @ 45 minutes almost on the dot, I will get the 9000002 error, which I believe is my network card throttling to save power.

You could trying switching your systems power to High Performance to see if that helps. (Balanced and Power Saving, will lower performance where it thinks it can safely save power, but may cause issues)

Quote:

---

Originally Posted by Judge_Xero

Nothing unusual about your TraceRT that I can see other than Step 2 * * * Request timed out.

But if it does that all the time, that could be normal for that gateway to not return a response, even though it's receiving the info.

-----------------------------------------------------------

Not sure if this is helpful, but on my laptop if I play FFXIV on battery power then @ 45 minutes almost on the dot, I will get the 9000002 error, which I believe is my network card throttling to save power.

You could trying switching your systems power to High Performance to see if that helps. (Balanced and Power Saving, will lower performance where it thinks it can safely save power, but may cause issues)

---

He/She has routinely seen latency spikes north of a 50% swing starting as early as the first hop after the headend...at times reaching as high as 400%. There are localized issues there, not to mention additional signs of issues that had been tracked further upstream as well. IIRC this route is from/through Spain and going through the Madrid area, which frequently shows up with congestion issues on various reports