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	5 hours ago
Châteaubriant	Online Play	5 hours ago
Cesson	Sign in	5 hours ago
Rillieux-la-Pape	Online Play	5 hours ago
Brest	Sign in	5 hours ago
Paris	Game Crash	5 hours 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:

• 
  The Scholared Medjai (@MUIHorus) reported 7 minutes ago

  @Battlefield FIX YOUR ******* MATCHMAKING! it does need SBMM but the balancing is ******* abysmal. Why and I facing a team of PC players and my team is full of console players with no thumbs. It’s been the same way since BF1. Do better.

• 
  Nikita Kabardin (@nkabardin) reported 9 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.

• 
  Marwan (@6db560c87fec4ea) reported 12 minutes ago

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

• 
  Marwan (@6db560c87fec4ea) reported 16 minutes ago

  @Hyago_Cruz_BR @BattlefieldComm And testing is non-existent. Maybe testing for them is automated like a check list of AI testing a selected new feature or fix.

• 
  Batu 🇺🇦 (@BatuPhD) reported 16 minutes ago

  @BattlefieldComm @Battlefield Can you fix the spaws. Why always appears looking back or do they appear to you?

• 
  before i slip,, ima slide♟️📜 (@Rocinantemoons) reported 17 minutes ago

  @Battlefield fck off if u not fixing server issue in ME

• 
  chris (@ChrisSlaske) reported 18 minutes ago

  @Battlefield Stop wasting our time with portal. Fix all the glaring issues everywhere else. Ranked and portal need to go. Stop putting FNB on portal maps. Gameplay is even more atrocious than a normal server

• 
  Michael E. Perry (@lcbchefperry) reported 21 minutes ago

  @Primary_Pianist The Book of Mormon describes whole peoples, cities, buildings, wars, kings, prophets, temples, records, armies, weapons, and massive battles. Mormon 1 says the land was covered with buildings and the people were almost as numerous as the sand of the sea. Mormon 6 describes roughly 230,000 Nephites killed at Cumorah. Ether 15 describes nearly two million Jaredite “mighty men” killed, plus wives and children. Imagine someone claimed that an ancient Israelite civilization existed somewhere in North America. Not a tiny campsite. Not one immigrant family. A real civilization. Imagine it had a final battle where the dead were roughly the size of Irving, Texas population 238K. Then imagine another earlier civilization in the same sacred history lost a male fighting population roughly the size of Houston 2.4M, plus women and children. Now imagine this civilization supposedly had cities, temples, written records, named places, religious systems, kings, trade, weapons, metalwork, and centuries of history. Then ask: Would it be plausible for a civilization of that size and complexity to vanish with no confirmed city, no confirmed inscription, no confirmed Hebrew or Egyptian writing, no confirmed Nephite place name, no confirmed Israelite temple, no confirmed Book of Mormon battlefield, no confirmed “reformed Egyptian,” and no material culture that clearly identifies it? That is the issue. A small family can disappear genetically. A civilization of that scale should not disappear historically, archaeologically, linguistically, and materially. So the problem is not merely DNA. DNA is one missing footprint. But the larger issue is that almost every expected footprint is missing. At some point, “the evidence disappeared” stops being an explanation and starts becoming a shield against testing the claim.

• 
  ☭ Rèbél ☭ (@ReBeL_Actual) reported 25 minutes ago

  @TacticalGramps @Battlefield @EndersFPS Yeah this is a step in the right direction but the other problems especially with netcode and hit detection eclipse any positive change

• 
  Robbie Blair (@TheRobbieBlair) reported 25 minutes ago

  @OhmanEU @BattlefieldComm I play RedSec too, when I need a good laugh But I'm on SeriesX with fiber optic internet and hard-lined with a CAT8 ethernet cable I usually have crossplay off, but you cant get a match Putting crossplay on brings many bugs/glitches/issues that don't exist without crossplay

• 
  Ashish Bajpai (@AshishB60558222) reported 25 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!

• 
  Hamburgler (@CurseYouBayle22) reported 29 minutes ago

  @BattlefieldComm Fix the support challenge for pouches ffs

• 
  Gabriel K (@EGabrielK) reported 31 minutes ago

  @GokTurk_01001 @Emrulla48879475 @hermes_z You are talking about technical issues for a plane under development produced by an industry that hasn't produced anything similar and compare it against an airplane from a superpower that based its battlefield dominance in air power and has fought in hign intensity conflicts. 🤡

• 
  NodeAspect (@IdleMindl4qg) reported 35 minutes ago

  @Battlefield Horrible game! Broken and unbalanced

• 
  ✯ R I L E Y ✯ (@RileyTX) reported 35 minutes ago

  @DylanBurns1776 @RisingActionRA @whoseurlefty We can’t even call Gaza/West Bank a battlefield because they have no standing army or functioning government in place. They are in an open-air concentration camp. Your pet issue has broad majority support in Congress. This is not in need of the same level of advocacy at all.

• 
  Robbie K (@OSINToffenders) reported 36 minutes ago

  @BattlefieldComm I had an issue near crash site where the entire screen looked like I was going through a dust storm.

• 
  光希 (@fromavalon45656) reported 37 minutes ago

  @DDiboma Giving birth was compared to GOING TO WAR in ancient civilizations for a reason. You guys don't die enough on the battlefield to demand it from women. Maybe you need to start again. Too many pointless males in the world is the problem right now.

• 
  Mike (@Mike_2471) reported 37 minutes ago

  @BFBulletin Don't worry about it battlefield unistalled the game solved my issues with the game

• 
  __Khz__ (@___Khz___) reported 37 minutes ago

  But the problem is who wanna learn battlefield and who are only thinking kd and my stat if im streaming it or for my own "ego" ...... Thats a part of the problem why the info the developers recive, is a disaster.

• 
  Erick (@Erickschultz11) reported 38 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.

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

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

• 
  Bud (@ImaBudtender) reported 38 minutes ago

  @Battlefield Fix the portal server search. Shows people playing but all servers say 0/64

• 
  Woke Smeed (@mrburgerboy) reported 39 minutes ago

  @Viscountpost Okay then whoever your preferred moderate is should have no problem easily defeating her on the battlefield of ideas or whatever what are you even bitching about at this point

• 
  iBRAR (@ibrar_dev) reported 52 minutes ago

  @Battlefield 6 is broken and unbalanced man. Two douche bags can circle a map and abuse the too-low and too-close mechanics and there is no reliable to take then down. Aerial superiority continues to plague the game. BLOPS 2 had a mobile SAM site almost 20 years ago! Battlefield has jack ****!

• 
  Mo.aly (@snipermomo_1994) reported 52 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.

• 
  chris (@ChrisSlaske) reported 52 minutes ago

  @BattlefieldComm Remove ranked. Give every squad size for red sec. Casual better be whatever squad size we want. You removed working initiation for graphic lighting glitchfest in redsec you cant even patch a fix. Great job giving recon even more bullshit for redsec. Infantry conquest, not oblit

• 
  Blaccode (@IamBlaccode) reported 53 minutes ago

  @NigeriaStories Very mumu initiative, what would be the essence of journalists following the military to gun battlefield??? Would that fix the insecurity on ground??? If you insist I nominate VDM for this mission, he is a great content creator.

• 
  NISHIT DESAI- YOGA IS LIFE (@1974nishu) reported 58 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

• 
  Grim (@GrimBF6) reported 1 hour ago

  @FlacoG_2023 @Millitings @BattlefieldComm All he said was there’s nothing mentioned about netcode, when there is. Netcode is frustrating, and they’ve been working on it for a decade+ of titles. It’ll always be an issue atp.

• 
  Ju. (@lakewoodxlegend) reported 1 hour ago

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