1. Home
  2. Companies
  3. Battlefield 6
Battlefield 6

Battlefield 6 status: server issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

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.

Problems in the last 24 hours

The graph below depicts the number of Battlefield 6 reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

At the moment, we haven't detected any problems at Battlefield 6. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Battlefield 6 users through our website.

  • 40% Sign in (40%)
  • 30% Online Play (30%)
  • 13% Glitches (13%)
  • 11% Matchmaking (11%)
  • 7% Game Crash (7%)

Live Outage Map

The most recent Battlefield 6 outage reports came from the following cities:

CityProblem TypeReport Time
Moûtiers Matchmaking 2 days ago
Nantes Matchmaking 3 days ago
Gramat Matchmaking 3 days ago
Amsterdam Matchmaking 4 days ago
Fontarèches Matchmaking 4 days ago
Paris Matchmaking 4 days ago
Full Outage Map

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:

  • Aimlocker2
    Aimlocker (@Aimlocker2) reported

    @Battlefield FIX THE “EVERYONE IS MEDIC” BUG

  • DrangoNew
    brand new durango (@DrangoNew) reported

    @BattlefieldComm Need to fix this annoying bug where the entire play ui bugs out when I tab out then tab back in on pc, then I have to restart everytime to get it back to normal, shouldn’t be a thing I can’t play at all until I restart! Is anyone else having this issue on pc?

  • VigilConsilium
    Vigil Consilium (@VigilConsilium) reported

    @CSIS @csisfutures Air defence is becoming a production-rate problem as much as a battlefield one. If interceptors are consumed faster than they can be replaced, even highly capable systems eventually lose coverage. The observable is sustained monthly output — not announced spending.

  • grumblyLive
    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.

  • 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

  • ekyalb
    🅱️layke (@ekyalb) reported

    @BattlefieldComm The more of these updates that come out, the more I feel like they are just centered around player count and attention. If they actually started updating major issues I have a feeling more people would be coming back, but for some reason they don't see that.

  • 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.” 𝐓𝐡𝐢𝐬 𝐢𝐬 𝐧𝐨𝐭 𝐯𝐢𝐜𝐭𝐨𝐫𝐲. 𝐈𝐭 𝐢𝐬 𝐇𝐞𝐳𝐛𝐨𝐥𝐥𝐚𝐡 𝐛𝐞𝐢𝐧𝐠 𝐛𝐥𝐞𝐝 𝐝𝐫𝐲 𝐟𝐨𝐫 𝐈𝐫𝐚𝐧.

  • Blackwidow8163
    BlackWidow (@Blackwidow8163) reported

    @BattlefieldComm Also please fix the respawn beacon occasionally doesn’t work!

  • DecodeConflict
    Decode Conflict (@DecodeConflict) reported

    AMERICA’S DRONE PROBLEM IS NOT TECHNOLOGY. IT IS PROCUREMENT. The United States can design some of the world’s most advanced autonomous weapons. Its weakness is turning those designs into inexpensive, replaceable systems at wartime scale. The Department of War acknowledges that adversaries collectively manufacture millions of unmanned systems annually while the United States has been slow to field comparable mass. Washington has responded with a Drone Dominance initiative intended to deliver tens of thousands of small drones in 2026 and hundreds of thousands by 2027. Roughly $1 billion has been allocated toward approximately 340,000 systems. A new Direct Reporting Portfolio Manager has also been given authority to coordinate the development, procurement, deployment and sustainment of unmanned systems across the military. The decision exposes the underlying problem. Responsibility was previously divided among services, acquisition offices and disconnected programs, each operating with separate requirements and timelines. The battlefield will not wait for that machinery. Ukraine has demonstrated that drone warfare evolves in weeks. Airframes, frequencies, software and tactics must be continuously modified as the enemy adapts. A system that takes years to approve may be obsolete before it reaches a combat unit. China’s advantage is not simply that it can build drones cheaply. It controls much of the commercial ecosystem that supports them, including motors, batteries, cameras, electronics and manufacturing capacity. America may design the superior platform while China retains the ability to manufacture and replace the larger fleet. Decode Conflict Assessment Drone dominance is a production contest disguised as a technology competition. Washington should purchase drones in large recurring batches, establish common interfaces, authorize frontline units to test competing systems and guarantee manufacturers enough demand to expand domestic production. The objective cannot be one perfect drone. It must be an adaptable American ecosystem capable of producing thousands of acceptable systems every month. The Pentagon has finally identified the problem. The decisive question is whether its acquisition system can move faster than the battlefield it is trying to dominate.

  • robonzo81
    Bonbonbonbons (@robonzo81) reported

    @BattlefieldComm Has the annoying time nudge errors been sorted or anything on the awful netcode re-introduced in s5?

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

  • TorsoReaper
    NameIsNotBlank (@TorsoReaper) reported

    @BattlefieldComm You're going to punish people because your matchmaking is ******* atrocious? Here's a shocking idea. FIX YOUR MATCHMAKING AND LESS PEOPLE WILL LEAVE. I know, it's a crazy idea but just try it.

  • BIG_PARMENIDES
    Not A ****** (@BIG_PARMENIDES) reported

    @Battlefield But make the damn red dots less thicc. Most of them have way too big of a dot at least for me on MnK. I doubt roller players have that issue but the dots lose effectiveness past really short ranges because they obscure the target too much.

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

  • eagles7251
    Masten Thrust (@eagles7251) reported

    @BattlefieldComm So no fix for invisible weapon after revive? No netcode improvements between console and PC crossplay?

  • 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. ???

  • mastersabin
    Sabin (@mastersabin) reported

    @BattlefieldComm again, pure nothingness to come, no major fix the game needs

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

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

  • psychfox
    Jeremy the therapist (@psychfox) reported

    “Identity diffusion is represented by a poorly integrated concept of the self and of significant others.” - Kernberg, 1984 This is the heart of borderline personality organization: not simply mood swings, but unstable self-other representation. Under threat, the self cannot mentalize (understand emotional/cognitive/behavioral causality) itself or others. One minute: “I’m safe with you.” Next minute: “You are dangerous, I am humiliated.” Identity diffusion in action: the self fractures, turning the other person into a source of fear, and the relationship consequently becomes a battlefield of unstable meanings and self-states. Kernberg saw this clearly; the problem is a self-system that loses integration when attachment is activated and vulnerability ensues.

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

  • DHKITCH
    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.

  • omniclay2
    Marc Clay (@omniclay2) reported

    @Battlefield Fix the console matchmaking! There's no reason that this is the only game that separates console players, forcing us to play with computer players or bots

  • StruckEllis3227
    Nate Ellis (@StruckEllis3227) reported

    @Battlefield Can you fix hit reg on PlayStation holy **** it’s horrific

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

  • RDSGIS
    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.

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

  • chemliakram
    AkramRock (@chemliakram) reported

    @BattlefieldComm Fix redsec

  • prozck
    Zach (@prozck) reported

    @Battlefield Sure we can stay on target all we want, doesn’t mean the bullets are going there. Fix your trash *** game.

  • 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