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
Lyon, Auvergne-Rhône-Alpes 6
Châteaubriant, Pays de la Loire 1
Cesson, Île-de-France 1
Rillieux-la-Pape, Auvergne-Rhône-Alpes 1
Brest, Brittany 1
Paris, Île-de-France 21
Criciúma, SC 1
Saint-Ouen, Île-de-France 1
Oyonnax, Auvergne-Rhône-Alpes 1
Cluses, Auvergne-Rhône-Alpes 1
Mont-Bonvillers, ACAL 1
Triel-sur-Seine, Île-de-France 1
Marseille, Provence-Alpes-Côte d'Azur 2
Lille, Hauts-de-France 1
Moirans, Auvergne-Rhône-Alpes 1
Villefranche-sur-Saône, Auvergne-Rhône-Alpes 1
Meyzieu, Auvergne-Rhône-Alpes 1
Nantes, Pays de la Loire 2
Carvin, Hauts-de-France 1
Bordeaux, Nouvelle-Aquitaine 2
Ornans, Bourgogne-Franche-Comté 1
Annecy, Auvergne-Rhône-Alpes 1
La Garde, Provence-Alpes-Côte d'Azur 1
Brunstatt, ACAL 1
La Crèche, Nouvelle-Aquitaine 1
Sarreguemines, ACAL 1
Saumur, Pays de la Loire 1
Le Blanc-Mesnil, Île-de-France 1
Saint-Nazaire, Pays de la Loire 1
Bracieux, Centre 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:

  • Fredvelezcrypto
    Fred Velez (@Fredvelezcrypto) reported

    Morning BTC read: The chart is still not pretty. BTC rejected the $65.5K–$66.5K range high and is now sitting closer to the lower half of the current battlefield. Right now, I see the active range like this: Range high: $65.5K–$66.5K Mid-zone: $62K–$64K Range low: $60K–$61K Major line: $58.1K The liquidation heatmap also shows liquidity stacked below, especially around the $61K–$62K area, with deeper danger still near $60K. So yes, BTC can still sweep lower. But here is the key: this is not confirmed collapse yet. It is a market trapped in a violent range. The problem for bulls is ETF flows are not helping. Another red BTC ETF day. Roughly -$90.7M yesterday. That comes after -$82.2M the day before. So the market has: weak ETF demand negative structure liquidity below DXY still elevated and BTC below the reclaim zone That is not the setup for blind optimism. For bulls, the first job is simple: reclaim $64K–$64.5K. Then $65.5K–$66.5K. Until then, every bounce is just a bounce inside a damaged range. If BTC loses $62K cleanly, I think the market starts hunting $60K–$61K again. If BTC holds this zone and reclaims $64K+, then we can talk about stabilization. No need to overcomplicate it. BTC is not dead. But buyers have not taken control. This is still a trigger market. No confirmation, no conviction.

  • MarkSimonHK
    Mark Simon (@MarkSimonHK) reported

    @hughhewitt @philipaklein Once we start going down in the weeds, is there any chance the American people are on board with continued war? - This is turning into a Foreign Policy/DC issue. Is it top five in voters minds if US troops are not on the battlefield?

  • OSINToffenders
    Robbie K (@OSINToffenders) reported

    @BattlefieldComm I had an issue near crash site where the entire screen looked like I was going through a dust storm.

  • NewsTongueX
    NewsTongue (@NewsTongueX) reported

    🔴 Marine vet uses combat first aid to save trucker's life after highway crash James Brown, a 12-year US Marines veteran driving for Melton Truck Lines, witnessed another truck driver lose control and overturn on 22 May near Little Rock, Arkansas. The crashed driver had a piece of metal lodged in his leg; when the man pulled it out, Brown saw he had severed an artery and was bleeding heavily. Brown cut up a seatbelt and fashioned a tourniquet, applying battlefield medical training from his service. "He wasn't making much sense and had lost quite a bit of blood" by the time first responders arrived, but remained conscious.

  • Smokemifyo14691
    3 KingsInPersia (@Smokemifyo14691) reported

    @BattlefieldComm @Battlefield I’m tired of getting killed behind walls and solid objects, I’m tired of poor hit registration, I’m sick of getting killed with 1 bullet. I’m just tired fix it. NOW!! No more lightning fast kills no more

  • miahfuta
    Miah (@miahfuta) reported

    @BattlefieldComm You need to fix the world render distance cap you guys added in season 3. There is no reason why I should be seeing people floating on nothing when they are sitting on mountains, when I have all settings maxed out. This was never an issue before season 3 was released.

  • DundeeLord
    Lord Dundee (@DundeeLord) reported

    @NoGGiNTheNoG8 @deadlyweapns Not necessarily, but all it takes is a little bit of dirt on the wrong hydraulic piston and this whole thing goes out of service. Btw, the entire battlefield is covered in dirt. Drones don’t even need to touch it to break this thing.

  • __abioye_
    Pọ́ọ̀lù (@__abioye_) reported

    @WorldCupMedia That Canada vs. Qatar match was painful to watch—truly painful. Let's hope Ismail Koné is not badly injured, because that pitch was a battlefield of bad decisions and broken rhythm. The game was so poor, Qatar made Canada look like a Premier League side. Let that sink in. Absolutely amazing—and not in a good way.

  • GeezerJx
    GeezerJx (@GeezerJx) reported

    @Battlefield fix your game, i shouldnt have to alt-f4 to get back into a game

  • BakerBoy270895
    DarkMuffins2708 (@BakerBoy270895) reported

    @Battlefield PLEASE PLEASE fix the bug with Support Specialist Class Challenge. When ever I resupply anyone with a pouch. Team mate. Squad mate. Bot. Or enemy it doesn’t register at all. Please fix

  • Rocinantemoons
    before i slip,, ima slide♟️📜 (@Rocinantemoons) reported

    @Battlefield fck off if u not fixing server issue in ME

  • 1974nishu
    NISHIT DESAI- YOGA IS LIFE (@1974nishu) reported

    @desi_thug1 Border fencing work is also going on leaving no room for China and Bangladesh to foment trouble. With COBRA now entering the battlefield, lasting peace should be a reality in Manipur in the same way as it happened in Chhattisgarh

  • lcbchefperry
    Michael E. Perry (@lcbchefperry) reported

    @Primary_Pianist The Book of Mormon describes whole peoples, cities, buildings, wars, kings, prophets, temples, records, armies, weapons, and massive battles. Mormon 1 says the land was covered with buildings and the people were almost as numerous as the sand of the sea. Mormon 6 describes roughly 230,000 Nephites killed at Cumorah. Ether 15 describes nearly two million Jaredite “mighty men” killed, plus wives and children. Imagine someone claimed that an ancient Israelite civilization existed somewhere in North America. Not a tiny campsite. Not one immigrant family. A real civilization. Imagine it had a final battle where the dead were roughly the size of Irving, Texas population 238K. Then imagine another earlier civilization in the same sacred history lost a male fighting population roughly the size of Houston 2.4M, plus women and children. Now imagine this civilization supposedly had cities, temples, written records, named places, religious systems, kings, trade, weapons, metalwork, and centuries of history. Then ask: Would it be plausible for a civilization of that size and complexity to vanish with no confirmed city, no confirmed inscription, no confirmed Hebrew or Egyptian writing, no confirmed Nephite place name, no confirmed Israelite temple, no confirmed Book of Mormon battlefield, no confirmed “reformed Egyptian,” and no material culture that clearly identifies it? That is the issue. A small family can disappear genetically. A civilization of that scale should not disappear historically, archaeologically, linguistically, and materially. So the problem is not merely DNA. DNA is one missing footprint. But the larger issue is that almost every expected footprint is missing. At some point, “the evidence disappeared” stops being an explanation and starts becoming a shield against testing the claim.

  • 6db560c87fec4ea
    Marwan (@6db560c87fec4ea) reported

    @CallieSue1109 @Battlefield And that took them many days to fix

  • Adam9110
    GHOST (@Adam9110) reported

    @BattlefieldComm Start testing these updates, preferably daily... Because what you fixed in update 1.3.1.0, you later broke in 1.3.2.0. The netcode is broken, and it was relatively fine. The footsteps are once again inaudible. Optimization isn't great either.

Check Current Status