This is also happening to me (and many others in my Guilds, particularly in Australia), and it started after the "quarterly backend datacenter fixes and updates" maintenance on Wednesday, May 22.

These issues occur with fresh installs of ESO with all default settings, with or without addons. Everything has been tried to mitigate these problems including completely reinstalling Windows (10 and 11) and ESO. Nothing changes. The only constant is ESO servers.

The *only* thing so far that has (almost) eliminated the errors is to use a VPN, although today I did receive the generic "Error (an Error has occurred).

Since the errors are reduced when using a VPN, I think that some of the issues may have to do with ISPs use of CGNAT. I suspect that network and/or code changes implemented during that maintenance have triggered some incompatibilities.

The day after the maintenance I stopped playing because of the constant disconnects. I submitted a support ticket.

For example, this is a log of my ESO experience on Saturday 25th May:

14:17 login, port to Glenumbra, start running, disconnect -> Error (An error has occurred)
14:29 login, port to BRP, ui reload, disconnect ->Error (An error has occurred)
14:29 login attempt -> Error 103 (cannot locate server information)
14:30 login attempt -> Error 307 (booted from server)
15:14 login, Auridon survey x 3 -> Error (An error has occurred)
15:24 login, bmup Stormhaven -> Error 334 (lost lobby connection)
15:34 login, Stormhaven wayshrine, click on other Stormhaven wayshrine -> Error (An error has occurred)
15:45 login, Stormhaven, idle -> Error (An error has occurred)

Gave up trying to play until guild trial that night, where me and 4 of my Guild *immediately* disconnected going through the first door.

ZOS_Bill wrote: »

@Bunnios

Do you have your support ticket number?

If so, we can check on it and give you an update.

@ZOS_Bill

My support reference number is 240524-008346.

It was responded to with a cut and paste of the "what to do if you have connectivity issues" support article.

BTW, I logged in this morning for the first time in days *without* using a VPN and I was disconnected again within 10 minutes (Error 302).

Yesterday I played for hours using a VPN without disconnecting at all.

My ticket was closed after they copy and pasted the connectivity troubleshooting steps:

"This incident cannot be reopened or updated. If you need further assistance, please submit a new ticket."

I wrote in the forum post(s) that I (and others) have done literally everything possible up to and including complete reinstallation of Windows and ESO and that the issues persist regardless of what I do. All connectivity troubleshooting was tried, including opening ports on routers, which made absolutely no difference, and that practice is strongly discouraged anyway, from a security perspective.

I never needed to open ports before to play ESO (I've been playing on and off for 10 years) and I reiterate that it made no difference after last week's maintenance.

It's clear that the people who in a position to solve these issues are not getting the information/feedback required or that ZOS simply does not care whether people can play the game they have paid for, or not. I'm tending towards the latter.

SOMETHING was changed during the May 22 maintenance that causes constant disconnects for people whose ISPs use CGNAT [1] and when they happen they seem to happen at roughly 10 minute intervals, which points towards some timeout/configuration value. I've been with the same ISP (using CGNAT) for almost 2 years and did not have these issues UNTIL the May 22 maintenance.

As I mentioned, I can play for hours without a disconnect, IF I use a VPN, which provides me with my own unique IP address.

Friends in my guilds who have NOT had disconnect issues since the May 22 maintenance all have ISPs that do NOT use CGNAT.

[1] https://en.wikipedia.org/wiki/Carrier-grade_NAT

You need to get to get feedback like this into the hands of people with the skills and knowledge to do something with it.

Copy and pasting useless support documents is just wasting everyone's time, especially in response to tickets that contain detailed information about technical issues and what has already been attempted to solve them.