Broken official servers
hello. BF5 official servers #26262 and #10619 have been stuck/broken for weeks/months now. please reboot/fix them.
Forum Discussion
EA_Atic
DICE Team
DICE Team- @EA_Atic They are still up and frozen sadly.
confirmed that the B5F servers #26262 and #10619 are still broken
Hello @EA_Atic
Please fix the 2 servers as described.
@EA_Atic If it's of any help, here is a list of bugged servers I spotted on PC a while ago: https://answers.ea.com/t5/Battlefield-V/Bugged-server-s-in-Advanced-Search/m-p/11052173#M80276
[DICE] Tactical Conquest - #99342 has been bugged for days.
Most if not all bugged entries I listed 4 months ago are still present to this day in Advanced Search, and now a new class of broken Official servers has appeared on top of that.
These new bugged servers can easily be found by clearing all filters and searching for Official servers with ALL slots free; a few 0/64 servers will appear, and attempting to join them will result in a "Failed to join game session" error.
It can take a few refreshes for those servers to show up, and sometimes the browser seems to alternate between 2 or 3 different lists of bugged servers, as if there is either some caching issue or the servers are actually stuck in a reboot loop.
One of such servers I'm seeing at the moment is [DICE] STRATEGIC CONQUEST - #15040 in North America, but yesterday I could find half a dozen of them.
Hello @EA_Atic
The many servers described in this thread by various users are still broken.
There is a shortage of servers on BF5.
When is the fix due?
Please act with speed, asap.
We are running out of servers to play.
Thank you
Lol, EA acting with speed... this game's support is dead. They don't ban cheaters, they don't restart a stuck server for months... it's time to accept reality.
- @OsvaldohPaniccia they know this will be very, very, very bad rep if it gets to the media. not only not moderating the game, not fighting cheating, not fixing any bugs of course... but also not even caring for the servers.
Give ‘em another poke? #38925 is still hanging around in the server browser.
