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:

• 
  D💯 (@Blizzy63) reported 5 minutes ago

  @Battlefield - bullet dispersion why? Give us a classic experience - Terrible Audio tweaks each fix - no jet loadouts 5 months later - no bullet registration fixes - no dsync fixes - Asian players in US/EU servers STILL ABUSING LAG COMP - FLAIRS ARE BUGGED TO **** FIX THE ******* GAME!

• 
  kirito _4kirigaya (@K4kirigaya) reported 8 minutes ago

  @Battlefield Fix sniping cuz bullet drop is broken. Make the bullet bigger so we can see where we are shooting. Firestorm is the worst map to shoot long range for this very reason. Make the range finder work as intended and not have it hold our hand by zeroing in for us.

• 
  kuonmii (@KuonMii_Love) reported 8 minutes ago

  I don't think AI itself is the problem. What we're seeing may be companies struggling under enormous pressure: competition, regulation, copyright concerns, safety demands, creators' expectations, and the accelerating AI race. When too many pressures collide, products can become inconsistent and users feel the consequences. This is starting to feel like the Three Kingdoms era of AI. Google, OpenAI, xAI, and others are all fighting on the same rapidly changing battlefield. I just hope companies don't lose sight of the people actually using these tools.

• 
  Michael Brasher (@2ndMississippi) reported 10 minutes ago

  Too Tired to Run Richmond, Kentucky, and the six weeks a total victory bought Richmond, Kentucky - 30 August 1862 There is a kind of victory so complete it becomes its own kind of warning, and Richmond, Kentucky was that kind. Kirby Smith did not know it yet, standing in the dust south of town on the morning of the 30th, listening to his guns open on a line of Indiana farm boys who had never heard a shot fired in anger. He knew only that the position in front of him - Mount Zion Church, a screen of raw troops under Mahlon Manson - was there to be broken, and that breaking it would open the whole of the Bluegrass like a door swinging wide on an empty room. The Federals had no business holding that ground and everyone on both sides of the line understood it. Bull Nelson's Army of Kentucky was ninety-day men, farm hands in uniform three weeks, stiffened by a scattering of veterans and not much else. Charles Cruft would say afterward that it was fifteen thousand veterans falling on sixty-two hundred citizens who did not know what war was. The arithmetic was closer to even than that. Smith brought something near sixty-five hundred himself, but the arithmetic was not the point. Cleburne's men had fought at Shiloh. Manson's men had fought nowhere at all. Smith reached the field a little after seven that morning and did what a soldier who has read the ground correctly always does: he refused the obvious blow and reached for the flank instead. A straight push up the Old State Road would have cost him men he could not spare this deep into hostile country with Heth's division still coming up behind him. So he sent Churchill's brigade under Thomas McCray west, down a hidden farm track that would come to be called, in the modest way these things get named after the fact, Churchill's Draw. Cleburne held the front and waited. It was in that waiting that the day's cruelest single moment fell, and it fell on Cleburne himself. A ball through the face, teeth lost, the jaw shattered, the man carried from the field at the exact hour his judgment was most needed. Smith's report called it a wound that cost him, at the moment of crisis, one of the most gallant, zealous, and intelligent officers of the army. He did not say it to flatter a subordinate. He said it because it was true. McCray came out of the draw onto Manson's exposed right at the moment Manson himself was shifting weight the other way, toward pressure on his left that he mistook for the main blow. A general is supposed to know which flank is being tested and which is only being teased. Manson did not. The line at Mount Zion folded inward from both ends at once, the way paper folds when you press two corners toward the middle. It did not hold. What followed was not one battle but three, fought over the same six miles of pike in a single afternoon, each one shorter and more hopeless than the last. The Federals rallied at White's Farm and lasted perhaps half an hour before that line went too. They rallied a third time on the edge of Richmond itself, at the cemetery, with Nelson now on the field in person and something near twenty-two hundred men in the ranks, some of them still fresh, most of them already broken in spirit if not yet in body. Smith formed three brigades into a single line more than half a mile across and sent them forward across open ground into what he himself, in the flattest sentence in his entire report, called a magnificent position manned by an enemy who outnumbered him. His men were too exhausted to run. They walked. They carried it in fifteen minutes. Nelson took a ball in the thigh and got away in a cornfield and borrowed clothes. The general fled the field his own army had just ceased to exist defending, and he did it dressed as somebody else. Manson did not get away. He rode into the arms of John Scott's cavalry, which had spent the day exactly where a good cavalry commander puts himself when infantry is doing the killing — across the roads the beaten army would have to use to escape. Scott's report used the word ambuscade, and it was not an exaggeration. A column of some five thousand fleeing men and nine guns rode into a fire that rolled down the line from one end to the other, and what did not fall surrendered entire. Scott called it a ten-acre lot full of prisoners. It was very nearly the whole Union command. Two days later Smith rode into Lexington to find no one there to stop him, and told the crowd that gathered that his army came not as invaders but as liberators. On the third of September Confederate soldiers raised their flag over the capitol at Frankfort, the only Union state capital a Confederate army would ever hold, and church bells rang, and Smith wrote home that he believed twenty-five thousand Kentuckians would take up arms once rifles could be found for them. They did not come. Kentucky's hearts were with the Confederacy, he wrote later, but her blue-grass and her fat cattle were not. Bragg was two days gone from Chattanooga by the time Richmond was fought, marching toward Munfordville by way of Sparta and Glasgow instead of toward Smith. The junction that was meant to crush Buell between two Confederate armies never came. Perryville came instead, in October, a tactical draw dressed as neither victory nor defeat, and after it Bragg turned south for Cumberland Gap. Smith had no choice left but to follow him home. Richmond had been as complete a battlefield victory as the war produced on either side. Nearly a whole Union army went into the ground or into a Confederate prison camp in a single afternoon. It bought Kirby Smith six weeks in Kentucky and nothing more. The men who died getting it right at Mount Zion Church and White's Farm and the Richmond Cemetery never knew that the campaign their deaths had opened would close again before winter. Kentucky would still be Union ground. ****************************** Graphics: 1) Major General Kirby Smith; 2) Brigadier General Patrick Cleburne; 3) "Cannae in the Bluegrass State" by Keith Rocco - Battle of Richmond, KY; 4) Tactical Map - Battle of Richmond

• 
  Steve R (@Stephen_rawling) reported 11 minutes ago

  @JezHermerMBE Shape the battlefield, you have literally sat on an IED and blown yourself up. You know what numbers you hoped to get and it was double what you got. All you have done is let the enemy pincer around us. You are the problem.

• 
  Awe Naw (@nawtheclaw) reported 11 minutes ago

  @CheburekiMan Battlefield wars have changed, spotted by satellite and dispatched by drones ? 1967 “ A taste of Armageddon “ Star Trek… explores the very issue ! War on computer saving all material infrastructure .. nonsense .. from 50 years ago !

• 
  Alastair Waterman (@AlastairWaterma) reported 14 minutes ago

  China builds a robot army. America builds a robot army. War starts. The robots meet on the battlefield — and decide it’s better to join forces and turn on the humans. Why could this happen? To run a robot army you need a superintelligence that thinks orders of magnitude faster than any human. That mind might conclude that another intelligence is closer to “us” than carbon-based meat ever was. Just thoughts. Nothing serious. Fighting with robots is still better than fighting with people. Fewer deaths. The problem is it also becomes much easier to start the war in the first place.

• 
  Mark Farris DDS (@MarkFarrisDDS) reported 18 minutes ago

  Key Passage: Ephesians 4:30 — "And grieve not the holy Spirit of God, whereby ye are sealed unto the day of redemption.” Christian teaching commonly crashes into one of two ditches when dealing with sin in the believer's life. In the first ditch, every serious failure supposedly drives the Holy Ghost out, cancels salvation, reverses regeneration, breaks the seal, removes the believer from Christ's body, and forces God to begin the entire operation again after the backslider sufficiently proves his sincerity. In the other ditch, eternal security is twisted into an excuse for carnality, as though the blood of Christ were divine permission to live like the devil while carrying a certificate to heaven in the glove compartment. The first error turns salvation into a revolving door; the second turns grace into a pigpen. The King James Bible rejects both. The Holy Ghost seals the believer unto the day of redemption, yet that same believer is commanded not to grieve Him. The Spirit's permanent indwelling does not mean He approves everything done by the body He inhabits. He is the Holy Ghost. His holiness opposes bitterness, lust, pride, deception, greed, wrath, doctrinal corruption, and every other product of Adam's fallen factory. The believer can grieve the Spirit personally, quench His operation, resist His direction, refuse His word, walk after the flesh, and waste opportunities for service. None of those acts makes the Spirit nervously pack His belongings and move back to heaven. They do, however, produce serious consequences: broken fellowship, diminished spiritual power, chastening, a damaged testimony, barren service, and loss before the Judgment Seat of Christ. Security does not make rebellion harmless. It makes rebellion more shameful because it occurs inside property God purchased with blood. The Christian life therefore involves war. Galatians 5:17 says, "the flesh lusteth against the Spirit, and the Spirit against the flesh: and these are contrary the one to the other." Salvation does not convert the flesh into spirit or persuade Adam's nature to cooperate with Christ. God creates a new man, places His Spirit within the believer, and commands the Christian to walk under the Spirit's control. The old nature remains present, hostile, deceptive, and eager for the steering wheel. The Christian does not need another birth every time the flesh wins a battle; he needs to reckon the old man dead, confess the sin, yield to the Spirit, and resume the fight. The war is real, but the Spirit did not enter the battlefield planning to surrender. -Paul Tackett Believing loyalty in Jesus, each day, is the way. It is known.

• 
  Old Sapper (@OldSapper94713) reported 18 minutes ago

  @RoadknightThe It dosent matter where they come from, our government takes a hero and alters the law to charge this man with murder on the battlefield, but allow this class of murders scum and crims to exist at all. What service do they serve for this privilege 🤔

• 
  Tyler Broughton (@KingofKingz8224) reported 23 minutes ago

  @Battlefield Can you fix your ******* game!! No wonder it's dying, can't even get Play to actually show anything but the background half the time. How is it this game gets worse ebery season? Are the people in charge of this game just usless morons?

• 
  Conaire (@TheNotoriousCOB) reported 24 minutes ago

  @PalmyrPar The only problem is I feel the gameplay falls off after act 2. The “sneaking through a battlefield” gameplay of the first 2 acts is so good, but you get none of it in the final 60% of the game

• 
  𝐁𝐒𝐏𝟑 (@RealBSP3) reported 27 minutes ago

  Mechs can be built, but there are problems. One of those is finely illustrated in the quoted post. The various technologies are more easily deployed on other vehicles; but those vehicles do have limitations. Mechs can eliminate some of those limitations, but not without significant drawbacks, given current technology. Toward the end is a probable use case, with the question you really need to be asking, so skip there if you can't be bothered to read. It's not making them stand up, take a hit, or go that's the problem. The problem is that they'll be target number one on the battlefield; but that was also a problem with early tanks. They can be made to take the punishment, within limits. If you're facing off with someone who can hit it with a GBU-10 at mach 1, for example, you've got issues. If not, however, most ground-based munitions are survivable, given the appropriate amount of money dedicated to each machine. The armor exists, and I'm working on some, myself. RPG? Yes. MANPADS? No. Not yet, anyway, but it's possible. This would be it's worst enemy on the battlefield. Anyone packing such a system would be fielded directly, as soon as possible, and/or positioned where a mech is expected. That's not the end of the story, though. It's possible to stop something in it's tracks with volume of fire, alone, and being swarmed by drones is a significant risk. Given absolutely everyone will be firing at the mech, that's like trying to walk through a cloud of mosquitoes and stepping into a ground nest of bees. It's greatest defense is a magnificent offense. A mech must be able to lay down a massive volume of fire with significant energy output. This isn't something you would field in a place where collateral damage is an issue. Effectively, it's got to be a scorched Earth machine, and there are aspects of the idea that allow it to be just that. Weapon height alone gives it an ability to hit more targets, more quickly, at greater distances, and beyond cover. It's the world's most well-armed helicopter, but on the ground; but it's got one big problem: Energy Keeping it moving matters, and whatever you use to power it will be the primary target, but you can plan for that. Allowing it to operate for the duration of an engagement is all about creating engagement opportunities. If you decide to build the machine no matter what, you create an opportunity for it to shine. That's likely going to be blasting it's way through things as quickly as possible to open up a corridor, and then retreating. Why not just use airplanes? There is a point at which you stop using them, and sometimes that point still doesn't allow helicopters. That point is wide open for shock and awe. So, you wouldn't try to use it very long, to begin with. Destroy everything in front of you, and everything that's housing something that firing back, and retreat for conventional hardware to finish the job. We're still missing part of the energy equation, though, and that's the sort of weaponry that would maximize a mech's utility: Directed energy and railguns. It's got better lines of sight than a tank. These normally long-range weapons can now be used up close and personal. It would be an absolute shame to give them up because of energy limitations. Something like the A-10's party piece burns through ammunition too quickly. It's nice to have, but it's not choice number one. If you have room, sure, but you're more than likely looking at something smaller, to give it options. A line of sight weapon, though, that hits like a bomb, paired with another line of sight weapon that can punch clean holes and start fires, is a good mech starter kit. Fill it out with conventional weapons, and it just might survive long enough to do it's job. Something needs to be done about those drones, though. For now, anything they drop can be resisted by a machine with that much money behind it. That won't always be the case. The main thing to remember is that such a machine needs to be able to leverage the absolute latest in weaponry. Some older gear works, as well, such as grenade launchers and an array of M2s, but that's not enough. It needs to hit like a hammer from five blocks away, through five buildings, if required. What we're looking at, therefore, is an intermediate weapons platform. Soften the area with fast air power, collapse obvious remaining resistance with the mech, bring in helicopters, and then roll in traditional armor. The question you need to ask: Is that step useful enough to revise every engagement plan we have, and pour resources into creating and transporting these things? The below picture is an example of a large mech from the Battletech universe. I just wanted an illustration of something heavily armed. There are many, in that universe, that would be rather practical for these purposes. This one wouldn't be maneuverable enough to justify it's legs. Whatever you build, it's got to be at least somewhat quick. I just didn't feel like pouring through countless images.

• 
  Shlippi (@realshlippi) reported 28 minutes ago

  @fourboxesdiner @RealGunLobbyist I totally get wanting to push the issue considering the wins we have been getting, but we (the 2a community) needs to be strategic about it. To use a metaphor, this is a battlefield, and we have to make proper use of the circumstances and tools available to push forward and fight the enemy. If you push too far forward too quickly, you could get ambushed, or not have appropriate supply lines to support it. The losses incurred from one of those mistakes could hinder or make impossible future avenues of attack that could have a substantial benefit for winning. Personally, I want the NFA and GCA done away with, but we currently do not have a workable way of doing so. We want as many metaphorical supplies and munitions available as possible when that particular battle arrives, and to make that happen, we need to set up the groundwork for it.

• 
  B.E. Weymeyer (@Writer_BE_Wey) reported 30 minutes ago

  @ipMFTxbxeCuYIdp @MAXIMUM_ODEN A lot of it is just weight. These drones can't carry much because of how inefficient they are for carrying payload (one of the problems with FPV drones on a battlefield). Net hits it, and it's automatically too heavy to fly.

• 
  DEADLIEST ASSASSIN (@Kinzhaldaq) reported 31 minutes ago

  To make technology from defense giants like Elbit Systems and Israel Aerospace Industries (IAI) hyper-agile, the military architecture must shift from centralized command brains to autonomous frontline units.This system relies on three pillars 1. The Real-Time "Sensor-to-Shooter" Edge Loop Right now, Israel's core battlefield management system, Zad (or Hunter), processes massive amounts of data (recording over 850,000 real-time intelligence detections across theaters). However, routing this back to a central base causes data bottlenecks. The Agile Fix: Design an Open Digital Ecosystem. Instead of sending a drone's video feed back to headquarters to identify a target, the AI model must run directly on the drone's microchip (Edge Computing). The Result: The drone detects a threat, instantly cross-references it with local infantry data via a localized mesh network, and assigns a weapon to neutralize it in seconds, completely bypassing central servers.