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 (29%)
• 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
Recife	Online Play	23 hours ago
Brasília	Online Play	4 days ago
Arlon	Glitches	5 days ago
Coyoacán	Sign in	6 days ago
Saint-Malo	Online Play	10 days ago
Buenos Aires	Sign in	12 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:

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

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

• 
  Ax1omVoid (@Ax1omVoid) reported 6 minutes ago

  WTF WEDNESDAY is officially entering the rotation. 📷​ Battlefield 6 is the move tonight — I’ve played it before, just never brought it to stream. Only problem: the download apparently has other plans. The second it finishes, we’re going straight into the chaos. 📷 Twitch + YouTube tonight.

• 
  Andres Solomon (@AndresSolomon2) reported 9 minutes ago

  @Battlefield Some unpaid intern did this in an afternoon and has been a problem since day one. lmao.

• 
  Alex Devine (@SwiftyLunatic) reported 13 minutes ago

  @BattlefieldComm Let's hope you actually fix the issues you listed! Most of the time, you just write words and never fix the issues!

• 
  Joe (@MonFartS) reported 13 minutes ago

  @BattlefieldComm Fix the spawn beacon not working

• 
  HellBoundLycan (@madruger) reported 13 minutes ago

  @WolfGangPlays to be fair I think all sports games are just the same thing over and over again... Same with CoD and Battlefield. It's the same game with the same content, just a different year. *i complain about those too for the same problems.* There's so much hype over so much broken.. :(

• 
  Decode Conflict (@DecodeConflict) reported 16 minutes ago

  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.

• 
  UNALIENABLE RIGHTS (@F1sT) reported 17 minutes ago

  @LaymanPlays @IamplayerXYT This reply is doing the usual dodge: treat “this looks copied and thin” as “you’re crying because Battlefield exists.” Those are not the same argument. Layman’s post is basically: 1. Yes it looks like a BF6 map. 2. It’s better. 3. BF6 will die, Warzone won’t. 4. Therefore you’re wrong. 1 can be true and 2/3 still don’t answer the complaint. A mode can look like Battlefield, live on a bigger platform, and still be a half-finished clone. Population is not a design review. Warzone can outlive BF6 for brand, habit, SBMM, streamers, and the CoD install base. That does not mean IW put a finished large-scale mode on the map, or that classes/layout/pacing were thought through instead of traced. My “point” is the cleaner one: if you’re going to take the Battlefield shape—bigger space, vehicle/class flavor, a map that reads like theirs—don’t ship the crayon version and call criticism fragility. “I like it” is fine. “It’s good because WZ won’t die” is not a rebuttal. That’s just saying the bigger product can absorb a lazy mode. That’s also the same pattern as the TTK / studio-collage stuff. Support teams and live-service cadence make it easy to drop a familiar silhouette (“this is our Battlefield-coded playlist”) without owning the rules that make that silhouette work: readable sightlines, class jobs that aren’t CoD loadouts with new names, spawn logic that isn’t 6v6 logic stretched, vehicles that aren’t props. Copying the postcard and keeping CoD’s leftover systems is half-assing a mode. You can like the postcard. That doesn’t make the mode finished. So no, im not crying that someone enjoys it. Im “saying” IW borrowed the look, didn’t finish the game inside it, and the “BF6 will die” line is just covering for that.

• 
  TROUBLE (@Johnny316420) reported 17 minutes ago

  @DethNade @BattlefieldComm They’re cooked.. it goes to show you it’s not a money thing. You can spend and support a game and EA and battlefield can’t make a game that will work right. This game since day one has lighting issues, falling through the buildings, and they patch a EOD arm smh

• 
  MrMcGugan (@TheRobbieBlair) reported 17 minutes ago

  @1godimak @BFBulletin Why would the fps of last year worry about gunplay? 35 million people who bought Bf6 and are NOT playing it just love wondering why theyre shots are ghosting Bullet sponge Battlefield is NOT working for anyone Its hard to believe that this game is being run by a 30 yo company

• 
  Sabin (@mastersabin) reported 17 minutes ago

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

• 
  Not A ****** (@BIG_PARMENIDES) reported 18 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.

• 
  Xaos Kun (@XaosKun_YT) reported 23 minutes ago

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

• 
  D💯 (@Blizzy63) reported 24 minutes ago

  @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

• 
  💁🏻 James (@brotherhoodcree) reported 26 minutes ago

  @Ryangofett_2490 @Battlefield pls fix it and add this weapon 🙏🙏

• 
  BKScoPe (@BKScoPe) reported 26 minutes ago

  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.

• 
  Aric Chen (@aricchen) reported 28 minutes ago

  Japan put 8.9 trillion yen on the table Monday for fiscal 2027, a record request, and left more than 100 line items unpriced. Prime Minister Sanae Takaichi is rewriting the three security documents before year-end. The final figure is widely expected to clear 10 trillion yen. That is not a rounding error. It is Tokyo deciding that the cheap, attritable systems the PLA already fields in quantity are now Japan's problem to solve at scale. The Defense Ministry is asking for attack drones that can launch from the surface or from underwater, built at home, produced fast and cheap, and flown with standoff missiles. Officials point to Ukraine. They also want an AI coordinator inside command and control so battlefield assessment and target selection move faster than a human staff can cycle. A ministry cloud is meant to keep classified traffic up when the network is under stress. I have watched Japanese cabinets talk around this problem for years. This request does not. Shinjiro Koizumi's ministry is buying tools that raise the cost of a first move across the first island chain. Beijing still calls any Japanese hardening "new militarism." Koizumi already answered that in Singapore: China fields nuclear weapons and strategic bombers. Japan does not. The budget paper is the operational follow-through. The 2022 documents put spending on a path to 2 percent of GDP. Tokyo hit that two years early. This request is the bridge to whatever Takaichi writes into the revised strategy. The blank lines are the tell. They are holding space for a larger counterstrike architecture, not padding a press release. If the PLA assumed Japan would stay a high-end, low-volume force that runs out of munitions in week one, that assumption is being written down. ACI — Aric Chen | Insights

• 
  Miguel Carones (@s3n0rac) reported 31 minutes ago

  @BUZZ3RX @BattlefieldComm lol dude while that would indeed be great, the game has a ton of different technical issues that it needs to solve before even starting considering such things

• 
  LetMeOffThisRide (@in_TSMWEL_era) reported 32 minutes ago

  @Blizzy63 @BattlefieldComm Half the **** you're complaining about has been addressed, you just still don't like it. There's a difference in something being broken and you just sucking too much to recognize it's a skill issue

• 
  posiedon1971 (@posiedon1971) reported 32 minutes ago

  @BasilTheGreat Brown people will be the majority in the public service, professional services and the intelligence agencies while white people will be dying on the battlefield - it is a very deliberate and calculated policy. Pretend it isn't at your own peril!

• 
  Tom (TheLankySoldier) (@TheLankySoldier) reported 36 minutes ago

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

• 
  EvilToolLord 🇦🇺🎸🎮 (@EvilBeastLord) reported 37 minutes ago

  positive feedback It was easy to play with 6 people last night in @Battlefield (It shouldn’t have taken till season 3) But at least we could join games!! Now we have had it when at the end of a round we end up in different servers… I wonder what/could fix that. @T0TALfps

• 
  oobie (@oobiewpb) reported 40 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

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

  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.

• 
  NameIsNotBlank (@TorsoReaper) reported 44 minutes ago

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

• 
  TallJohnSilver (@TallJohnSilver) reported 49 minutes ago

  @_ITYSL Sun Tzu would call that a failure of target selection. The joke was aimed at the spectacle and the institution --not the children. If you can’t distinguish the battlefield from the collateral, that’s your tactical error.

• 
  BUZZ3R (@BUZZ3RX) reported 51 minutes ago

  @BattlefieldComm fix the anti cheat errors causing game/pc to crash

• 
  Iain Rae Lennox (@iainsnotes) reported 54 minutes ago

  @dhh I’d love to see this. I absolutely love Battlefield 6, but it’s one of the few things keeping Windows around for me. The game itself isn’t really the problem, it’s EA Javelin AntiCheat and its Windows kernel/security requirements. Proton can’t solve that from the Linux side. If some of those behind-the-scenes conversations eventually persuade EA to support Javelin on Linux/Proton, that would be huge. BF6 running properly on Omarchy would remove one of the biggest reasons I still need Windows.

• 
  Stormfall (@stormfall33) reported 56 minutes ago

  Star Wars Zero Company really surprised me with its characters and dialogue. It's written very well. The problem is the gameplay is too simple, anyone playing the game for few hours could think of 10 ideas to make it more fun and it just feels like they needed a few months to add in deeper mechanics and dial the balancing in. There's 7 characters and you can recruit up to 20 people for your team.. but the squad cap is only 4 and the people you don't take on missions have nothing to do so most of them are never being used. It's also very hard for them to die so you aren't going to be cycling in and out characters. Making and recruiting your own custom characters is pointless because if I can only use 4, why would I take Glup Shitto over a Jedi and a Mandalorian? There's no A-team and B-team to manage, it's just "pick your 4 favorites" You can send crew members on unplayable operations but it doesn't seem to matter who you send for what task. Each mission has a briefing that tells you NOTHING about what the battlefield will be like or who you might want to bring with you on the mission, and when the mission starts all your characters are randomly placed so you usually end up with your supports stuck in the frontline while your tank is in the back. I'm new to XCOM-likes but all of this seems like no-brainer fixes that will hopefully happen in future patches. 👍

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

  @M2Games2 Battlefield at your service😭