Error 2002 after the patch

[Dixssa]

From what I understood from the discord group I think VIVACOM have already solved the issue and people are able to log in.

Not for all Vivacom clients the issue is resolved.

[Hikarizu]

Yeap, Also Vivacom here. Managed to get to their tech support mail 7 hours ago and send them all the required info to notice the issue. They did some work but I am still getting timed out.
Used to stop at 2nd step. It's progress, but not quite there.

[AriannaStormwake]

i will be glad when this is fixed as i still have the issue
+1 to Emm post

[Reven_]

I am also trying to log from Bulgaria and I get error 2002. My ISP is A1, so it looks like the issue will persist for a bit longer. Still, thank you for keeping us updated with your communication with A1 and Vivacom.

[Balveda]

@Yatogami, and everyone else that helped, Thank you! I can play at last

[AriannaStormwake]

i did the same thing although the only sfia i see on the twelve99 looking glass is sfia-b4

[Revy_Sydcrow]

Hello,
Yet another Bulgarian with 2002 error, unable to login.
I have allowed all TCP Ports, that were posted in another thread about the same error, from a couple of years.
I have restarted both my router and my PC.
I have also tried pinging the servers from 2 different providers and devices, but I can not connect to the IP of the EU servers at all.
I have FF14 as an exceptions to all Firewalls, also tried turning them off, but I still can't log in or ping the servers.
I can ping NA, OC, and JP servers just fine.
The providers I have tried are OrlandoNet and Yettel, and a friend from A1 also has the same issue.

[Elaris]

Hey everyone giving info on my situation regarding contacting A1 and I just got a call back, they have confirmed the issue and are working atm to fix it. The problem has been acknowledged and being worked on! They will call me back once they have fixed it, will keep posting updates.

[EmmaneliusBrightbark]

Can confirm I can log in without problems through A1 in North Macedonia. Others are having problems tho. Apparently, it is ISP-related.

[danetrovskij]

I am with Vivacom as well, ex NET1, and I still have the issue.