1. Home
  2. Companies
  3. Battlefield 6
  4. Outage Map
Battlefield 6

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
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
Courbevoie, Île-de-France 1
Chaumont, ACAL 1
Check Current Status

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:

  • Abdurazok
    Abdurazok Abdulloev (@Abdurazok) reported

    @Reuters The broader strategic issue is that Moscow is running two clocks at once - a battlefield clock it says is favourable, and a fiscal clock its own officials are flagging. Wars usually end when those two diverge sharply. Worth tracking budget and borrowing data alongside frontline maps.

  • ItsQagain
    GoGitUrFuknShineBox (@ItsQagain) reported

    @Battlefield Who tf cares?? You don’t fix the **** that needs to be fixed and I’m tired of you recycling the same three maps in multiplayer..You’re so in love with empire fck off

  • PUMAonCOD
    PUMA (@PUMAonCOD) reported

    @SoaRZephy This is a cheat that I've seen happening since Battlefield. After a while it merged over to COD. It purposely pushes you off your aim. Based on your footage and my new Beta experience, they've upgraded it to also have lag spike glitches. It's garbage, dude.

  • RJowen56
    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

  • TheLankySoldier
    Tom (TheLankySoldier) (@TheLankySoldier) reported

    @BattlefieldComm What about challenge rewards that are black and can't unlock them? They been broken since mid July. All that grind and for what?

  • GauldForge
    GauldForge (@GauldForge) reported

    @BattlefieldComm No mention of the request order button… how strange? ALSO WHEN WILL YOU FIX THE RPGS AND GRENADES SPLASH DAMAGE, ITS PATHETIC THAT A POINT BLANK RPG DOESNT KILL SOMEONE. Also, I rammed a tank yesterday in a buggy with 4 C4s attached, tell me why it only done 30 vehicle damage?

  • WuuussH_
    WuuussH (@WuuussH_) reported

    @BattlefieldComm Adjusting things no one even complained about like melee weapon and not correcting proper issues. While your game is getting joked on by groundwar from cod is laughable

  • oobiewpb
    oobie (@oobiewpb) reported

    solana: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

  • Aimlocker2
    Aimlocker (@Aimlocker2) reported

    @Battlefield FIX THE “EVERYONE IS MEDIC” BUG

  • Blizzy63
    D💯 (@Blizzy63) reported

    @BattlefieldComm - no fix for black screen bug - no bullet dispersion fixes - no audio changes - no jet loadouts 5 months later - no bullet registration fixes - no dsync fixes - Asian players in US/Eu servers abusing lag comp I’m posting till **** changes… Your ******* morons

  • ZiadElkhalil
    ziad elkhalil 🇱🇧 (@ZiadElkhalil) reported

    𝐇𝐞𝐳𝐛𝐨𝐥𝐥𝐚𝐡 𝐢𝐬 “𝐰𝐢𝐧𝐧𝐢𝐧𝐠.” 🙄 Truck after truck. Coffin after coffin. Lives sacrificed, not in defence of #Lebanon, but in service of #Iran and its mullahs. #Tehran gives the orders. Lebanon supplies the battlefield, the destruction, the funerals and the dead. And then Hezbollah calls the catastrophe a “divine victory.” 𝐓𝐡𝐢𝐬 𝐢𝐬 𝐧𝐨𝐭 𝐯𝐢𝐜𝐭𝐨𝐫𝐲. 𝐈𝐭 𝐢𝐬 𝐇𝐞𝐳𝐛𝐨𝐥𝐥𝐚𝐡 𝐛𝐞𝐢𝐧𝐠 𝐛𝐥𝐞𝐝 𝐝𝐫𝐲 𝐟𝐨𝐫 𝐈𝐫𝐚𝐧.

  • DiabolicalDoDad
    DiabolicalDoodle (@DiabolicalDoDad) reported

    Dear @Battlefield Why can people jump 4 feet in the air, slide, jump, slide and then 360 no scope me with a pistol? Can you fix the bloody movement so I'm not playing COD...

  • Sjr3016
    XRPlosive (@Sjr3016) reported

    @Battlefield Get rid of the bots. How did i get a black screen, restart the game get placed in a queue and bots be in every lobby? Dumbest sht yall ever did! And fix the fking AA dropping my chopper from their spawn with that glitch guided rocket. And if i hit flares lock on shouldnt hit

  • JiveTurkey600
    Your girl came over drunk, i said she was lagging! (@JiveTurkey600) reported

    @BattlefieldComm Kicking AFK players but not giving us a Chance to Reconnect (in Redsec) if we disconnect is CRAZY!!! @DRUNKKZ3 @BattlefieldComm Sorry Florian lol

  • BarabiloT
    Barabilo T (@BarabiloT) reported

    I keep coming back to one idea with @quipnetwork : what if the work that secures a chain was also the work someone actually wanted done? Instead of burning energy on meaningless hashes, Quip has miners compete to solve real optimization problems through Proof of Useful Work. That means CPUs, GPUs, ASICs, and quantum machines can be measured on the same battlefield. If this works at scale, unused quantum capacity could become accessible, verifiable infrastructure, while researchers and hardware operators get a clearer incentive to contribute. Feels like an early building block for a future where quantum compute is shared globally, not locked behind a few closed platforms.

Check Current Status