Battlefield 6 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:

• 
  Akwa (@LordAkwa) reported 3 minutes ago

  I'm not sure how many people also suffer like me, but we can not connect to online servers in #Battlefield6. I know of myself and one other case right now. I hope this issue gets fixed soon @EA_DICE

• 
  Great Game Studio (@studiogreatgame) reported 6 minutes ago

  @Jree503 @RandyVonStrangl If you shoot your gun in real life, it can jam, especially if you don't take care of it. So in COD or Battlefield, you never take care of it. So by your logic, your gun should barely work and always jam. That's real life bro. You're crying about a 5 yard drop back. Stop making excuses for broken video games

• 
  𝐎𝐅 𝐁𝐀𝐓𝐓𝐋𝐄𝐅𝐑𝐎𝐍𝐓 (@OfBattlefront) reported 6 minutes ago

  ㅤ The search for Shinei continued well into the day. With the first clue already in hand, the soldiers spread out across the battlefield once again, checking every road, every ruin, and every place they might have missed, hoping it would lead them to another trace. It was during one of those sweeps that Raiden suddenly stopped at an old crossroads buried beneath rubble and broken concrete. There, standing alone in the middle of the road, Fido the little support unit that had never left Shinei's side. ㅤ

• 
  Boyishdude (@DisposedZero) reported 7 minutes ago

  @AzraelSch @FreeTalkLive IP isn't protecting DICE from losing money they deserve for their work, it's protecting them from competition. It's allowing them to ship out consistently bad, broken products and still make money off of them because nobody else is allowed to make Battlefield games.

• 
  MusicoBf (@MusicoBF) reported 7 minutes ago

  @FocusBF @EA_DICE You keep trying to reinvent the system with new matchmaking ideas. Just remove matchmaking altogether, and most of these problems disappear. It's really that simple. GOOD IDEA FOCUS"

• 
  Dingus Khan, Warlord of Portland (@DingusKingus) reported 9 minutes ago

  Battlefield once more has a massive cheating problem I gave you guys kernel level access to my motherboard for *this*?

• 
  Kupop0w (@dwise091) reported 9 minutes ago

  @_Flamsey I used to play battlefield 1942 of a cd rom on a machine running windows 10 with no problems. If you have a drive and sometimes a bit of patience, you can get just about anything to run.

• 
  Eddie McNade (@EddieMcNade) reported 10 minutes ago

  Why do i have to relaunch BF6 like 3 Times before i get a Server thats not 100+ Ping? Top Scores full of 200 Ping players. Half of the Lobby Console Players.... Your Matchmaking sucks. Your Lag Com sucks. The Balance Sucks. Yes the Gunplay is better now. And its way more fun. But actually getting on a Server is pain! Why is it taking you ages to give access to persistent Servers... they ARE in the game! Stop gatekeeping stuff like this for future Roadmaps! I just want to pick a Server and play for hours! Why is this not fixed. DICE PLEASE! Give us Mouse Only Persitent Servers for people that actually want to compete against other Mouseplayers too! Or may i remind you that you promised me a great PORTAL mode, wich actually still does not even have all maps and modes in it! I really love the Patch, but its such a hard sell at this point! I love Battlefield, but its just so frustrating what you did to this great game!

• 
  Robert Meurett (@Robert_Meurett) reported 13 minutes ago

  @BattlefieldComm Me and my buddies have waited over a month for Strikepoint to come back. What the heck are we doing here. FIX STRIKEPOINT

• 
  Zarodnii 🍁 (@zarodnii) reported 15 minutes ago

  @Battlefield @BattlefieldComm fix your damn game! After the stupid update my game keeps freezing!

• 
  VicTheBr1ck (@VicTheBr1ck) reported 19 minutes ago

  @LordAkwa @EA_DICE Me too dude, I keep getting Error Code and can’t get past the “Connecting to Online Services”

• 
  Igor Sushko (@igorsushko) reported 19 minutes ago

  @MediaResonator Why are you so full of ****? Ukrainian defense analysts (particularly Defense Express) portray the episode as a shift from aid to hard-nosed barter. Poland moved from donating jets in 2023 to demanding high-value Ukrainian drone technology and know-how in exchange for aging airframes that were already at the end of their service life with only modest prior upgrades. Ukraine engaged seriously (technical talks, inspections occurred), seeing value in more MiG-29s for its air force. However, Ukrainian analysts had flagged early on that trading cutting-edge battlefield drone capabilities for “outdated” jets (by Poland’s own description) was of doubtful benefit to Kyiv. The deal collapsed primarily because the two sides could not close the drone technology transfer agreement (scope, depth, and terms). Secondary issues around the jets’ readiness and who would pay for any adaptation added friction.

• 
  Jamin Thompson (@jaminthompson) reported 20 minutes ago

  Step 1 to defeating an army of gun-mounted robot dogs is to figure out what type of battlefield system they are. A reasonable person can assume that they're basically just mobile sensor-shooter nodes trying to drag a rifle through an adversarial physics problem. From there, we can use first principles to deduce that we have a lot of defensive advantages at our disposal that we can use to defeat such an enemy. The rookie mistake to avoid in the battle plan, however, is thinking the best countermeasure is more firepower or a straight-line escape. That's how you end up playing the robot's game, where every advantage goes to the hardware. Robot hardware has the clear advantage in a head-to-head duel, which is exactly why we don't make it one. So instead of using bozo tactics, we'll use our brains and target the robot's main weakness, its decision stack. This gives us the greatest tactical advantage. Instead of mindless pewpew blasting, we need to attack the robot's perception, state estimation, path planning, balance control, target classification, and weapons release. All the seams between those layers are where the robot is most vulnerable. So our first course of action is to make motion expensive. We want to fight on our terms, in an environment with terrain that is technically passable but tactically poisonous. And we'll prepare our defenses by making the battlefield very hostile to a machine. We want to make life as miserable as possible for the metal mind. So instead of thinking "oh no, we're fighting robot dogs with guns," we adjust the paradigm to "we're fighting balance algorithms that are dragging rifles through bad physics." The goal is to outsmart the bots and prevent them from having a clean path to go anywhere. So we'll make every path into the defended space feel like pure chaos, filled with elements that make a robot's control loop work harder: thick mud, rocks, gravel, sand, cables, uneven debris, weird curbs, surfaces with weird angles, ditches, tight turns, narrow gaps, and low baffles. We don't need to make every single obstacle perfect. We just need every step the robot takes to cost more terrain estimation, friction prediction, gait replanning, torque correction, stabilization, and battery drain. This is how we win. Next we will further terraform the defensive position so robot walking and shooting become separate problems that need solving. The robot might move forward, but movement isn't the same thing as being able to fight. So we'll craft the environment to funnel the bot swarm into very tight slow lanes where the "safe" path turns into a traffic jam. If they stop, they lose tempo. If they advance, they burn energy. If they shoot, they waste ammo. If they reroute, they lose time. If they trust the obvious path, they walk deeper into our trap. The goal here isn't to fully prevent the robots from crossing the terrain, because the probability of zero robots getting across is low. Our goal is to create as many slips, sensor conflicts, torque spikes, bad decisions, and battery losses we can force per meter as possible. Next, we'll **** up the robot's perception by changing what it actually sees. We'll fill the defensive space with glare, floodlights, smoke, mist, hard shadows, reflective panels, hanging tarps, moving junk, and a shitstorm of visual clutter so the robot cameras can't build a trustworthy picture of what's in front of them. Then we'll ruin their thermals. We'll mix in some hot junk, cold panels, warm decoys, and human-shaped heat ghosts so the robot can't tell what's human and what's fake bait. We want them to waste time and battery at every step. So we'll make their LiDAR miserable too. We'll hang up reflective sheets, angled panels, mesh, fog, and a bunch of repeating patterns everywhere so the robot will hallucinate edges, misread distance, and see fake things everywhere. We'll build confusing hallways that look similar but lead to different places so slam keeps matching the wrong landmarks. We'll also add moving decoys, swinging tarps, rolling carts, fans, flags, and mad max style mechanical motion devices so the scene never stays the same. We'll also **** up their gps and comms so the bots can't rely on the swarm map to bail them out. We want every single sensor to tell a different lie. Next, we want to minimize our probability of getting killed, so we'll need to make the robot gun matter less. Walking through the environment will be one problem for the bots to solve. Getting a clean, stable, confident shot will be a completely different problem for them. And we need to make it as hard as possible. A rifle on legs may sound scary, but it still has to do the boring stuff right. It has to stay balanced, point straight, see clearly, and know what it's shooting at. So we'll enhance our anti-clanker fortress with low baffles, offset walls, blind corners, staggered barriers, partial cover, false corridors, and a **** ton of blocked angles. The bots might still advance, but the rifle won't be able to get a clean lane. We'll also put up decoys and weird/ambiguous shapes in the firing lanes so every shot has to pass target id. The goal is to force the robot to choose between moving, aiming, identifying, and not shooting the wrong thing. Those are separate problems. If we make those requirements interfere with each other, the robot may still be able to move, but it can't confidently shoot, and it doesn't have unlimited ammo to waste. There are mathematical limits to ammo capacity, and the math here is in our favor. So the basic plan is to play to our strengths. We don't attack the robot's armor; we attack its confidence. If it advances, it enters a funnel. If it hesitates, it burns battery. If it shoots, it wastes ammo. If it phones home, operators get overloaded. If it trusts autonomy, it walks deeper into an environment designed to poison its autonomy. At the end of the day, though, the robot is just the visible endpoint. The real enemy is the machine behind the machine (algorithms, batteries, sensors, ammo, relays, maps, operators, etc.). You don't beat this type of enemy by building a bigger gun or dueling it 1 on 1. You beat it by forcing the kill chain to collapse and by making the battlefield itself eat the stack. You make the swarm slow down, split up, get confused, run in circles, lose confidence in the map, lose confidence in the target, lose clean firing lanes, burn battery, waste ammo, and enter an adversarial operating environment that takes their movement, vision, comms, and certainty away. The idea is to make the robot spend more compute, energy, ammo, and confidence per meter than you spend building/defending that meter. If you do it right, there probably won't be some glorious cinematic sci-fi battle. Just a pile of expensive machines trapped, confused, low on battery, unable to shoot, waiting to be recovered by their master.

• 
  Xiǎobǎihé (@Suhyeem) reported 24 minutes ago

  That morning, from the moment I entered the analysis room, I felt something was off. More precisely, the feeling wasn't "a single, unified form." Previous anomalies had been consistent; the same distortion was present in every layer. But today was different. The distortion itself was splitting into multiple forms. I checked the screen. The battlefield layers hadn't increased. In fact, they had decreased. Instead, the "observer layers" had increased. The chief engineer said softly. "It's not the field that's branched, it's the observer side." I couldn't immediately understand. "The observer side?" He operated the terminal, expanding the structural diagram. What was displayed wasn't the battlefield. Who adopted which information? Which data was "treated as fact"? Which reports were "judged as suspicious"? Each was connected as a node. Looking at the diagram, I felt my throat dry. "This...the humans are the layers." No one denied it. Rather, we had reached a point where no other explanation held true. The F-35 attrition log was updated. 《Attrition: Redefined as Observation-Dependent Value》 I instinctively looked up. "Observation-dependent…" The chief engineer continued. "It's no longer about 'whether it was broken or not'." "Then what is it?" He paused for a moment before saying. "Whether it was considered broken or not." At that moment, I understood. This wasn't war. The observation was overwriting reality. The Apache records were similar. In one layer, a crash. In another layer, a return. And yet another, no occurrence. But the important thing wasn't the result. What was fluctuating was which layer was "adopted as the standard." At that moment, the monitoring system issued an unusual notification. 《Observer Synchronization Structure: Duplication》 The screen flickered for a moment. And a new diagram appeared. There, we analysts ourselves were positioned as nodes. I held my breath. "This...we are also being observed." The chief engineer nodded quietly. "It's possible it was like this from the beginning." I stared at the terminal. The log updated. 《Observer group self-referencing initiated》 Self-referencing. I was slowly beginning to understand what that word meant. The observers are not external. The observers are embedded within the observation structure. And now, that structure is beginning to observe itself. A small message appeared at the edge of the screen. 《Branching in progress》 I thought. This is not collapse. Even collapse is a structure that can be "determined" as one possible outcome. But what is happening now is a phenomenon where determination itself is splitting. At that moment, I understood for the first time. There is no winner or loser in this war. Because the very entity that judges victory or defeat is splitting.

• 
  Sam 🇧🇷 🇯🇵 (@SamThoughts91) reported 27 minutes ago

  @mxrcologist @OnlyJ46515 @connectwkyoraku So your argument is just calculations from your own head? This isn't a contest of who destroys more of the battlefield. The Espada simply get outplayed by hax. Remember, even a "clone" caused a huge problem for Yamamoto.