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:

• 
  Jamin Thompson (@jaminthompson) reported 57 seconds 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.

• 
  Caleb (@Caleb9697088880) reported 7 minutes ago

  @BattlefieldComm Fix game freezing in redsec ranked on Xbox idiots

• 
  REVENGE (@revsprotwit) reported 8 minutes ago

  @ThelVanDamne Removing health packs, dual wielding, vehicle boarding, equipment did alter halo. Also, the BR doesn't have hit scan. It's just really fast projectile. In fact, the projectiles of the BR are actually slower in halo 3. Further proving you don't know jack **** about what you're trying to seem like an expert on. All of the things you listed were carefully considered and tested before being greenlit to be added to the game. most of the things you mentioned don't really alter the player that much other than improve gameplay flow, which halo 5 abilities do not as we'll get to in a bit. Vehicle boarding is a natural evolution of the combined arms combat halo is known for. it gives people not on vehicles another tool to defend themselves against vehicles, especially when paired with the emp of the plasma pistol, or EMP ball. Removing Health packs (while I don't agree with it) was necessary for multiplayer. Regenning health ensured that once you finished a fight and had time to recover, you entered new engagements on equal footing with other players. Allowing you to be more aggressive. Removing fall damage allowed for greater organic verticality, and improves gameplay flow. Fall damage was a hinderance to map design, and player movement that halted the game. Halo is a game that relies on good consistent flow, and 30 seconds of fun philosophy. If fall damage stayed it would objectively hurt gameplay flow and map design. Equipment affects the battlefield directly. It creates area denial, support for team mates, and cover from enemy fire. It emphasizes the team work aspect of halo's multiplayer. at the same time though, the equipment was never one sided. A skilled player could turn equipment you brought into the field against you, and even use it to their benefit. Dual wielding is an extension of the weapon sandbox. It gives weaker single handed weapons additional utility. While I think the implementation and execution was not the best, it provided another layer to combat that gave you pause to consider using single handed weapons over two handed weapons. All of these changes organically evolved halo's combat loop. Which I even said I wasn't against. Spartan abilities on the other hand: >Sprint even though it makes you run faster, is still disruptive to the gameplay loop, because it forces you to put your gun into low ready while sprinting. Then have to bring it back up when exiting sprint, disrupting halo's gameplay flow. Along with the other aforementioned gameplay implications. >Ground pound locks you into an animation that you have zero control over, and on impact you have to wait for an animation to play before you can regain control of your character. Same for spartan charge. Again, disruptive to gameplay flow. The only "spartan ability" I have no problem with is clamber, because that's less of an "ability", and more of a quality of life improvement that still punishes you for bad jumps.

• 
  youngharold (@youngharold) reported 9 minutes ago

  @JonathanGuito @GrindeOptions And I don’t doubt millions of robotaxis will be on the road one day. It’s just not going to beat Optimus. The factory near Giga Texas will be complete at the end of 2027. They already have it going up. Optimus is a no-brainer for so many applications, from corporate, retail, personal, and most importantly, the battlefield. Companies will easily spend $ 50k-$100k on a robot to replace tasks humans currently perform. Even if it only replaces 1% of labor tasks, that’s trillions in revenue. Optimus revenue will make robotaxis become what Model Y made Model S look like—rounding error. The $400 stock price already includes robotaxi revenue; otherwise, the stock would trade around $75-$100 on the car business. You have to compare revenue with that of other companies like Nvidia, Facebook, and Google. Retail is not going to pump the price; only big money can. And right now they like printing money on the ups and downs. I like it. I’ve made way more selling options than on the stock itself. Tesla will be a $3,000 stock in the next decade, but not because of robotaxis.

• 
  LèTrunks (@TrunksInu) reported 14 minutes ago

  Facebook has a new flag most creators don't know exists. "Limited originality of content." It freezes your earnings. No warning. Just $0. Fix: 100% original posts. No reposts. No AI spin. Your words. Your angle. Warriors don't borrow someone else's battlefield. 🔥

• 
  urticaria⚧️ (@urticariuh) reported 20 minutes ago

  bouta drop bf6 and play bo2 because battlefield wants to CRASH EVERY TWO SECONDS I NEVER HAD ANY ISSUES BEFORE LIKE 2 DAYS AGO

• 
  bigby (@EsdHhb) reported 21 minutes ago

  @EndersFPS The problem isn’t the large factor it is the variety that matters i dont care if the maps are large or small they need to be great But battlefield 6 has already more than enough of small to medium maps so yes big maps in this exact context actually matter

• 
  PLA_Overwhelm (@junshiguancha1) reported 22 minutes ago

  @alpha_defense Bro, it’s time to retire this aircraft—it’s an embarrassment to India. The return on continued investment is simply too low; if it can crash at an airshow, what kind of survivability could it possibly have on the battlefield?

• 
  Kupop0w (@dwise091) reported 22 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.

• 
  medoyid_ua (@LetsArmUKR) reported 25 minutes ago

  The footage from occupied Donetsk region says it all: Ukrainian long-range strike drones are turning Starobesheve into a logistics bonfire. That thick black smoke isn't random. It's moscovian supply lines, fuel dumps, and rear-area staging points getting exactly what they deserve. While their meat assaults crawl forward a few ruined villages at a time, losing more orcs per square kilometer than the pre-war population, our forces are systematically burning everything that keeps their front alive. This is the pattern they refuse to admit. Moscovia cannot stop the war because the war is the only thing holding their rotten imperial project together. End the fighting tomorrow and a million traumatized conscripts come home asking why their friends died for another "liberated" ruin with no strategic value. Putin knows that question ends regimes. So he feeds more bodies into the grinder, hoping quantity magically becomes quality. Z-bloggers already admit it in their own circles: fresh mobilization waves change nothing except the body count, and the bill is paid entirely in moscovian lives. Meanwhile Ukraine is scaling. By end of 2026 our mid-range strike capabilities will be 2-5 times what they are now. Operational-level logistics across occupied territories will burn daily. Crimea is being isolated in plain sight. We're not begging for permission to exist. We're building the defense industrial base that will eventually license Patriots, Tomahawks, and our own next-gen air defense while churning out FREYA systems, drone interceptors, and Gripens that will make Ukrainian skies the most defended on the planet. The favor narrative needs to die. Europe isn't "helping" Ukraine out of charity. Ukraine is absorbing the direct cost of a war the continent would otherwise be fighting on its own soil with its own conscripts. Every drone strike on a moscovian depot, every burned fuel train, every neutralized glide-bomb carrier is security bought and paid for in Ukrainian blood so Berlin, Paris, and Warsaw don't have to learn these lessons the hard way. The isolationist crowd in Washington and European capitals pretending this is someone else's problem are not serious people. They're either useful idiots laundering Kremlin narratives or cowards who think appeasement has ever worked. History's verdict on that delusion is written in mass graves from 1939 onward. Moscovia only understands force. Their hybrid war against NATO is already active. Time to stop pretending otherwise and start closing skies over western Ukraine, accelerating aircraft deliveries, and treating Ukrainian interceptor drone production as the continental shield it has proven to be. We don't need lectures about negotiations. Zelensky keeps saying direct talks with Putin are necessary precisely because everyone knows Putin will refuse them. It proves who is serious about ending the war and who requires total military defeat before any real conversation can begin. There is no diplomatic off-ramp that survives moscovian imperial DNA. Only battlefield reality. The smoke over Starobesheve is not just tactical success. It's strategic inevitability. Moscovia is running out of cards. Their soldiers remain cheap, but even cheap resources are finite when you're losing them faster than you can replace them. Keep feeding the meat grinder. Ukraine will keep adjusting the burn rate until the only thing left is ash and the realization that empires die when their neighbors finally refuse to be swallowed. The question isn't whether we can win. The question is how quickly the West will provide the resources so we finish the job before more European capitals have to learn these lessons firsthand.

• 
  Robert Meurett (@Robert_Meurett) reported 26 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

• 
  Joey Zhuo (@JoeyZhuo777) reported 26 minutes ago

  $NVDA Jensen says it's worth a trillion, the filings say ROE is 0.46% Wait — that's not right. Nvidia's up 24% this year while its semiconductor peers are up 110% and some AI bottleneck stocks have quadrupled. When everyone's chasing the picks-and-shovels story, the actual arms dealer is getting left behind. That disconnect tells you something about where the money went, and where it should have stayed. The market is pricing Nvidia like its moat is crumbling. It's not. It's actually widening, and the data proving it is hiding in plain sight. Start with inference. The narrative says custom chips from Google and Amazon, plus the rise of CPU-heavy agentic AI, will eat Nvidia's lunch. But Nvidia's market share in inference has gone up, not down. The whole "merchant chips are dead" story doesn't match what's happening on the ground. Jensen's full-stack approach — chip plus software plus networking, all co-designed — is delivering lower total cost of ownership than the hyperscalers can match with their in-house programs. The hyperscalers aren't building custom chips to replace Nvidia's ecosystem. They're building them to control costs and reduce dependency. Those are different goals. Google's TPU program is on its ninth generation, and it still hasn't weaned itself off Nvidia. Amazon and Microsoft are in the same boat. Custom silicon makes sense for specific workloads at their scale, but it's not a moat against Nvidia — it's a hedge. The real strategic move is what Jensen is doing with his balance sheet. Nvidia is now investing in and backstopping smaller AI clouds — Firmus, CoreWeave, Nebius. That's not just customer diversification. It's an insurance policy against a future where hyperscalers hold all the cards. If Amazon, Google, and Microsoft are your only customers, they eventually dictate terms. Jensen is deliberately fragmenting the buyer base, seeding competitors to the hyperscalers, making sure no single customer can capture the value Nvidia creates. That's not defensive. That's offensive positioning. He's shaping the structure of the industry while he still has the leverage to do it. Then there's the CUDA question. A recent breakdown showed that re-architecting around CUDA is technically possible — DeepSeek proved it — but the engineering lift is massive even for top-tier teams. Hyperscalers have the resources to attempt it. Smaller developers and neoclouds do not. That bifurcation works in Nvidia's favor. The long tail of the AI ecosystem stays locked in, and that tail is growing as Nvidia funds its expansion. Now layer in the CPU play. Nvidia's Vera CPU is a pre-emptive strike on agentic AI, where reasoning workloads tilt toward CPUs. The worry is that AMD, Intel, or Arm takes the lead there. But Nvidia entering that fight with $213 billion in free cash flow this year — potentially $360 billion by fiscal 2029 — means it can outspend any rival by a factor of three. Cash flow is a weapon, and Nvidia is wielding it to stay in every game that matters. The stock trades at just under 20x forward earnings. The semiconductor sector average is 18.4x. Nvidia is being priced like a mature cyclical with single-digit growth ahead, not a company expected to go from $393 billion in revenue this year to over $600 billion by fiscal 2029. That's not skepticism — it's disbelief that the growth is durable. The disbelief is wrong. Revenue concentration risk is falling, not rising. Margin pressure from custom chips is real but overstated. The inference narrative was supposed to hurt Nvidia, and instead it's gaining share. The CPU threat is being addressed before it materializes. And the balance sheet gives Nvidia the ability to reshape the competitive landscape while competitors are still trying to catch up on the last battlefield. The six-week selloff since mid-May brought the stock back to the 50-week moving average. The last time it tested that level was late March, and it took four months to base before the next leg up. Dip buyers are back. Momentum chasers who rotated into AI bottleneck stocks are going to rotate back when those names start to consolidate. The setup is straightforward: the market mispriced the risk, the technicals are stabilizing, and the fundamental case is stronger than the multiple suggests. Nvidia isn't cheap because it's broken. It's cheap because the market decided the moat was narrowing, and the data says the opposite. Image source: Seeking Alpha / JR Research

• 
  Jorge (@ghosy01) reported 29 minutes ago

  @AndreiBtvt They just keep slapping explosive bricks on the t90 . I don’t think anything can fix that tank it just doesn’t work on a modern battlefield

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

  ㅤ Raiden went farther than anyone else, he searched every place Shinei would normally go. when he found nothing, he started over and He crossed the battlefield once. Then again. And again. Every ruined street, every collapsed trench, every broken road. He retraced them all, refusing to believe he'd overlooked something. ㅤ

• 
  Margo (@MargoinWNC) reported 30 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.