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:

• 
  Gerardy Cabrera (@gerardyimdesign) reported 1 minute ago

  @Battlefield Finally. Now fix the home UI menu. Thanks

• 
  TekkenJlN (@germanocassese) reported 2 minutes ago

  the amount of console desync in battlefield 6 is insane, it's very cancerous. I don't understand why they don't want to fix this ****, it has been months. VPN high pingers follow. Allow us to disable crossplay on PC and please set max ping servers to 90. @DRUNKKZ3 @tiggr_

• 
  chris (@ChrisSlaske) reported 2 minutes ago

  @Battlefield season 3 update. Another update that doesnt fix anything except giving us a clear all button

• 
  Xiǎobǎihé (@Suhyeem) reported 5 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.

• 
  Peace🕊️ (@isjustnatural) reported 6 minutes ago

  @BattlefieldComm TTK is still a joke. This won‘t change without reducing the rpm for all weapons!! You guys need to put in the work, this is still no fun at all!!! Netcode feels slightly better, but boy oh boy, this is not what I hoped for! Fix the game guys, this is not enough!!!

• 
  Fauzi (@fuuzzzzy) reported 10 minutes ago

  @Battlefield my man, ranked redsec on singapore server is unplayable, no lobby at all after the update. do fix it.

• 
  Andrew Lyerly ☦️ (@andrew_lyerly) reported 10 minutes ago

  @wokehammer Pariahs were absolute beasts on the battlefield though. Totally broken and could one-shot a Leman Russ if you rolled right. Could break a Custodes in half (if there were any) and do AOE damage to Psykers. The only thing that saved you was they couldn't regenerate and were slow.

• 
  Battlefield 6 News (@BF6Updates) reported 10 minutes ago

  Battlefield 6 players are dealing with major audio bugs after Update 1.3.3.0. Battlefield Studios says it’s currently looking into issues affecting the game’s sound, including random tank emergency beeping, air vehicle audio playing with no vehicles nearby, muddy/random footstep audio, and bugged grenade explosion sounds. Some players say it’s now harder to tell if enemies are close or far away. Hopefully a fix drops soon.

• 
  LewdHub (@LewdLab760) reported 11 minutes ago

  Myrtle | Arknights "Hehe~ Seems like you really like my special service, Doctor~ Then please take care of adjusting my position later~ I want somewhere more relaxing~" "Your only job is generating DP… how much lazier do you wanna be?I didn’t even put you on the battlefield."

• 
  Sann (@san_x_m) reported 13 minutes ago

  His name was Major Shaitan Singh. He was told to abandon his post. He was outnumbered, out of range of his own guns, and no help was coming. He was ordered to fall back. He refused. He was born on 1 December 1924 in Jodhpur, into a family of soldiers. By 1962 he was a major in the 13 Kumaon, commanding a company of 120 men, most of them Ahir farmers from Haryana who had followed him to the roof of the world. Their post was called Rezang La. A pass in Ladakh at nearly 16,000 feet, guarding the road to Chushul. Behind it lay Leh. If Rezang La fell, Ladakh lay open. There was one cruel problem. A ridge stood between his company and the Indian artillery. It meant that if the Chinese came, his 120 men would fight without a single supporting gun. They knew it. They dug their trenches into the frozen rock anyway. On the freezing dawn of 18 November 1962, the Chinese came. Not in dozens. In waves. Hundreds at a time, wave after wave, up the ravines below the pass. Shaitan Singh's men cut them down and kept cutting them down. When one post was overrun, he moved to the next, and the next, walking through machine gun fire to hold his men together. He was hit. He kept going. He was hit again. By the time the guns fell silent, almost all of his company was gone. 114 of the 120 were dead. But they had made the enemy pay in blood for every foot of that ridge. The snow closed over the battlefield. For three months no one could reach it. When the thaw came and the recovery teams finally climbed to Rezang La, they found the men of Charlie Company still in their trenches. Frozen. Weapons still in their hands. The mortar man with a bomb still in his grip. They had died exactly where they had been told to stand. Shaitan Singh was found on that ridge, beside his men. He was given the Param Vir Chakra, the highest honour India has. He was told to fall back. He chose the mountain.

• 
  Margo (@MargoinWNC) reported 15 minutes ago

  Well, William Wallace wasn’t actually Braveheart in real life. That was actually Robert the Bruce. From a historical accuracy perspective, Robert the Bruce did not betray William Wallace as the movie portrays. My dad (who lived in Scotland and loved its history) watched Braveheart and was so mad at the historical errors, he had to tell me all of them-down to the fact the battlefield used in the movie was wrong. The battle was fought at a narrow bridge which was key to their strategy to force the English over and ambush them. So now, you have to know too.

• 
  Alexa 🇮🇱 🇺🇸 (@crowntitanium) reported 16 minutes ago

  @JamieShea260715 @sonnyc_usa @netanyahu It was a serious mistake. Israeli forces misidentified the clearly marked aid vehicles as carrying Hamas fighters in the middle of a war. This led to a tragic error.Israel admitted it quickly. Investigated it. Fired two officers and punished others. Expressed deep regret. Releasing all raw drone audio and secret military details publicly during an active war would help the enemy (Hamas), so Israel shares what it can with allies privately.This was not done on purpose to kill aid workers. It was a failure in a confusing battlefield where Hamas hides among civilians and uses aid areas for military purposes.Israel regrets the deaths and says it has improved procedures to prevent this from happening again.

• 
  Ryan (@Hoskins1st) reported 26 minutes ago

  @Battlefield No if you you would allow kids that have the paid for the battle pass to use your store to at least get the free items that they are supposed to get with the Battle pass that they paid for @Battlefield @BattlefieldComm fix the store

• 
  Akwa (@LordAkwa) reported 27 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

• 
  MusicoBf (@MusicoBF) reported 28 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"