Blank Tenancy - Unplayable Packet Loss
Since December, my Battlefield 6 client has been experiencing persistent and severe network instability that renders the game effectively unplayable.
The issue presents as repeated latency spikes and packet loss that scale with match size. In larger matches, the in-game performance/network graph shows missed packets per second (mp/s) regularly spiking above 200mp/s, with a clear, periodic pattern rather than random fluctuation. These spikes occur approximately every two seconds and correlate directly with noticeable rubber-banding, delayed hit registration, and deaths occurring well after taking cover.
Importantly, this behaviour is not accompanied by client-side performance issues. Frame rate and system performance remain stable, and the issue does not resemble local network congestion or intermittent connectivity faults.
Within the in-game settings, the TENANCY field is displayed but remains blank (“TENANCY:”), suggesting the client is not being assigned or is unable to resolve a regional backend tenancy. When this occurs, the network health indicator frequently turns red, and mp/s values increase dramatically. Restarting the game or changing matchmaking context occasionally resolves the issue temporarily, which strongly suggests tenancy assignment or backend routing at session creation is a contributing factor.
The issue has been persistent for several weeks and appears to disproportionately affect larger matches, which is consistent with backend routing or cross-region failover behaviour rather than a local client or ISP problem. Other users are reporting similar symptoms, including apparent routing to non-local regions despite their physical location.
In its current state, the game does not maintain a stable or reasonable network connection and is therefore not fit for purpose. This appears to be a backend networking or routing regression introduced in December and requires investigation and remediation.
