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:

• 
  Hidden History (@HiddenHistoryYT) reported 27 seconds ago

  On June 8, 1943, one of the most powerful warships ever built was destroyed in 15 minutes. No American planes. No submarines. No enemy in sight. IJN Mutsu was one of the "Big Seven" treaty battleships, the most powerful class of warship allowed to exist under the Washington Naval Treaty. 41,000 tons of steel, 16-inch guns, a floating fortress that had sailed through Midway and Guadalcanal without a scratch. She was anchored at Hashirajima, Japan's most secure fleet anchorage. A place so safe it was considered a parking lot, not a battlefield. 113 young naval flight cadets were aboard that afternoon for a routine familiarization tour. They were teenagers, essentially on a field trip. At 12:13 PM, the magazine beneath turret No. 3 detonated. The blast was so violent it cut the ship clean in two. The forward section, nearly 500 feet of warship, capsized to starboard and vanished beneath the water almost instantly. The stern section rose out of the sea at a grotesque angle and floated there, upright and burning, for hours, before finally sinking at 2 AM the next morning, as if refusing to accept what had happened. Of the 1,474 men and boys aboard, 353 survived. Of the 113 cadets, only 13 made it out alive. The Japanese Navy's investigation concluded it was sabotage. A single gunner's mate from turret No. 3, facing a court martial for petty theft, had apparently decided to start a small fire inside the magazine as a diversion so he could escape the ship before his trial. He had disabled the temperature sensors beforehand. He miscalculated. The fire hit the propellant charges. The charges hit the magazine. The magazine killed 1,121 people. His body was reportedly found in the wreckage. Japan's response was not grief. It was silence. The entire event was classified as a state secret. The bodies of the dead were quietly collected and cremated in mass burnings with no ceremony and no public acknowledgment. The ship's captain, Teruhiko Miyoshi, was found dead on June 17. His wife was not informed of his death until January 1944, seven months later. Families of the dead received no explanation. No official word. Some were simply told their sons and husbands had "died in service." The loss of a Nagato-class battleship, one of only two ever built, was erased from official memory while the war continued around it. To this day, not everyone buys the sabotage story. Some historians believe the investigation was designed to blame a dead man and protect the navy's reputation, covering up catastrophic negligence in ammunition storage procedures instead. The wreck was discovered after the war. Partially salvaged in the 1970s. The guns are on display in Japan. One man's court martial for stealing. 1,121 dead. A battleship erased from history.

• 
  sol (@monoviolins) reported 29 seconds ago

  @AtreusQuincy @nyannorin im not op but the titles r virche evermore: error salvation, battlefield waltz (i think), jackjeanne, and taisho x alice !!

• 
  Cowan Wilkinson (@WilkoBooReviews) reported 55 seconds ago

  @Battlefield Anyone else having a problem actually loading into game, always put me back to the main menu

• 
  Kale (@HartAttackKidd) reported 5 minutes ago

  @BloodyTIGER999 @BattlefieldComm I'm having the same problem

• 
  Marty Robbins 🏴‍☠️🇺🇸 (@Mike_McD5511) reported 6 minutes ago

  Shotguns are absolutely useful in war. What Ivan is saying is their impact in WW1 is VASTLY overstated. They're not even in the same ballpark of casualty causing weapon systems. Artillery and belt fed machine guns caused the vast majority of battlefield casualties. Chemical weapons caused hundreds of thousands of casualties and likely killed at least 100,000 men in battle over the course of the war. Shotguns were only useful in enemy trenches and were usually used in small scale trench raids. By the time the US joined the war mass wave attacks like you picture were not the main engagement style. Smaller probing raids and mass attacks shielded by walking barrages were the tactic of the day. Mass casualties were still common, but it was not to the scale of the absolute horror of early engagements like the Frontiers and 1st Marne. The reason for such mass killings in 1914 had more to do with lack of instant communication, mass wave attacks on open ground with no cover, little to zero use of steel helmets, and the ability of a couple machine guns to cut down entire infantry Battalions hundreds of yards away. The rate of casualties accrued in the early stages before the "Race the the Sea" was a nightmare. The 1897 itself was usually issued with paper shotgun shells. In the mud and rain of western Europe this was a hindrance as they would swell and could cause feeding issues. I am certainly no expert on WW1, but this is all basic knowledge you can learn from good documentaries. A YouTube channel called "The Great War" has decently researched info on tactics, weapons, and firsthand accounts of the war.

• 
  Mohammed ♪ (@MGam3z) reported 6 minutes ago

  @BattlefieldComm Are you aware of the Middle East server problems? Players are still facing high ping and being connected to servers outside the region. Any updates?

• 
  3rd Reich Revisited Back-up Account (@3rdReichRevisi2) reported 7 minutes ago

  @thepalehundreds I agree. I was just addressing what many critics have said due to the amount of manpower and resources it consumed. Personally, I understand that such efforts have to be made to advance military science as well as solve certain battlefield problems.

• 
  pierre plex (@pierre_plex) reported 10 minutes ago

  @fawk_yuuu @BattlefieldComm There is no skill based damage, sounds more like a skill issue and bad hitreg/ desync

• 
  Jake Steckler (@JakeASteckler) reported 12 minutes ago

  It's hard to express just how vulnerable helicopters are on the modern battlefield. They fly low and slow and only have crude countermeasures. This problem is only going to get worse as small drones continue to proliferate. I say this as a former AH64 pilot.

• 
  Harrison McCall (@LeadHead0) reported 12 minutes ago

  The debate that matters most right now. Direct syscalls: You bypass ntdll.dll entirely. Call the kernel directly. Advantage: Evades userland hooks (most EDR hooks live in ntdll). Problem: Your syscall stubs now live IN YOUR IMPLANT. Straight anomaly. Modern EDRs detect the call originating from non-ntdll memory. Call stack is broken. You're flagged. Indirect syscalls: You redirect execution through the legitimate ntdll stub, but swap the syscall number. The call originates from ntdll. Stack looks clean. EDR sees expected caller. Indirect is generally superior for stealth. With Direct you need to handle call stack spoofing. Stack telemetry is the battlefield now.

• 
  LetMeOffThisRide (@in_TSMWEL_era) reported 15 minutes ago

  @forknoses @BattlefieldComm High ping players are just people that are playing when it's not peak hours. If I'm playing at 7am on a weekday, I'm not always gonna get a good ping server. Cheating issue is just lol

• 
  orbitant (@orbitant) reported 15 minutes ago

  Pokémon Go and the Hidden Military Value of Play A strange story out of the Netherlands should make every consumer-tech user pause. Dutch newspaper Trouw reports that scans created by Pokémon Go players may have helped train visual positioning technology later useful for military drones and robotic systems. The claim is not that Pokémon Go players directly piloted or trained battlefield drones. The more precise version is this: Millions of players scanned real-world environments through a mobile game. Those scans became part of a massive spatial dataset. That dataset helped train AI systems capable of understanding location and navigation without relying only on GPS. That matters because GPS can be jammed. In modern war zones, especially Ukraine, GPS denial is a serious problem. Drones, robots, and vehicles need alternative ways to navigate when satellite signals are blocked or spoofed. One solution is visual positioning: comparing what a camera sees against a pre-trained 3D map of the world. According to reporting, Niantic Spatial obtained nearly 30 billion environmental scans from users. These scans were used to train an early version of a navigation model. Niantic Spatial later worked with Vantor, a US company involved in visual positioning systems for drones, vehicles, robotic platforms, and other equipment. Vantor reportedly denied direct use of Pokémon Go data for military purposes. Niantic said user scans were used to train an early version of the model. That distinction matters. But it does not remove the bigger issue. Consumer data can become dual-use infrastructure. A game mechanic that feels harmless — scan this landmark, receive an in-game reward — can create a machine-readable map of the physical world. That map may later be useful for delivery robots, AR glasses, autonomous vehicles, security systems, and, potentially, military navigation. This is the real story. Not “gamers knowingly trained drones.” But rather: A consumer app collected real-world spatial data at enormous scale, and that data may have contributed to systems with military applications. Most users probably had no meaningful understanding of that downstream possibility. They were not thinking about GPS-denied drone navigation. They were playing a game. That is the ethical gap. Terms of service may technically permit data transfer. But legal permission is not the same as informed consent. Very few people understand how valuable spatial scans are, or how easily civilian datasets can cross into defense, surveillance, and autonomy. The lesson is simple: In the AI era, data exhaust is not passive. Photos, scans, movement patterns, location trails, voice clips, driving behavior, and gameplay interactions can all become training data. Once aggregated, they may become infrastructure for industries users never intended to support. In the World, people may not be interested in war. But war is interested in maps, sensors, phones, cameras, games, and every dataset that helps machines understand the world. Pokémon Go may be just one example. The bigger question is how many other consumer apps are quietly building dual-use datasets under the language of convenience, entertainment, or product improvement.

• 
  MEDIK86 (@MEDIK861) reported 16 minutes ago

  @Battlefield How bout you fix your game before you push more paid content why do I see glare when I get revived it's like your trying to piss us off

• 
  Franklin’s Tower (@errlgreen) reported 19 minutes ago

  @Bushra1Shaikh Lebanon wouldn’t be getting attacked if its government could actually control Hezbollah instead of harboring an Iranian proxy army that operates as a state within a state. The Lebanese leadership has repeatedly condemned Hezbollah’s attacks and tried to disarm them the real problem is Iran using Lebanon as a battlefield.

• 
  Stefano (@StefanoRota3) reported 21 minutes ago

  @Battlefield Boutique bug... 1 month with this fucina bug... i can't understand you no fix this ****...