Battlefield 6 status: server issues and outage reports

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.

Most Reported Problems

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

• Sign in (43%)
• Online Play (28%)
• Glitches (14%)
• Game Crash (8%)
• Matchmaking (6%)
• Hacking / Cheating (0%)

Live Outage Map

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

City	Problem Type	Report Time
Brasília	Online Play	12 hours ago
Arlon	Glitches	2 days ago
Coyoacán	Sign in	2 days ago
Saint-Malo	Online Play	7 days ago
Buenos Aires	Sign in	8 days ago
Comuna 1	Online Play	8 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:

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

  @M2Games2 Battlefield at your service😭

• 
  o RAY qu 🐦‍⬛ (@o_Ray_qu) reported 7 minutes ago

  I 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. 🪦

• 
  Barabilo T (@BarabiloT) reported 8 minutes ago

  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.

• 
  Dustin Paine (@grizzgolf) reported 8 minutes ago

  @Battlefield Fix Hitreg Desync and let pc turn off crossplay

• 
  ℜ𝔶𝔞𝔫 🇺🇲 (@OfcRyan79) reported 11 minutes ago

  @BattlefieldComm How about fixing the issue of not connecting with your team when the round loads?

• 
  🗡fer (@redpotionseller) reported 12 minutes ago

  @Skitzotech @Battlefield These look much sharper so they wont be lost when you're trying to aim at literally anything. Old reticles were incredibly blurry and would disappear into any scenery.. skill issue if ur still gnna find something to complain about lol

• 
  Not A ****** (@BIG_PARMENIDES) reported 12 minutes ago

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

• 
  Archaeo - Histories (@archeohistories) reported 15 minutes ago

  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

• 
  Bonbonbonbons (@robonzo81) reported 16 minutes ago

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

• 
  RJ owen (@RJowen56) reported 18 minutes ago

  @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

• 
  Xaos Kun (@XaosKun_YT) reported 20 minutes ago

  @BattlefieldInte wtf is that? @Battlefield Yall need to fix that garbage

• 
  Rosemary O'Connell (@RosemaryOConne6) reported 23 minutes ago

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

• 
  Jeremy the therapist (@psychfox) reported 26 minutes ago

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

• 
  TheSuperRebel (@TheSuperRebel1) reported 27 minutes ago

  I like how battlefield 6 makes sure they have new store options and skin options but can’t fix the bugs

• 
  Joe (@MonFartS) reported 28 minutes ago

  @BattlefieldComm Fix the spawn beacon not working

• 
  Andrew Lydiard (@andrewlydiard) reported 29 minutes ago

  @BattlefieldComm In RedSec, there are still some glaring issues like the Recon drone being unable to ping, which is kind of the entire point of it. The SVD still being overly oppressive, sniping being all but useless. These are CORE game issues you have to address sooner rather than later.

• 
  Dustin Paine (@grizzgolf) reported 32 minutes ago

  @BattlefieldComm Fix the Desync already

• 
  Howard Roark (@J_Galt_I_Am) reported 34 minutes ago

  @BattlefieldComm Can you fix the hit reg on the tv missile on the F18. It will phase through moving targets or bounce off.

• 
  David (@RightByTheSea) reported 41 minutes ago

  @Battlefield Lasers don’t line up with the sight fix that morons

• 
  oobie (@oobiewpb) reported 43 minutes ago

  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

• 
  zenStrategist 🇬🇧🇮🇱⚔️🌸 (@zenstrategist) reported 44 minutes ago

  @Lindstar24 Imagine you've shot been shot to pieces on a battlefield. They send for a medic. They send private Burnham. He stands there and tells you that he wants to fix everything, but clearly hasn't got a clue how to do anything. And you wonder why everyone suddenly gets nervous?

• 
  AkramRock (@chemliakram) reported 45 minutes ago

  @BattlefieldComm Fix redsec

• 
  JaeTwoTimez (@Jaetwotimez323) reported 45 minutes ago

  Shocker so many issues with #redsec @Battlefield @BattlefieldComm

• 
  Andrew Lydiard (@andrewlydiard) reported 45 minutes ago

  @grvmpss @Tremourx47 @BattlefieldComm It's been that way for months. It's not like we didn't use it for that time. It's not a **** you, it was a free item that wasn't terribly difficult to obtain. You didn't purchase anything. This is better for the health of the game (albeit lightly so given other issues).

• 
  Nick (@Minoanlitigator) reported 46 minutes ago

  @RichardMarlesMP @JDVance Do you have cabbage for brains? In the last 18 months DC has made it abundantly clear they don't care about Americans, Europeans, Koreans, or any other country except Israel. Even assuming the US would do more than pay lip service the battlefield has revealed a paper tiger.

• 
  LaDeX (@LaDeXi) reported 53 minutes ago

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

• 
  Slightly Concerned (@RDSGIS) reported 54 minutes ago

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

• 
  Papi Wolf (@thePapiWolf) reported 57 minutes ago

  @GameBoostCom @RinoTheBouncer Slight argument to size of game. Example, Battlefield 6 is a much bigger game. More modes, more graphics, more happening. 16GB. CoD, complete opposite, almost 400. The problem isnt necessarily the size of game, rather than the studio doing its job ensuring the game is reasonable.

• 
  Lets negotiate (@EliteKingDarth) reported 1 hour ago

  @Parasite Why dont they make the change like all previous cods bro? Simple fix we dont want alot of settings like battlefield

• 
  Derkin 🇫🇷 ベジット (@Derkin_) reported 1 hour ago

  @piccolofanb0y @SlightlyAni Problem is on metal coola team i rather play a free to play Battlefield LR (Lude) than hiru. Lude tanks better and has a giant form for hard moment. And he hit harder. And for the other spots he is nowhere near any titular option on mc team