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
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
Persan, Île-de-France 1
Metz, ACAL 3
Aubais, Occitanie 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:

  • VincentKellam
    JUST KICKASS BABY #RN4LIFE (@VincentKellam) reported

    @HondoCarpenter THE @RAIDERS MAY HAVE SIGNED & DRAFTED NEW QBS YET MAJOR ISSUES AT R-TACKLE REMAIN,& THEY JUST WAIVED{DALTON WAGNER}WHOM IS THE CORRECT REMEDY TO THE 12.5 SACKS SURRENDERED BY DJ GLAZE LAST YR. GLAZE SHOULD HAVE BEEN THE PLAYER DEVELOPING ON THE P-SQUAD & NOT ON THE BATTLEFIELD

  • Hicham825
    𝕳𝖎𝖈𝖍𝖆𝖒💛💙🕊️ (@Hicham825) reported

    @M2Games2 Battlefield at your service😭

  • archeohistories
    Archaeo - Histories (@archeohistories) reported

    Jacob Miller was a Union soldier in the 9th Indiana Infantry who fought at the Battle of Chickamauga in 1863. During the chaos of the fighting, he was shot directly in the forehead, the bullet entering above his left eye. The impact knocked him unconscious, and he was left on the battlefield assumed dead, one of thousands lying among the fallen. When he eventually regained consciousness, he found himself surrounded by bodies and had to crawl toward help, bleeding heavily and barely able to see. Amazingly, Miller survived long enough to reach a field hospital, but even there surgeons believed he wouldn’t make it. The wound was so severe that they didn’t attempt to remove the bullet; they simply cleaned the area and bandaged him. Miller endured weeks of agony, infection, and partial blindness, yet he continued to cling to life. Eventually he recovered enough to return home, though the bullet remained lodged in his skull. The wound never fully closed, leaving a permanent hole in his forehead that became his most recognizable feature. For the next 31 years, Miller lived with the bullet still inside his head. He suffered chronic pain, headaches, and vision problems, but he also became a living symbol of Civil War resilience. In 1894, three decades after Chickamauga, surgeons finally removed the bullet, which had slowly migrated and caused worsening symptoms. Miller lived into old age, proudly wearing his veteran’s medal and often photographed to show the extraordinary injury he had survived. Jacob Miller spent years after the war writing letters to military surgeons because his head wound kept “changing.” The hole in his forehead never fully healed, and he reported that tiny bone fragments would occasionally work their way out decades later. Even stranger, Miller said he could feel weather changes inside the wound, pressure shifts, storms, and cold fronts caused sharp pain where the bullet sat lodged behind his eye. His case became so unusual that medical journals quietly circulated his letters as an example of long‑term cranial trauma survival. #archaeohistories

  • 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

  • eagameover
    SONS OF LIBERTY -MAGA MOVEMENT !!! (@eagameover) reported

    RESPECT 🫡 🇺🇸 AND HONOR !! 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 Lawrence Joel was sh*t through the chest and left for dead in a Vietnam battlefield, but the Army medic refused to stop. He treated wounded soldiers under machine-gun fire, dragged men to safety, and kept fighting until his own body gave out. Joel was serving as a medical specialist with the 1st Battalion, 503rd Infantry Regiment, 173rd Airborne Brigade. It was November 8, 1965, near Bien Hoa, Vietnam. His unit came under a massive enemy attack. North Vietnamese and Viet Cong forces opened fire from hidden positions. American soldiers were being hit everywhere. Joel ran toward them. He treated the wounded. Then he was shot. A bullet entered his chest. He collapsed. The enemy kept firing. Joel got back up. He continued treating casualties while bullets ripped through the battlefield. Then he was shot again. And again. He refused evacuation. He kept moving between wounded soldiers. He bandaged wounds. Administered medication. Dragged men away from exposed positions. At one point, he crawled toward a soldier who was bleeding heavily and treated him while enemy fire continued around them. Joel eventually suffered multiple gunshot wounds. He was losing blood. He was exhausted. But he refused to stop until the wounded men were stabilized. When reinforcements finally arrived, Joel was evacuated. He survived. For his actions, he received the Medal of Honor. He became the first living African American soldier to receive the Medal of Honor for actions in Vietnam. But the story didn't end there. Joel continued serving in the Army. He later worked with veterans. He retired after more than 20 years of service. Lawrence Joel died in 1984. He was 57. His legacy was later honored when the U.S. Army named a clinic after him. The soldier who had been shot and left for dead became a symbol of battlefield medicine. He didn't stop because he was wounded. He kept treating other soldiers while bleeding himself. Lawrence Joel was shot repeatedly in Vietnam. He kept crawling toward the wounded.

  • JasonAtwell14
    Jason Atwell (@JasonAtwell14) reported

    They 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.

  • krystos1k
    krystos1k🇺🇸🇩🇴🇭🇹 ☦︎ (@krystos1k) reported

    @JoeViller @BattlefieldInte I can switch between any other battlefield and have no issue. This game doesn’t move like the others. If I want to play COD I go on there this isn’t COD.

  • TheInfamousEG
    🌹 The Infamous E.G.🌹 (@TheInfamousEG) reported

    If im wrong about the frostbite engine being the reason it takes them so long to fix bugs that LITERALLY get unfixed the next patch later in Battlefield How come non Battlefield games had SIMILAR problems including SINGLE PLAYER games

  • BKScoPe
    BKScoPe (@BKScoPe) reported

    been sitting with one idea about @quipnetwork for a few days now. what if the work that secures a chain was also the work someone actually needed solved. not hashes for the sake of hashes, actual optimization problems, proof of useful work instead of proof of work. i keep going back and forth on what that actually changes. one side of me says it's just a scoring trick, put every kind of hardware on the same problem and call it fair. the other side wonders if this is actually the first time cpus, gpus, asics, and quantum machines get measured on one shared battlefield instead of separate leaderboards. both feel true at once. quantum capacity right now mostly sits behind a handful of closed platforms, expensive, gated, hard to even test against. if this holds up at scale, that idle capacity starts looking like infrastructure other people can actually rent and check the work on. researchers get a reason to point real problems at it instead of vanity benchmarks, and operators get a reason to keep machines running past the demo phase. none of that is guaranteed yet, still early.

  • RosemaryOConne6
    Rosemary O'Connell (@RosemaryOConne6) reported

    I want to talk against alcohol. It's not cool. It's pathetic. People have a problem& they NEED to numb themselves like they were in screaming agony on the battlefield? It's pathetic. You CAN handle your problems. And you CAN handle an alcohol or drug pusher. Only a loser can't just walk away. It's ridiculous. Oh let me shoot myself up & numb myself rather than walk away from an enemy ***** or bastard. ???

  • LaDeXi
    LaDeX (@LaDeXi) reported

    @robynvanpersiee @Battlefield Then you shouldn't have trouble finding people.

  • CPryorNYC
    Clarence Alexander Pryor 🏳️‍🌈 (@CPryorNYC) reported

    @_nelsonthomas @DerrickMTV Never run away from problems. Face it and own it out there on the battlefield.

  • yuyan_mtg
    Yuya Hosokawa (@yuyan_mtg) reported

    @joseaf_PT @RWishnitze92421 @Papa_Jablo Thank you for speaking up on my behalf. Sometimes you lose easily, and other times you do not. It is a issue with lands. Since three-color commons are weak, you might lose without being able to do anything because of too many lands entering the battlefield tapped, or you might win through card power because you can use three colors. Ultimately, whether it works or not comes down to luck, and often the three-color player who was the luckiest that day wins. I understand that Magic is a game that goes hand in hand with mana screw and flood, but in Pauper, it was unbearable. Just to be clear, I am generally a good player, but I have not played Pauper since High Tide was banned.

  • shairondriel
    Shai ✨ (@shairondriel) reported

    @justqu1n THIS! It’s the way they’ve said **** like he will fix Galadriel (and by fix they mean remove her from the battlefield 🙄). Or that once he’s here Galadriel won’t ever interact with Sauron. Hello???? They are eachother’s chief foes and will remain eachother’s chief foes

  • grizzgolf
    Dustin Paine (@grizzgolf) reported

    @Battlefield Fix Hitreg Desync and let pc turn off crossplay

Check Current Status