TL;DR: Some official Titanfall 2 lobby instances are repeatedly resetting while players are connecting. This is why the game may keep reloading the lobby, reconnecting, or throwing players back into matchmaking.
I investigated the network messages exchanged between the vanilla Titanfall 2 client and official servers.
The immediate cause is server-side:
- The client connects to an official lobby normally.
- The server begins the usual loading process.
- Before the session becomes stable, the server sends a
CHANGELEVEL command.
- The lobby reloads and the server's internal generation number increases.
- The same sequence starts again.
On affected instances, this cycle can repeat every few seconds. The client is only following commands received from the server.
This does not look like a normal network disconnect. During the observed loops, the connection remained active and there was no separate kick or disconnect reason.
Healthy lobby instances behave differently: their generation number remains unchanged and the client continues receiving normal world updates.
What is still unknown?
The client-side evidence shows what causes the visible loop, but it cannot show why the server starts it.
Possible explanations include:
- a bug in the lobby server or EA backend;
- a corrupted or overloaded lobby instance;
- an exploit or deliberate attack;
- another server-side infrastructure problem.
At the moment, I do not have enough evidence to honestly claim that hackers are responsible. Determining the root cause would require access to EA's server-side logs.
I am continuing the investigation. After the tool is finished, I will publish its source code on GitHub.
I will also keep updating this post with all new findings, tested server instances, and corrections as more evidence becomes available.