Game opens and closes straight away

I've got the same issue.  In 2042, I get "connecting to online services", the load freezes for a few seconds then crashes.  I just tried to run BF5 and I get basically the same thing, the load freezes and then crashes back to the EQ app.  The common denominator is EA AC.  This issue started Friday evening as I was able to play fine earlier in the day.

I've had a ticket opened (Case #180982909) and have IM'd with I believe 3 different people so far.  Things I've done to attempt to resolve this issue (most of the following have been done multiple times):

Cleared EA app cache (https://help.ea.com/en/help/faq/clear-cache-to-fix-problems-with-your-games/)

Uninstalled and reinstalled EA Anticheat at least twice and repaired 3 more times (https://help.ea.com/in/help/pc/ea-anticheat/#:~:text=Failure%20during%20update%20process&text=Click%20Close%20in%20the%20EA,again%20for%20the%20game%20manually.) & (https://help.ea.com/in/help/faq/troubleshoot-easy-anti-cheat/)

Uninstalled and reinstalled BF 2042 and BF5

Clean hard boot (https://help.ea.com/en/help/faq/how-to-clean-boot-your-pc/)

Multiple restarts

Ran app as admin

Tried running the game as admin

I also received this link from one of the chats (https://support.microsoft.com/windows/fix-network-connection-issues-in-windows-166a28c4-14c1-bdb1-473c-09c1571455d8) but thought it was pretty obvious my internet was working if my chat was working 

I also received this from one of the reps but can find no information about a master ticket, status of the ticket or even if there is a ticket.

Deepika: I just got this case investigated by the concerned team and am happy to tell you that you’ve nothing to worry about, looks like a few other players have reported this issue as well, however, the good news here is that the studio is already aware of it and is already working on a fix, it’s getting rectified as we speak, thanks for your patience on this one and again do not worry we got your back on this one. As per the investigation, I have found that this is a known issue to us. Our dedicated teams are working hard on the issue to fix it at earliest.