Battlefield 6 status: server issues and outage reports

Problems in the last 24 hours

Battlefield 6 signals over the past 24 hours. The dashed line is the service-wide baseline used to detect unusual activity.

• Service-wide signals
• Service-wide baseline

Most Reported Problems

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

• Sign in (41%)
• Online Play (29%)
• Glitches (13%)
• Matchmaking (11%)
• Game Crash (7%)

Live Outage Map

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

City	Problem Type	Report Time
Chalon-sur-Saône	Matchmaking	2 days ago
Mexico City	Online Play	2 days ago
Moûtiers	Matchmaking	5 days ago
Nantes	Matchmaking	6 days ago
Gramat	Matchmaking	7 days ago
Amsterdam	Matchmaking	7 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:

• 
  helvetica (@helvetica369) reported 2 minutes ago

  @BattlefieldComm so they are going to penalize you for leaving a match when they put you into an ongoing match where your team is already getting steamrolled? maybe fix your matchmaking and ppl wouldnt need to leave matches so often.

• 
  Isaiah 🇮🇱🇺🇲 (@brotherstrikebs) reported 4 minutes ago

  @Battlefield Yeah? How about being able to reconnect to the same redsec match after a crash?

• 
  Dustin Paine (@grizzgolf) reported 6 minutes ago

  @BattlefieldComm Fix the Desync already

• 
  Pvt_Rinzler (@PvtRinzler) reported 7 minutes ago

  @BattlefieldComm Grenades still not working. You really tested this? They are still not visible.

• 
  Aimlocker (@Aimlocker2) reported 7 minutes ago

  @Battlefield FIX THE “EVERYONE IS MEDIC” BUG

• 
  NOBUNAGA🇯🇵🏯_夏樹蒼依 (@japan_nobunaga) reported 7 minutes ago

  In Texas I went to a game where the entire student side of the stadium did not sit down for four hours. I assumed the seats were broken. I checked the one next to me. It worked. I asked a student named Tyler why nobody was sitting. He said, "In case they need us." That was the whole answer. In my land we have a saying, always on the battlefield. A samurai does not lounge in the presence of a lord who may call him. He stands, so that when the call comes there is no distance between the call and the man. Here were thirty thousand of them. Standing. In case. I asked Tyler how often they are needed. He thought about it. "Once." Once. In 1922. The team was running out of healthy men, and a student named Gill was called down out of the stands. He put on an injured player's uniform and stood on the sideline, ready, for the rest of the game. He never went in. They won without him. That is the whole origin. A man who did not play. A hundred years of standing for a man who did not play. So I stood. I am not a student. I was not going to be called under any reading of the rules. My knees began filing complaints in the third quarter and I ignored them, because Tyler was nineteen and had stood through every home game for three years and had never once been called, and was not bitter about it, and was in fact eating nachos. Nobody was called. Nobody has been called since 1922. The knees of Texas do not care. In my land we say be ready at every moment. Texas built thirty thousand seats and refuses to use them.

• 
  Alex Devine (@SwiftyLunatic) reported 12 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!

• 
  zenStrategist 🇬🇧🇮🇱⚔️🌸 (@zenstrategist) reported 13 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?

• 
  Aric Chen (@aricchen) reported 17 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

• 
  Ax1omVoid (@Ax1omVoid) reported 19 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.

• 
  AkramRock (@chemliakram) reported 20 minutes ago

  @BattlefieldComm Fix redsec

• 
  Azraël (@azrael_options) reported 21 minutes ago

  0DTE scalpers: nobody has ever blown up an account taking one trade per day on $SPX. Six trades before lunch is where accounts go to die. Overtrading is negative expectancy you volunteer for, five to eight times a day, and the industry sells it as work ethic. Why do smart traders defend the habit? → More trades feels like more control. In practice it is more crossings of the spread. → Survivorship bias runs the feed: one guy posts 8 green scalps while 400 silent accounts provided his exit liquidity. → Flat feels like losing, so you manufacture setups. Every red scalp demands revenge, every green one demands proof it was skill. → By trade 5 the desk is a casino and you are the revenue stream. Now hear the same day from the other side of the book. → Dealers classify retail market orders as the cleanest flow in the book. Every scalp hands them the spread on both sides. → 0DTE theta bleeds hardest mid-session, exactly when scalper activity peaks. You pay hourly rent on an asset built to expire worthless. → They fade the opening wick, pin price between expected move boundaries, and let the churn cook you into tilt. The real move prints after the overtraded accounts are flat and done. The fix is fewer decisions, not more discipline. → Premarket: pull VIX, compute the expected move, mark the upper and lower boundaries. That is the entire battlefield for the day. → Let the first 20 minutes play out. That window is dealer inventory reload, not opportunity. → One trade per day, taken only at an expected move boundary where dealer hedging flows actually turn. → Hard 1R cap on every position. Structure breaks, the day is over. No revenge trade, no second attempt. → Demand asymmetry: target the far boundary or the next structural shelf so the reward is multiple R against a fixed 1R. One asymmetric trade with a fixed 1R cap beats eight frantic scalps on every risk-adjusted metric that matters. That single rule carries the entire challenge I am documenting. Boring scales. Frantic bleeds. I put the entire system, the 4 trade archetypes, the Excel workstation engine, and the 20 minute opening rule into an ebook. Comment "MATRIX" and I'll DM it to you.

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

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

• 
  Iain Rae Lennox (@iainsnotes) reported 27 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.

• 
  Rosemary O'Connell (@RosemaryOConne6) reported 27 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. ???

• 
  drugrankings (@RxRankings_com) reported 28 minutes ago

  @TheBluePen25 The reality is that women or female warriors cause more problems on the battlefield. 50:50 male:female army definitely loses to 100% male army

• 
  1god-dim-mak (@1godimak) reported 29 minutes ago

  @Battlefield You ***** haven't figured it out yet. How about you fix the desync and hit reg and optimize this game as well. ******* cucks are more concerned with censorship and language use. You're disgusting and appalling.

• 
  UNALIENABLE RIGHTS (@F1sT) reported 30 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.

• 
  Aitvaras (@Aitvaras2726601) reported 31 minutes ago

  @BattlefieldComm For a small bugfixing patch, this is pretty good. Now we just need a few decent feature patches that actually address the major issues.

• 
  GoGitUrFuknShineBox (@ItsQagain) reported 35 minutes ago

  @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

• 
  KoMiNt (@_KoMiNt_) reported 36 minutes ago

  @BattlefieldComm Games are too long. Too many players. Not enough vehicles. Your broken system better know when someone leaves a match that is in progress that they get matchmade in to that is losing. Players just camp vehicle spawn and with 32 players it is an annoying feature. "Top 5%" lol

• 
  Voice for the truth (@voiceofztruth) reported 36 minutes ago

  @benshapiro @benshapiro forget about the Hareidim. Do you believe it’s ok to force people to fight on the battlefield or be conscripted to service against their will? It’s hard for me to digest.

• 
  SeekingParadise (@ParadiseSeek3r) reported 40 minutes ago

  @Rafaelmiguel89 @grok @Nirosha_31 I don't believe Jesus is "The Lord" you jeet, I am referring to standard trinitarian theology. As for your waffle about striking necks, it's obvious you want to shift the topic over like a typical jeet. We have no issue with Allah commanding that on the battlefield.

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

• 
  David (@RightByTheSea) reported 42 minutes ago

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

• 
  𝗕𝗥𝗔𝗗𝗦𝗛𝗔𝗪 👹 (@JBrdshw_) reported 45 minutes ago

  @PurpleColonelSP All of a sudden clicking L3 to sprint is an issue when CoD, Battlefield and literally almost every single ******* game in the world uses that same button. You guys just wanna find **** to cry about atp

• 
  Lets negotiate (@EliteKingDarth) reported 46 minutes ago

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

• 
  Slightly Concerned (@RDSGIS) reported 53 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.

• 
  Dajovi (@Dajovi2) reported 56 minutes ago

  @Battlefield Enough with rotating modes out of nowhere. I'm tired of checking if my favorite mode is up every single day. Just kill Portal, it’s garbage. Keep the core modes -including Rush- and fix them so they work properly. Completely useless.

• 
  ALAEHD (@ALAEHDx) reported 59 minutes ago

  @BattlefieldComm No need to fix anything Dice just leave the game as it is, you're gonna reintroduce all these bugs next season anyway as you always do.