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 |
|---|---|
| Chalon-sur-Saône, Bourgogne-Franche-Comté | 1 |
| Mexico City, CDMX | 1 |
| Moûtiers, Auvergne-Rhône-Alpes | 1 |
| Nantes, Pays de la Loire | 2 |
| Gramat, Occitanie | 1 |
| Amsterdam, nh | 1 |
| Fontarèches, Occitanie | 1 |
| Paris, Île-de-France | 17 |
| Le Mont-sur-Lausanne, VD | 1 |
| Jauldes, Nouvelle-Aquitaine | 1 |
| City of Brussels, Brussels Capital | 2 |
| Cergy, Île-de-France | 2 |
| Annecy, Auvergne-Rhône-Alpes | 3 |
| Samatan, Occitanie | 1 |
| Carquefou, Pays de la Loire | 1 |
| Strasbourg, ACAL | 2 |
| Troyes, ACAL | 1 |
| Bordeaux, Nouvelle-Aquitaine | 4 |
| Valence, Auvergne-Rhône-Alpes | 2 |
| 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 |
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:
-
RJ owen (@RJowen56) reported@robert_lyman I suspect this is being deliberately misrepresented. No government would be that stupid to grant a blanket immunity for battlefield actions. However, immunity from post service prosecution as is occurring now in the UK over actions in N Ireland & the Troubles makes more sense
-
Gera (@GeraKerla) reported@stefayylmao1 I do not understand why we keep putting in snipers in moba shooters when they create so many issues and are extremely unfun to play against at the level that the majority of every playerbase operates on. At least in battlefield you have more meaningful ways to work around them.
-
Szymon (@simonsaypl) reported@BattlefieldComm Please FIX BF6. For the last 2 days, the game has been a mess. You dump a FULL MAG into someone, they turn around and kill you instantly. Hit registration and desync are absolutely broken. 5–8 min matchmaking, getting kicked from matches, terrible server stab
-
Iain Rae Lennox (@iainsnotes) reported@dhh I’d love to see this. I absolutely love Battlefield 6, but it’s one of the few things keeping Windows around for me. The game itself isn’t really the problem, it’s EA Javelin AntiCheat and its Windows kernel/security requirements. Proton can’t solve that from the Linux side. If some of those behind-the-scenes conversations eventually persuade EA to support Javelin on Linux/Proton, that would be huge. BF6 running properly on Omarchy would remove one of the biggest reasons I still need Windows.
-
KILL_J0HN091 (@GAMER_1411) reported@Battlefield Fix the damm audio bug/mix/blend where lobby BGM AND MULTIPLAYER OR REDSEC PLAY BOTH AT THE SAME TIME. Ita fking annoying
-
o RAY qu 🐦⬛ (@o_Ray_qu) reportedI think I’m done with Battlefield for now. I’m having a TPM 2.0 BIOS issue. I literally just started streaming again too, haha. I guess fate is trying to tell me something. 🪦
-
John Ruth (@Lfrankbaum1939) reported@Smil3yAngel I understand your anger…people don’t really care what the u.s. says….now all that aside, as a doctor, I am..I would never judge her integrity by her weight; however whatever the cause, she needs to address the issue…also if she was in combat, unless her only job was to be a sniper…she can’t be allowed on the battlefield….nothing stops her from flying drones, developing strategies…etc
-
Xero Minded (@XeroMindedSY) reported@wrenfps Yeah this game is ***. The net code, pc to console Desync, The servers lag, the audio sucks, visibility still needs improvement, no server browser, no persistent servers, there’s clearly EOMM. @EA_DICE ******* SUCKS
-
J. Edwards (@BigEd6530) reported@Battlefield The player has never been the captain. EA does not listen and your customer service sucks.
-
Royalty 👑👑 (@bash_shar) reportedCheap drones are now enough to destroy multi-million dollar tanks, and Ukraine's outgoing top general just admitted: "We're making virtually no use of armored vehicles." Modern warfare has changed. Permanently. @powerus_usa was built specifically for this moment: a counter-UAS company scaling toward vertical integration, producing drones and Guardian interceptors at scale. The old defense model, building expensive weapons in distant factories and shipping them months later, is exactly what the drone age has exposed as broken. Powerus produces close to where the threat is, at a price point the math of modern warfare actually supports. The battlefield changed faster than the procurement system did, and we're building Powerus for the battlefield that exists today...and tomorrow. Disclaimer: This content was produced in collaboration with the client and is intended for informational purposes only. It does not constitute financial or investment advice. Always conduct your own research before making any financial decisions.
-
Mind of the Motherland (@UncolonisedMind) reportedOne thing I genuinely don’t understand is how some people can acknowledge that colonialism obstructed Africa’s development, yet somehow refuse to recognise that neocolonialism continues to do the same thing, in some cases even worse. Is the difference simply that the white man is no longer physically there to administer it? There is no meaningful difference between the colonial master and the local agent who administers the same system on his behalf. Your mistake is thinking these people are your people simply because they look like you. Physical appearance does not change the interests they serve, the system they uphold, or the consequences of their actions. Neocolonialism does not require the continued physical presence of the colonial master. It works precisely by reproducing the interests and structures of the former colonial order through local institutions, elites and agents. There is no “post-colonial era”. There is the pre-colonial era, the colonial era, and the neocolonial era. The system continues. The administrator changed. The structure of ********** did not. Replacing one agent with another is not the same as destroying the system entirely. And this is why understanding what we are fighting matters. If you do not understand the battlefield, you can defeat a local agent and still fail to defeat the system that produced and empowered that agent. You may mistake a few concessions and reforms for sovereignty, only to find yourself reproducing the same system under a different administration. And eventually, you either become another agent of that system or you are removed and replaced by one. When people tell you about neocolonialism, they are not denying the actions of its local agents. They are trying to give you a fuller understanding of what you are actually fighting. Because if you think the local agent is the entire problem, you will celebrate replacing the agent while leaving the system intact. The system is not failing. It has not failed. It is working as designed.
-
Slightly Concerned (@RDSGIS) reported@1492SPANIARD @Battlefield I had the same problem with my 7950x3d. I had to make sure my cores were parking and I also made an .ini to force the game to utilize cache. DLSS and frame gen with a touch of motion blur made it look nice out of my 5080. Hardly any artifacts. Temps stayed around 65c max.
-
BigCheeseTX (@BigCheeseTX) reported@Battlefield This mode has been completely ruined by people camping the ships before it's open. Teams don't care who wins they just want to troll the other carrier. I can't play it anymore. Make the opponent ship out of bounds until the 50% is hit, when it has been opened, that would fix it
-
Aitvaras (@Aitvaras2726601) reported@BattlefieldComm For a small bugfixing patch, this is pretty good. Now we just need a few decent feature patches that actually address the major issues.
-
oobie (@oobiewpb) reportedsolana:J3NKxxXZcnNiMjKw9hYb2K4LUxgwB6t1FtPtQVsv3KFr $SPY $QQQ $IGV $IWM DLMM MATERIAL-SHIFT ALERT — TUESDAY, SEPTEMBER 1 — 2:51 PM ET STATUS: RED — VOLATILITY HAS REJOINED THE SELLING This is a meaningful change from the 2:00 PM check. The missing confirmation then was volatility. SPX had lost 7650 again and small caps were deteriorating, but VIX had backed away from its morning high. That has changed. VIX has now pushed to approximately 16.12, up about 8% on the session and its highest level since August 4. So the afternoon alignment is now considerably cleaner: SPX DOWN ~0.6–0.7% NASDAQ DOWN ~0.9–1.0% RUSSELL 2000 DOWN ~1.1% VIX ~16.12 / +8% 10-YEAR ~4.79% BRENT NEAR $94 OIL AND YIELDS BOTH REMAINING PRESSURE POINTS. That is the volatility confirmation we specifically said would escalate the 2 PM warning. WHY THIS MATTERS The sequence today has become unusually clean: SPX broke 7650 this morning. Buyers reclaimed it. The reclaim failed. SPX lost 7650 again. IWM lost the breadth level. QQQ/Nasdaq remained weak. And NOW volatility is expanding again. That's a much different setup than a simple red afternoon. The options market is beginning to price more movement at the same time price is struggling to repair broken structure. There is another interesting piece. Today's SPX 7700 0DTE calls have seen more than 23,000 contracts trade against only about 2,400 contracts of prior open interest, and the contract has collapsed roughly 96% as SPX remained well beneath the strike. That is not by itself a directional flow signal—we cannot tell from volume alone who initiated every trade—but it illustrates how aggressively today's same-day upside premium has been destroyed as price remained beneath the former 7675–7700 battlefield. I would NOT translate that into "dealers must sell." We don't have sufficient public intraday information to establish that confidently. But combined with the renewed IV expansion, it tells us the 0DTE environment is becoming less forgiving into the final hour. THE 3 PM MAP SPX 7650 Still the heartbeat. At this point a simple touch above it isn't enough. I want: 7650 reclaimed → held → expansion away from it. Otherwise it remains failed-reclaim territory. SPX 7675–7685 This remains the real repair zone. Getting back there would tell us the afternoon volatility expansion failed to produce additional downside acceptance. SPX 7700 Major repair. Given today's action, reaching and holding 7700 would represent a significant seller failure. IWM Small caps remain the breadth warning. Russell 2000 is down roughly 1.1%, materially worse than SPX. If IWM makes another afternoon low while SPX remains beneath 7650, breadth continues confirming the weakness. QQQ Technology remains important, but IWM is actually giving us the stronger risk message now. QQQ weak + IWM substantially weaker = pressure is no longer isolated to mega-cap duration. WHAT WOULD ESCALATE THIS AGAIN SPX stays beneath 7650 → afternoon low breaks → QQQ makes a corresponding new low → IWM makes another low → VIX expands THROUGH 16.12 rather than merely touching it. That would be the closest we've been today to a genuine late-day volatility/dealer-risk acceleration environment. WHAT WOULD DEFUSE IT SPX reclaims 7650 → holds → attacks 7675 while VIX falls back beneath 16 and IWM stops making lows. That would tell us the volatility spike failed to convert into additional price damage. CURRENT READ: RED — PRICE + BREADTH + VOLATILITY ARE ALIGNED AGAIN. The important change since 2 PM is NOT another few SPX points lower. It's that fear finally caught back up with price. And with barely an hour remaining, that matters because 0DTE positioning is becoming increasingly sensitive to every move away from the strikes where today's contracts were concentrated. Don't chase the red candle. Watch whether sellers can KEEP SPX beneath 7650 while VIX holds above 16. If they can, the final hour deserves respect. If they can't, today's repeated failure to hold below 7650 becomes the story all over again. ~oobie