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 |
|---|---|
| Biscarrosse, Nouvelle-Aquitaine | 1 |
| Pont-Sainte-Maxence, Hauts-de-France | 1 |
| Recife, PE | 1 |
| Brasília, DF | 1 |
| Arlon, Wallonia | 1 |
| Coyoacán, CDMX | 1 |
| Saint-Malo, Brittany | 1 |
| Buenos Aires, CF | 1 |
| Comuna 1, CABA | 5 |
| Perpignan, Occitanie | 1 |
| Domingos Martins, ES | 1 |
| Courbevoie, Île-de-France | 1 |
| Strasbourg, ACAL | 1 |
| Chaumont, ACAL | 1 |
| Amagney, Bourgogne-Franche-Comté | 1 |
| Annecy, Auvergne-Rhône-Alpes | 2 |
| Paris, Île-de-France | 17 |
| Itapemirim, ES | 1 |
| São Paulo, SP | 2 |
| Brech, Brittany | 1 |
| Trévoux, Auvergne-Rhône-Alpes | 1 |
| Nidau, BE | 1 |
| Villa Victoria, MEX | 1 |
| Santiago de Querétaro, QUE | 3 |
| Telêmaco Borba, PR | 1 |
| Bordeaux, Nouvelle-Aquitaine | 4 |
| Bron, Auvergne-Rhône-Alpes | 1 |
| Madrid, Madrid | 4 |
| La Trinité, Martinique | 1 |
| Lyon, Auvergne-Rhône-Alpes | 5 |
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:
-
\\\slagmire\\\ (@StonkKerman) reported@1864Memes Hot take, nobody has made a good RTS yet. the best ones so far are Homeworld 2, WiC, battlefield BC2, and EVE online. yes, I know BC2 and EVE aren't RTS's, but they function as an RTS when played right. every single one of these had something horrendously wrong. HW2 fixed a lot from HW1 but introduced new problems that didn't need to exist. I don't know why they gave fighters and corvettes airplane physics. WiC was near perfect but the TA was so out of hand units almost stop mattering at certain point and infantry is completely useless in urban maps because blown out building become obstacles instead of cover. BC2 was actually the most well screwed together game in the entire franchise but without a sever browser the only way you could put a team together was an XBL party so we got nothing but organized teams verse randos in matchmaking. EVE, for some ungodly reason they keep buffing the retard proof weapon systems out the ***** and are allergic to decent flight controls and instrumentation. a 3d radial isn't to much to ask. Making bullshit radials with bookmarked containers is just obnoxious.
-
grumbly (@grumblyLive) reported@BattlefieldComm The hitreg is still phenomenal dumb. I really don‘t know where the Problem is guys. If u play a round bf2042 the hitreg is so much better compared to bf6 that is just annoying and is killing off the fun with the Game.
-
Bonbonbonbons (@robonzo81) reported@BattlefieldComm Has the annoying time nudge errors been sorted or anything on the awful netcode re-introduced in s5?
-
dillon (@dpon_AK) reported@BattlefieldComm any 5000s series card users experiencing a mass amount of GPU crashes lately? I crash every game now with no solution to fix it :/
-
J. Edwards (@BigEd6530) reported@Battlefield The player has never been the captain. EA does not listen and your customer service sucks.
-
Jason Atwell (@JasonAtwell14) reportedThey could be taking a legitimate look at whether any of these recently removed generals had actually accomplished anything along the lines of adapting to the modern battlefield, but instead they're going to air the grievances of multiple anonymous sources who likely are part of the problem they claim they want to fix.
-
BlackWidow (@Blackwidow8163) reported@BattlefieldComm Also please fix the respawn beacon occasionally doesn’t work!
-
Dustin Paine (@grizzgolf) reported@Battlefield Fix Hitreg Desync and let pc turn off crossplay
-
Kurt Ambrose (@LtCmdrAmbrose) reported@EA_DICE FIX YOUR ******* GAME YOU USELESS *****
-
Azraël (@azrael_options) reported0DTE scalpers: nobody has ever blown up an account taking one trade per day on $SPX. Six trades before lunch is where accounts go to die. Overtrading is negative expectancy you volunteer for, five to eight times a day, and the industry sells it as work ethic. Why do smart traders defend the habit? → More trades feels like more control. In practice it is more crossings of the spread. → Survivorship bias runs the feed: one guy posts 8 green scalps while 400 silent accounts provided his exit liquidity. → Flat feels like losing, so you manufacture setups. Every red scalp demands revenge, every green one demands proof it was skill. → By trade 5 the desk is a casino and you are the revenue stream. Now hear the same day from the other side of the book. → Dealers classify retail market orders as the cleanest flow in the book. Every scalp hands them the spread on both sides. → 0DTE theta bleeds hardest mid-session, exactly when scalper activity peaks. You pay hourly rent on an asset built to expire worthless. → They fade the opening wick, pin price between expected move boundaries, and let the churn cook you into tilt. The real move prints after the overtraded accounts are flat and done. The fix is fewer decisions, not more discipline. → Premarket: pull VIX, compute the expected move, mark the upper and lower boundaries. That is the entire battlefield for the day. → Let the first 20 minutes play out. That window is dealer inventory reload, not opportunity. → One trade per day, taken only at an expected move boundary where dealer hedging flows actually turn. → Hard 1R cap on every position. Structure breaks, the day is over. No revenge trade, no second attempt. → Demand asymmetry: target the far boundary or the next structural shelf so the reward is multiple R against a fixed 1R. One asymmetric trade with a fixed 1R cap beats eight frantic scalps on every risk-adjusted metric that matters. That single rule carries the entire challenge I am documenting. Boring scales. Frantic bleeds. I put the entire system, the 4 trade archetypes, the Excel workstation engine, and the 20 minute opening rule into an ebook. Comment "MATRIX" and I'll DM it to you.
-
Sauce (@GotSauced) reported@BattlefieldComm Fix matchmaking and we won’t leave
-
TheSuperRebel (@TheSuperRebel1) reportedI like how battlefield 6 makes sure they have new store options and skin options but can’t fix the bugs
-
Kitch (@DHKITCH) reported@GBNEWS Having served and operated under rules of engagement, I think people need to understand the difference between a battlefield decision and an atrocity. In combat, soldiers sometimes have seconds to assess a threat and act. Those decisions must be judged in the context in which they were made. But summary executions, deliberate killings of prisoners or civilians, torture and similar conduct are something else entirely. That is where the line is clearly crossed. Investigating credible allegations of that kind is not persecuting veterans. If serious criminal misconduct occurred, service in uniform should not place anyone beyond accountability. What veterans should be protected from is endless reinvestigation of legitimate battlefield decisions without substantial new evidence. Those are two very different things.
-
TheTopMostDog 🇦🇺🐕🦺🏕️🎣🔫🪓🥩 (@TheTopMostDog) reported@Battlefield I don't understand why this needs to be a thing. Why did we have **** reticles to begin with? We went through this exact same problem before. Why can't BF learn from their mistakes?
-
رمز (@hommyramz) reported@BattlefieldComm High pings my most concerned issue not addressed