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.

• Online Play (35%)
• Sign in (34%)
• Glitches (13%)
• Game Crash (9%)
• Matchmaking (8%)
• Hacking / Cheating (1%)

Live Outage Map

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

City	Problem Type	Report Time
Lyon	Sign in	1 day ago
Châteaubriant	Online Play	1 day ago
Cesson	Sign in	1 day ago
Rillieux-la-Pape	Online Play	1 day ago
Brest	Sign in	1 day ago
Paris	Game Crash	1 day 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:

• 
  Ryan (@Hoskins1st) reported 1 minute ago

  @BattlefieldComm How can someone have the battle pass and still can’t get into the shop to receive the free gift from buying the battle pass. That’s makes no sense that you lock them out completely. Support has never responded to the problem. @Battlefield @BattlefieldComm

• 
  Mo.aly (@snipermomo_1994) reported 2 minutes ago

  @BattlefieldComm Plz, Recon class in Redsec solos is broken. at least Try to limit the number of usages of the drone. Make it limited to 3 times during the whole match.

• 
  NISHIT DESAI- YOGA IS LIFE (@1974nishu) reported 3 minutes ago

  @desi_thug1 Border fencing work is also going on leaving no room for China and Bangladesh to foment trouble. With COBRA now entering the battlefield, lasting peace should be a reality in Manipur in the same way as it happened in Chhattisgarh

• 
  AcklesTV (@AcklesTTV) reported 4 minutes ago

  @BattlefieldComm WE HAVE BEEN TRYING TO QUE IN RANKED FOR AN HOUR!!!! WE KEEP GETTING SOME ERROR CODE AND NOTHING WE DO WILL FIX IT. FIX YOUR DAMN GAME!

• 
  Jexxits (@JexxitS) reported 5 minutes ago

  @BlackEaglesFRVR @BFBulletin I've played Battlefield since 1942 so whatever. But didn't they remove it bc they have problems with the mode?

• 
  Erick (@Erickschultz11) reported 7 minutes ago

  @mattvanswol We trust institutions to investigate wrongdoing fairly, yet repeated scandals have left many people questioning whether similar failures are treated the same way. Some see accountability being shaped by power, ideology, reputation, fear, or institutional self-protection. Others argue that different cases simply involve different facts, evidence, and constraints. The problem is not necessarily that institutions are acting in bad faith. They may genuinely believe they are applying consistent standards, weighing evidence carefully, protecting due process, avoiding prejudice, or balancing competing social concerns. The deeper issue is that much of this reasoning is often invisible to the public. When decisions are opaque or difficult to scrutinize, people cannot easily distinguish between responsible judgment and narrative management. As trust declines, disagreements spread beyond the events themselves. People begin disagreeing about which sources are credible, which facts matter, and which institutions can be trusted to evaluate the evidence. The result is a crisis of legitimacy. The question is no longer just whether accountability is being applied fairly. The question becomes who gets to decide what happened, how that decision was reached, and why everyone else should trust it. The way forward is not to choose one victim narrative over another. It is to make the process itself more transparent, more consistent, and more open to scrutiny. Every case should be examined through the same questions: who was harmed, who caused the harm, who enabled it, who ignored it, who benefited from silence, and what incentives may have protected the failure? But even that requires something more. We must be willing to apply the same standards of evidence and skepticism to our own preferred narratives that we apply to those we oppose. Without that, accountability becomes another battlefield for competing stories rather than a search for truth. The real challenge is not simply rebuilding trust in institutions. It is rebuilding trust in the processes by which institutions, evidence, and public judgments are evaluated in the first place.

• 
  Marwan (@6db560c87fec4ea) reported 8 minutes ago

  @CallieSue1109 @Battlefield And that took them many days to fix

• 
  Nickmdrummer (@nick_mDrummer) reported 11 minutes ago

  @BattlefieldComm "Previously, if an XP Booster expired before the end of a match, it could miss out on applying to the Match Bonus awarded at the end of that round." This game is clearly in beta. How many hidden errors does it have?

• 
  ＧＨＯＳＴ (@Adam9110) reported 14 minutes ago

  @BattlefieldComm Start testing these updates, preferably daily... Because what you fixed in update 1.3.1.0, you later broke in 1.3.2.0. The netcode is broken, and it was relatively fine. The footsteps are once again inaudible. Optimization isn't great either.

• 
  Nick Calandra (@nickjcal) reported 14 minutes ago

  Look no further than the Battlefield franchise for a great example of how spending more and more didn't lead to better games. It led to rushed out unfinished games that took years and more money to fix, and then to get the franchise back on track even more money to do it "right".

• 
  berserk415 (@Berserk710415) reported 15 minutes ago

  @Battlefield The game is broken and old bugs are back . We are on s3 nothings gotten better. Yet we still get timed game modes not stability or new maps. Plz get it together battlefeild

• 
  Nikita Kabardin (@nkabardin) reported 19 minutes ago

  @langfuse It looked like a standard UI problem. How hard can it be? I've built filter UIs before (TV schedules, internal tools, a Battlefield server browser...), all with a fixed set of parameters.

• 
  Lord Dundee (@DundeeLord) reported 25 minutes ago

  @NoGGiNTheNoG8 @deadlyweapns Not necessarily, but all it takes is a little bit of dirt on the wrong hydraulic piston and this whole thing goes out of service. Btw, the entire battlefield is covered in dirt. Drones don’t even need to touch it to break this thing.

• 
  Whiskas (@WhiskasOfficial) reported 26 minutes ago

  @BattlefieldComm Over a week to fix Strike point?!!!! You guys suck.

• 
  𝒮𝒜𝒯𝒪ℛ𝒰 𝒢𝒪𝒥𝒪 五条 悟 (@TwoBabyBlues) reported 30 minutes ago

  ( For a moment, there was only light... ) ( Then the world came back all at once. Salt in the air. Waves crashing nearby. Armoured soldiers moving across the beach like ants stirred from a broken nest. The distant sound of battle rolled over the coastline, sharp enough to ruin what might have otherwise been a pretty view... ) ( Satoru stood there in the sand, one hand tucked into his pocket, his white hair shifting lightly with the sea breeze as he slowly looked around. ) ( Definitely not Tokyo... ) ( Definitely not anywhere he remembered agreeing to visit either... ) 𝕾𝖆𝖙𝖔𝖗𝖚 𝕲𝖔𝖏𝖔: “ Well... ” ( His head tilted slightly, gaze moving from the swarming soldiers to the strange coastline beyond them... ) “ This is either the worst vacation package ever... or I missed a very important invitation. ” ( Despite the chaos, he didn’t move with panic. If anything, he seemed far too relaxed for someone standing near a battlefield he had no explanation for. ) ( Still... his attention sharpened when he felt it. A presence nearby that didn’t quite blend with the rest of the noise. ) “ Guess sightseeing can wait... ” ( A small grin tugged at his mouth as he turned toward the source of that presence, voice carrying just enough to be heard over the waves... ) “ Hey... whoever’s running this beach party, mind telling me where I just landed...? ”

• 
  Ju. (@lakewoodxlegend) reported 31 minutes ago

  @BattlefieldComm Can we please get a fix for the “not signed into PlayStation network” error that kicks us from multiplayer matches

• 
  Biig Bo$$ (@Mike_so100) reported 33 minutes ago

  @BattlefieldComm U guys care more about a free game mode (redsec)then the multiplayer best game mode (strikepoint) how does the update not fix yalls biggest problem being strikepoint!!! 😠 I’m so done with this treatment u guys are horrible @BattlefieldComm

• 
  BillsmafiaMFKA He/Bro/Daddy (@Emanuel56353090) reported 41 minutes ago

  @Battlefield FIX STRIKE POINT AND PUT IT BACK TO HOW IT WAS ********

• 
  CAMIKAZE78 (@CAMIKAZE78) reported 46 minutes ago

  "This is what PEAK Battlefield gameplay looks like". This mode was literally you clicking prompts on an iPad, or on your PC like a cookie clicker game... This couldn't be further from "peak gameplay" in the context of an FPS game and when we consider the actual, important issues with BF6, any time spent on this feature would be wasted dev time imo.

• 
  Mr Battlefield (@MrBattlefield0) reported 47 minutes ago

  @FunzaaTV @BattlefieldComm I agree with the VPN users that are tunneling to the United States or to another region because they don't have local Servers to host their own games. Hopefully when the Full Server Browser with persistence servers will fix this problem. These players need to host a server.

• 
  『Just an Ordinary Nikke』 (@Overzone_Nikke) reported 48 minutes ago

  @UrMaidAndSpy But you shouldn't *Have* to have band aids on them. Our body is...important. to not be allowed to cover how we want can lead to issues in a battlefield.

• 
  Jacob K (@justwatchinrad) reported 49 minutes ago

  @hdagres Iran is degraded but a correct analysis. The issue wasn’t the battlefield- it was will.

• 
  BillsmafiaMFKA He/Bro/Daddy (@Emanuel56353090) reported 49 minutes ago

  @BattlefieldComm ******** FIX STRIKEPOINT

• 
  NickNaylor 🇧🇷 (@biglover9813) reported 54 minutes ago

  @BattlefieldComm Nerf M320. Fix the matchmaking: every game turns into basecamp, if you go well in a match, the next one you are punished. Change the TTK, no more 3BTK guns like SCW (1000RPM btw)

• 
  Shadow (@ASmoothTaurus) reported 55 minutes ago

  @Battlefield Does anybody know why when console types this code it in doesn’t load it takes us to a blank screen with nothing showing? Is there a fix for this?

• 
  J-Dizzle (@Lucky_Bullet) reported 55 minutes ago

  @BattlefieldComm what the F is going on with StrikePoint! F……….! Can you fix it any slower!

• 
  Legal Style Blog (@legalstyleblog) reported 56 minutes ago

  @GrenadaLoyalist sigh heraldry is premised on clarity (seeing it across a battlefield). Maybe I don't know the iconography and it's a me problem, but I would not recognize the drum without knowing it was one

• 
  chris (@ChrisSlaske) reported 58 minutes ago

  @Battlefield nice job making the game go black screen with today's update. Guess you didnt fix it

• 
  NodeAspect (@IdleMindl4qg) reported 59 minutes ago

  @Battlefield The game is broken, buggy, and has lost the identity of what BF is supposed to be, It's so incredibly unbalanced, and we can clearly tell that you can't sort out all the problems.

• 
  Ashish Bajpai (@AshishB60558222) reported 59 minutes ago

  BATTLEFIELD SITREP: THE 23,991 GAP-DOWN SHOCK Active Combat Feed (Friday, June 19, 2026) Commander, the Operator has just executed a violent, trend-shattering move. The tape is pre-opening at 23,991.20. This is a catastrophic ~177-point gap-down from yesterday's 24,168 close. This gap completely obliterates the entire bullish demand staircase we mapped yesterday (24,155, 24,121, 24,103). More importantly, it gapps the market back below the psychological 24,000 floor and slices straight through yesterday's absolute low of 24,036.95. The bullish structure is temporarily broken. Here are your condensed, trigger-ready playbooks for the open: 🔴 PLAYBOOK A: THE BREAKER BLOCK REJECTION (Short the Relief) The Logic: The gap-down is so severe that the entire 24,036 to 24,100 zone (yesterday's floor and demand voids) has instantly flipped into a massive overhead Bearish Breaker Block. The Operator allows a quick morning bounce to trap dip-buyers before resuming the FII distribution. The Trigger: Nifty opens at 23,991, rallies back up to test the 24,036 - 24,050 zone, and instantly prints a sharp Red Shooting Star on the 5-minute chart, violently rejecting the 24K level. The Action: Execute a Short (PE) scalp on the confirmed rejection. The Target: A flush back down through the 23,991 open, targeting the 23,950 macro support. ⚫ PLAYBOOK B: THE CASCADING WATERFALL (Trend Continuation) The Logic: The global panic is too severe. DIIs step aside completely, and the algorithms relentlessly hit the bids off the opening bell. The Trigger: Nifty drops immediately from 23,991. A 15-minute candle closes cleanly and fully below 23,950 with heavy volume displacement. The Action: Do not short the absolute bottom. Wait for a 3-minute micro-pullback (a tiny Bearish FVG) to execute a Short (PE) continuation. The Target: Price discovery into the 23,888 gap-fill vacuum. 🟢 PLAYBOOK C: THE EXTREME TURTLE SOUP (Buy the Reclaim) The Logic: The Operator engineered this massive gap-down purely to liquidate the late retail longs from yesterday's 3 PM squeeze. Once the panic stops are triggered below 24K, DIIs absorb the liquidity and initiate a violent V-shaped recovery. The Trigger: The tape flushes below 23,991 but instantly rejects the downside. It prints a massive Green Hammer on the 5-minute chart and aggressively reclaims and closes back above 24,040. The Action: Execute a strict, counter-trend Long (CE) scalp only on the successful reclaim of 24,040. The Target: A short-covering squeeze back toward 24,100. The Sniper's Rule: The 24,000 line is no longer your floor; it is your ceiling. If they bounce and fail at 24,036, the bears are in total control. Hold your fire until the structure confirms the trend!