Battlefield 6 Outage Map
The map below depicts the most recent cities worldwide where Battlefield 6 users have reported problems and outages. If you are having an issue with Battlefield 6, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Battlefield 6 users affected:
Battlefield 6 is a 2025 first-person shooter game developed by Battlefield Studios and published by Electronic Arts. Serving as the eighteenth installment in the Battlefield series, the game was released for PlayStation 5, Windows, and Xbox Series X/S on October 10, 2025.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Paris, Île-de-France | 4 |
| Villefranche-sur-Saône, Auvergne-Rhône-Alpes | 2 |
| Brest, Bretagne | 2 |
| Magdeburg, Saxony-Anhalt | 1 |
| Carson City, NV | 1 |
| Awka, Anambra State | 1 |
| Lens, Hauts-de-France | 1 |
| Colorado Springs, CO | 1 |
| Le Mans, Pays de la Loire | 1 |
| Bologna, Emilia-Romagna | 1 |
| Solonópole, CE | 1 |
| Waldheim, Saxony | 1 |
| Southport, England | 1 |
| Longueuil, QC | 1 |
| Asnières-sur-Seine, Île-de-France | 1 |
| Nantes, Pays de la Loire | 1 |
| Goiás, GO | 1 |
| Manchester, England | 1 |
| Ahascragh, Connaught | 1 |
| Numazu, Shizuoka | 1 |
| Bordeaux, Nouvelle-Aquitaine | 1 |
| Palatine, WV | 1 |
| Novo Hamburgo, RS | 1 |
| Toulouse, Occitanie | 1 |
| Glenwillow, OH | 1 |
| Inverness, Scotland | 1 |
| Rio de Janeiro, RJ | 1 |
| Santander, Cantabria | 1 |
| Charlotte, NC | 1 |
| Istanbul, İstanbul | 1 |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Battlefield 6 Issues Reports
Latest outage, problems and issue reports in social media:
-
I64VA
(@I64VA) reported
Update: Crash: EB on I-64 at MM290.2 (0.6mi west of Battlefield Blvd N Exit290A) in Chesapeake. 1 EB travel lane closed. 6:58AM
-
Raymond Tracing X-3🙅♂️
(@RaymondTracing) reported
@Ofudomyo74 comparing to battlefield was the issue, that game is s**t
-
manfredo ramirez
(@justjokemany) reported
@BattlefieldComm @Straatford87 @Battlefield Mouse input fix?
-
T Ford
(@NoMoreBS007) reported
@BattlefieldComm @Battlefield Really Dice, EA? So you mean to tell me that you did not fix the grenades but also you took 1 of Sundance's grenades? You have to be 1 of the stupidest companies on the F'N planet no F'N 🧢👎🏿🤬
-
Chris Felcker
(@chrisfelcker) reported
@TradingFool69 @KennyLied @mattpeloquin1 Communities aren't a battlefield. Your mentality is the problem.
-
Zultra
(@Zultra_99) reported
@BattlefieldComm @Battlefield Matchmaking error uhhh hello????
-
Largoat 🐐
(@largoatsecurity) reported
Guess I wrongly assumed that @EA_DICE would fix the OP choppers. A slight decrease to damage has done nothing. Servers still getting wrecked by condors, hinds and stealth choppers. Can't even use the drone/C5 anymore cause it's been slowed down by a ridiculous amount.
-
511 Virginia
(@511statewideva) reported
Update: Crash: EB on I-64 at MM290.2 (0.6mi west of Battlefield Blvd N Exit290A) in Chesapeake. 1 EB travel lane closed. 6:58AM
-
SlowButterFamilu
(@FamiluSlow) reported
@BattlefieldComm @Battlefield broken matchmaking!
-
deadly adept
(@applesoffatree) reported
I just cannot abide a poorly kept bow on the battlefield. It will cause more problems than it will solve.
-
Battlefield Bulletin
(@BFBulletin) reported
UPDATE: If you're still having issues with the matchmaking failed error, restart #Battlefield2042. Some players are reporting they're getting back into the game.
-
kittyonthefloor
(@kitty0ntheflo0r) reported
@Battlefield so you put priorities in moving buttons around more than actually fixing the issues. Team of morons is what you are!!!
-
I64VA
(@I64VA) reported
Update: Crash: EB on I-64 at MM290.2 (0.6mi west of Battlefield Blvd N Exit290A) in Chesapeake. No lanes closed. 7:06AM
-
I64VA
(@I64VA) reported
Crash: EB on I-64 at MM290.2 (0.6mi west of Battlefield Blvd N Exit290A) in Chesapeake. No lanes closed. 6:54AM
-
511 Hampton Roads
(@511hamptonroads) reported
Update: Crash: EB on I-64 at MM290.2 (0.6mi west of Battlefield Blvd N Exit290A) in Chesapeake. No lanes closed. 7:06AM