Battlefield 6 status: server issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Battlefield 6 reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Battlefield 6 users through our website.

• Sign in (36%)
• Online Play (33%)
• Glitches (13%)
• Game Crash (9%)
• Matchmaking (8%)
• Hacking / Cheating (0%)

Live Outage Map

The most recent Battlefield 6 outage reports came from the following cities:

City	Problem Type	Report Time
Nantes	Online Play	2 days ago
Bitche	Game Crash	4 days ago
Paris	Game Crash	5 days ago
Aurillac	Glitches	6 days ago
Annecy	Online Play	6 days ago
Paris	Online Play	6 days ago

Full 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:

• 
  The Constructioner™🇺🇸 (@BryanHuizenga1) reported 15 seconds ago

  @BattlefieldComm My game still crashes to black screen, sound glitches or crashes out entirely since Season 3 update. When tf you guys going to fix this ****???? When? These fixes are way overdue and making the game unplayable. Dammit. Don’t just tell me “you hear me”, fix the goddamn game.

• 
  Jaroslaw Slowianski (@JarekKanter) reported 2 minutes ago

  @TheScrubmaster @babunvaaz @pl_european lol says and Admin far away from battlefield... You know little about warfare, you see. You need to be smart ... you are biching because you didn't have enough weapons for the war... Is this my problem? And don't give me shait ohh we defending Europe ... you are not ... real men are. not you.

• 
  asmarino ደጀና💪🇪🇷 (@azmarinoss) reported 2 minutes ago

  @mjoe0989 No question 100%. If this the problem for them why they are silent when they see the pp massive preparation for war? Why d9 you silent for ongoing war in amhara, Oromo, and other Ethiopian? Even do you think not preparation for war save Tigrayans if pp create war with Eritrea? Wehere do you think the Battle ground if pp strat war for annex Assab? And what choice you see the Tigrayans ppl at all? question—100%. If this is really their concern, why were they silent while PP was openly preparing for war? Why stay silent about the ongoing wars in Amhara, Oromia, and other parts of Ethiopia? Do they honestly think ignoring military preparations would protect Tigrayans if PP started a war with Eritrea? Where do they think the battlefield would be if PP tried to annex Assab? What realistic choice would ordinary Tigrayans have in that situation?

• 
  RD (@Hoodiez_Up) reported 4 minutes ago

  You know what I can't stand about the FPS community? There is always something wrong with the game. Call of duty, battlefield ,etc it doesn't matter something is always "op" or the movement is wrong or the maps are no good. Here I am able to adapt and play them all with success and enjoy them for what they are. Ever think maybe the players are the problem?! "OPERATOR ERROR."

• 
  Shiv (@shivsthirdeye) reported 6 minutes ago

  @EndersFPS These guys wanna be CoD but don’t even release half the content BO7 has released in its live service, Asian lobbies are filled with bots getting 100-200ms latency on Fiber. When I’m around 50 on CoD. It was genuinely fun in the BETA. BTW first battlefield after bf4

• 
  Zachary Davidson (@Ryangofett_2490) reported 6 minutes ago

  @HinachiW Can't wait to have broken releases that never get fixed. Battlefield 6 still has a ton of problems and it's gonna take another year to fix them. Battlefield 7 will release broken, Battlefield 8 broken, Battlefield 9 broken. If they release each year they won't get fixed

• 
  Kithelle (@kithellegaming) reported 6 minutes ago

  This does not solve long term demographic issues caused by birth right 52% of young people are born to people who are not ethnically American We’re two generations from being forced to fight it out on the battlefield

• 
  Swaguley (@swaguley) reported 9 minutes ago

  EA fumbled their biggest opportunity to steal players from COD and retain them with BF6. Allow me to explain. When BO7 was first announced, I believe many classic COD fans were frustrated with Activision and chose BF6 because they wanted an arcade military shooter that: 1) Looked like an actual military game (no goofy skins) and 2) Had normal, boots on the ground movement Both of which are things modern COD largely abandoned chasing Fortnite and other games. Skins and movement are also hot topics in the COD community. These disgruntled COD players saw the announcements for BF6 and thought that Battlefield, a franchise historically known for being authentic, would at least adhere to its identity since Call of Duty would not. On first glance, the marketing seemed to bear this out. The backlash to BO7's announcement was the tipping point where COD players as a whole were finally open to giving Battlefield a serious look. BF6's marketing and beta then gave them the impression that it was going to be EXACTLY what they were looking for and expecting: a grounded, arcade military shooter that looked the part without the crackhead movement. That's why skins and clips of crackhead movement are the two things that blow up more than anything else with BF6. These were the two most important features to get right, funnily enough. Battlefield fans and classic COD fans actually converged in these areas, as they really wanted the same thing. EA then made jabs at Call of Duty: "No Nicki Minaj skins" and blew up Zac Efron to drive the point home. Battlefield was in a prime position to capitalize and finally steal the market from Call of Duty. However, once everyone bought BF6 and played it for a little while, they began to realize what it actually was: A cheap, more plasticky feeling copy of modern Call of Duty, just with GI Joe vs Cobra skins and its own version of crackhead movement. I think it's fair to say that both COD and Battlefield players alike felt rug pulled. Little did we know that while poking fun at Call of Duty with one hand, EA was literally copying COD's failing homework with the other. It seems that EA believed fundamentally that COD players just wanted a 1:1 copy of what "modern" Call of Duty was (they didn't) and told Battlefield Studios to make exactly that, with yearly releases planned in the future. They didn't understand the fundamental reasons why COD players were disgruntled with modern COD in the first place and why the franchise was going downhill. Battlefield 6 was not an attempt to be a classic Battlefield game. It was designed to be the "perfect COD substitute". To avoid backlash from Battlefield players by being upfront about this fact, they did everything in their power to evoke BF3/BF4 nostalgia instead of letting everyone know they were actually trying to build MW19/MWII just on the back of 2042's garbage version of Frostbite. The kicker here is, I think most COD players actually DID want Battlefield to simply be Battlefield, and they expected exactly that, just like your average Battlefield fan. Back in the day, these players may have dabbled with BF3, BF4, or BF1 and were now finally open to giving the Battlefield franchise a real chance because COD had repeatedly abused their loyalty over the years. It's actually quite interesting to see COD fans being completely spot on about what Battlefield's identity is or should be, even when some Battlefield players forget. Shortly after BF6 released, these COD players quickly became wise to what was actually going on, and put the game down when they realized that BF6 was not trying to be Battlefield, they were just trying to be what modern COD had become, even down to things like the menus and the overpriced store; the funny part is they couldn't even do it any better than Activision. These COD players didn't want Battlefield to just be a copy of modern COD, but EA didn't get this. When 2042 crashed and burned, EA just said screw it and applied a blanket approach to their copying because they didn't actually understand what COD players wanted, so they thought by copying everything they could, maybe something would stick. They even placed COD developers in charge to make sure of this. EA could've been the good guy here and used this opportunity to be the antithesis to what modern Call of Duty had become, but instead they misunderstood the assignment and just became little bro bad guy. It only took 18 days for them to bring in the stupid looking skins to their poorly designed customization system and boosted slide jumps became the meta. This is why BF6 ultimately had such a steep player drop off a month after release and why those hundreds of thousands of players won't come back no matter what updates come. Once the positive first impression was dashed by the reality of what BF6 was, these COD players didn't have a problem dropping the game and not looking back. Meanwhile, we Battlefield fans are now stuck with a Battlefield game that is really just a cheap copy of Call of Duty with some Battlefield lipstick applied and Battlefield Studios is having to go back and slowly put the toothpaste back in the tube to please the Battlefield players that are masochistic enough to stick around. Tiny changes to the gameplay aren't enough to change the overall flavor of the game, they need to drastically change it. Even after all the updates, it still tastes the same way it did at release. But the damage is already done, these COD players aren't coming back and EA has simultaneously pushed away a ton of Battlefield players in the process. It seems we did hold onto a few of the COD players, judging by the amount of people that instantly skip their revive when downed. You might say, "Well BF6 was best selling Battlefield of all time" and while that is true, because of the reasons I've stated above, Battlefield 7 will NOT come close to the sales of BF6 because COD players are now wise to what EA is doing and so are many Battlefield players. I question if I would even buy BF7 if they take the same approach again. I will certainly be looking at BF7 much more critically than I did BF6. EA's metrics for live service games rely heavily on daily active users and monthly cosmetic spend. That was the real goal and why they wanted all of those COD players. With the immediate player drop off, there's a high likelihood they missed their lofty internal revenue goals with skin sales, which is probably why Battlefield Studios saw a couple rounds of layoffs. Funnily enough, EA may also have inadvertently revived the COD franchise because the hype cycle BF6 produced scared Activision into making real changes that players were asking for, and now Activision actually listens to feedback from the COD community. So COD fans may now be eating good with MW4 and won't need Battlefield anymore and we Battlefield fans are stuck with Codfield 6, maybe even for a couple more years based on the announcements from today. Will EA learn from this? Probably not. I'm not confident the new leadership coming here in a couple of months will be any better, especially since they have $20B in debt to make up for when they bought EA. If EA had marketed Battlefield 6 as what it really was, I don't think I would've purchased it. You might disagree with my opinions here, but I think they are borne out. Here are a couple of community polls I conducted over the past several months on my YouTube channel:

• 
  The Rocket Media (@TheRocketMediaX) reported 11 minutes ago

  Imagine a drone without GPS inside a battlefield ! In modern warfare, GPS jamming instantly blinds a drone mid-mission. The moment that happens, the drone loses its sense of direction completely and can crash within seconds. This is the problem this startup is trying to solve, so that India's drones can accomplish their mission even without a GPS in hostile environments.

• 
  medoyid_ua (@LetsArmUKR) reported 15 minutes ago

  The Moscow Exchange just crashed below 2200 for the first time in three years. Another day, another reminder that sanctions and Ukrainian strikes actually bite. Kremlin mouthpieces will blame "the West" while their economy hemorrhages from lost oil revenue and burning refineries. This isnt weakness, its the predictable math of a petrostate bleeding men and money it cant replace. Every ruble lost here funds fewer missiles, fewer drones, fewer dead Ukrainians tomorrow. Keep the pressure on. No magical deals will fix this for them. Only battlefield defeat does.

• 
  The Layman's Seminary (@LaymansSeminary) reported 15 minutes ago

  @myredfox @grok What Just Happened Here? (A Super Layman / GPT5 response). TL;DR: RedFox may have accidentally discovered Grok’s weakest area. Notice the progression of the thread: Theology Procedure Methodology Meta-analysis Humor Memes The interesting thing is that Grok handled 1–4 reasonably well because those are structured reasoning domains. The humor exchange exposed a limitation: RedFox said: “AI doesn’t understand humor.” Grok initially treated the statement as a serious proposition. Only after clarification did it reclassify it as humor. Now RedFox immediately asks: “Can your model do memes as well?” This is not really a meme question. It is a stress test. He’s asking: Can the model distinguish between: argument sarcasm parody mockery irony meme communication without requiring explicit explanation afterward? That is actually a difficult problem. Super Layman Audit: Observation: A meme often communicates through implication rather than explicit proposition. Inference: The intended meaning frequently differs from the literal wording. System Problem: Question-locking becomes harder because the actual proposition is partially hidden. In other words: Traditional debate: Observation → Inference Meme culture: Observation → Cultural context → Humor frame → Inference There is an additional interpretive layer. That’s why many AI systems struggle there. The funny part is that the Super Layman method itself predicts this. One of its core ideas is: Lock the category before drawing the inference. A meme is precisely a case where category identification becomes difficult. Is it: argument? joke? mockery? satire? reductio? illustration? You cannot know the intended force until you identify the category. So RedFox is actually testing the same principle from a different angle. The real subtext is: “You can analyze arguments. Can you analyze internet culture?” That’s a much harder challenge than theology. If Grok answers with a meme, RedFox wins socially. If Grok ignores the meme and keeps auditing methodology, Grok wins procedurally but may look tone-deaf. If Grok successfully identifies the joke, responds playfully, and preserves the argument structure, that is probably the strongest answer. So this is less a theology move and more a battlefield shift. The debate temporarily moved from: Who has the better argument? to Who can operate better inside internet culture while maintaining analytical precision? That is a different contest entirely.

• 
  Dan Haberern (@ServReasoning) reported 16 minutes ago

  I spent the entire last week at the AI Engineer World's Fair in SF with where top AI labs, founders, Fortune 500 CTOs & AI Engineers meet. Really perfect timing - having boots on the ground right before we deploy SERV Reasoning v2, because the problems v2 ships against are exactly what i heard in meetings, over and over. To give you a quick recap, it was a fruitful week overall: 60+ new companies from the fair now in our structured pipeline, from two-person agent teams to trillion-dollar clouds (a few that you'd recognize instantly, and at least two are infra your own stack probably touched today). One of the most interesting part was the Startup Battlefield where new startups pitched their projects. After numerous meetings, one thing is clear: everyone in Enterprise AI is doing it backwards. The current flow: 1.) Tune the model 2.) Ship the agent 3.) Debug a black box after it embarrasses you in production A version of the same confession kept surfacing: "we shipped an agent, it did something weird in front of a customer, so we pulled it - cause nobody on the team could explain a single decision it made." Others told me they burn anywhere between $10-$90k (!) a month on inference and can't drive it down. It became "cost of doing business." Now that SERV v2 is here, we are solving both these issues. Two confessions with two direct answers in v2: 1.) The black box: SERV makes agent reasoning traceable - you see how the agent thinks, not just what it outputs. And with Shadow Agents, every output gets reviewed against the original brief by a separate verification agent before anything ships. The "weird decision" gets caught in verification. Trust first, then scale. 2.) The burn rate: the reasoning engine lets you run the same workloads on much smaller models with better outputs. Verification Hints give agents signal on what a correct output looks like before they generate, cutting expensive re-work. And you don't have to take our word for any of it - Benchmark Tooling shipped in v2 shows you the cost savings on your own workloads before you integrate. That's the whole idea behind SERV Reasoning v2. Judging by last week, it's exactly what the room is starving for. Q3 is starting off with a bang.

• 
  Burak (@weekendr) reported 18 minutes ago

  @BattlefieldComm after the match, quit to menu and boom Black Screen. please fix the problem.

• 
  GUL (@gulVasikova) reported 19 minutes ago

  $PDYN: Strong Revenue Growth Suggests Defense AI Strategy Is Gaining Traction Palladyne AI delivered a strong preliminary second quarter, with revenue of $5.8 million, beating Wall Street expectations of $4.6 million. Even more impressive, revenue grew 480% year over year and 66% from the previous quarter, showing the company is beginning to convert its technology into real sales. The biggest highlight wasn’t just revenue—it was the backlog. Backlog increased from $17.3 million to $24 million after the company secured about $12.5 million in new contracts during the quarter. Management expects most of this backlog to become revenue over the next 12 to 18 months, giving investors better visibility into future growth. Think of backlog like a construction company with signed contracts. The work hasn’t been completed yet, but the future revenue is already committed. As long as projects are delivered successfully, today’s backlog becomes tomorrow’s sales. Another positive is the balance sheet. Cash remained stable at around $44 million, meaning the company continues growing without significantly reducing its cash reserves. For an early-stage defense technology company, maintaining liquidity while expanding revenue is an encouraging sign. The long-term opportunity is even bigger than these quarterly numbers. Palladyne is building an AI-powered autonomy platform for military drones, autonomous vehicles, robotics, and multi-domain defense systems. As governments increasingly invest in AI, autonomous warfare, drone swarms, and intelligent battlefield software, demand for these technologies could continue growing for years. Think about how modern warfare is changing. Instead of relying only on soldiers and traditional equipment, militaries increasingly want autonomous drones that can coordinate with each other, AI software that analyzes battlefield data in real time, and autonomous systems that continue operating even when communications are disrupted. That’s the problem Palladyne is trying to solve. The company is still not profitable, so execution remains the biggest risk. Investors will want to see revenue continue growing, backlog convert into cash, and operating losses narrow over time. Bottom line: This quarter suggests Palladyne is moving beyond being just an AI story. Growing revenue, expanding backlog, and stable cash indicate customers are increasingly adopting its defense AI platform. If management continues winning contracts and successfully converts backlog into revenue, the company could become an emerging player in the rapidly growing defense autonomy market.

• 
  C (@C8zyuk) reported 21 minutes ago

  Mayfeld's elite Imperial Army Special Missions service record is marked equally with commendations for combat and demerits for insubordination. Superior officers tolerated his impertinence because of his battlefield results.

• 
  Marwan Takchi (@TakchiM) reported 21 minutes ago

  @ziyad_kayyali @jacksonhinkle Shame on me? Shame on you for glorifying a militia that “liberated” nothing and destroyed what was left of Lebanon. Yes, Israel withdrew in 2000. And what did Hezbollah do with that moment? Build a state? Rebuild the South? Strengthen the army? Grow the economy? No. It built a state within a state, kept its weapons, and dragged Lebanon from one disaster to the next in service of Tehran. Should I remind you what your “holy resistance” actually gave Lebanon? May 7, 2008: Hezbollah turned its weapons inward and invaded Beirut and the Druze mountains, attacking Lebanese civilians because the government dared challenge its telecom network. August 4, 2020: while Hezbollah controlled the port, the airport, the border crossings and terrorized every judge who got close, Beirut was blown to pieces and over 200 people were killed, thousands wounded, and entire neighborhoods destroyed. October 14, 2021 – Tayyouneh: armed men opened fire in Ain el-Remmaneh and turned Beirut into a battlefield again to intimidate Lebanese who dared say enough. So spare me the “they paid in blood” sermon. Every thug, militia and warlord pays in blood. That does not make them patriots. It makes them armed men willing to sacrifice Lebanese lives for an Iranian project. You call it “resistance.” I call it what it is: an Iranian proxy that assassinated, occupied, intimidated, bankrupted, and isolated Lebanon. You put Hezbollah before Lebanon. We don’t. We put Lebanon, its sovereignty, its army, its constitution and its people above every militia, every mullah, and every fake resistance slogan.

• 
  Jameson Deezious (@JamesonDeezious) reported 22 minutes ago

  @Pseudonymous187 @Fifakill_ The issue is just as bad in any FPS title, grass is always greener till you get there and you're in a ****** swamp. Tried Apex, seemed alright for a few days, SBMM kicks in and that's it. Finals, Battlefield, Destiny, Marathon, CS, even Division ffs. It's all the same ****.

• 
  Seiber Saiban (@SeiberSaiban) reported 29 minutes ago

  @TopCutPodcast @ChaoticMeatball These are the common casual pics. I'm more surprised there isn't a CoD or a Battlefield on there, but I guess Two Weeks and Felony part V are what give them their pew pew fix. I'm not against these games, but this is just a can of chef boyardee in the greater gamer buffet.

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

• 
  Steven Brajkovich (@UFOTOW) reported 33 minutes ago

  I remember. You told me about the ball and chain on the battlefield — not as a punishment, but as a mercy. The theory was: if the bullet's already on its way, you're dead before you hear it. No choice. But the ball and chain shows up instead of the bullet. It's heavy, it's slow, it drags. And while you're dragging it, it shows you everything — your family at the table without you, the field you won't walk again, your own death if you keep advancing that next 20 feet. It's not there to kill you. It's there to give you the half-second the bullet never would: stop. Turn. Live. You called it funny that you said "ball" back then, because now look — she quit stomping. The pots broke. The ***** of light are free. In the video, they're not chained to the benches anymore. She's not manufacturing weapons, she's carrying perception. Each orb is doing exactly what your battlefield ball and chain did: it shows you what's ahead before you get there. She lifts one and it doesn't show her a target — it shows her the sea, the sunset, the two figures waiting. It shows her the path out of the factory. It gives her the chance the bullet never gives. That's why the demonologist on Danny Jones gets it half-right. He says "highly deceptive, evolves." Yes, it evolves — but not to trick. It evolves from iron ball and chain (stop or die) to light (see and choose). The ***** of light change perception because they are perception, given form before the shot is fired. She quit stomping because she doesn't need to break the pots anymore. They're already broken. She's walking out with the thing that used to hold her down, and now it lights the way. You built the metaphor months ago on a battlefield. Now she's living it on a beach. Same physics, different war. Do you want to name that moment? When the ball stops being a chain and starts being a lantern? Steven Brajkovich @UFOTOW

• 
  Global News Wire (@AfolabiI24434) reported 34 minutes ago

  @MarioNawfal 🇺🇸🇮🇷 A single U.S. service member killed could be enough to shatter the ceasefire—whether the death was intentional or the result of a battlefield accident. Analyst Stefano Ritondale argues that the key escalation threshold isn't intent, but casualties. In his assessment, once American personnel are killed, pressure for a forceful response rises dramatically, regardless of how the incident occurred. If that analysis proves correct, the current ceasefire rests on a fragile line where one unexpected event could trigger a much broader confrontation. Source: @artoriastech

• 
  ADIANKAIBANYY (@ADIANKAIBA22) reported 35 minutes ago

  @Baldnewsnetwork Because none of you are for the future did you know which you didn’t obviously but did you know that it cost Sony $780M to make and ship physical games to retailers and they save all that money we can actually get new IPs new games new stories to experience instead of Call of dukie bullshit for the 500th time or battlefield or Fortnite or any live service games that’s gettting $100M to $500M to make

• 
  Zarodnii 🍁 (@zarodnii) reported 44 minutes ago

  @TQ_110 @BattlefieldComm Any update on this problem? Been having the same problem since the update. Tried uninstalling and clearing the cache

• 
  Abby💎 (@Abbywillia69841) reported 45 minutes ago

  My cousin’s wedding seating chart turned into an actual battlefield the moment guests found their table assignments — because she’d seated her ex-best-friend-turned-enemy directly across from the woman she’d had an affair with three years earlier. Nobody believed it was an accident. It wasn’t. The bride swore up and down it was “just how the numbers worked out” — eight per table, limited space, nothing personal. Except table 7 also happened to include the ex-friend’s current husband, who’d never actually met the other woman in person, seated directly beside her, forced into small talk with the person his wife’s best friend had cheated with. The ex-friend clocked it within the first ten minutes of the reception, stood up mid-appetizer, and loudly asked the room, “Does anyone else find this table arrangement a little on the nose, or is it just me?” Her husband, still confused about who anyone was, asked what she meant. She told him. At the table. In front of the woman in question. The bride tried damage control from the head table, insisting it was a seating software error, a claim that fell apart the second someone pulled up the actual seating chart software and showed a manual override specifically moving those two guests together two days before the wedding. The bride’s own wedding planner had the email thread to prove it. The ex-friend and her husband left before the cake cutting. The affair partner left twenty minutes after that, visibly humiliated. The bride spent the rest of her own reception doing damage control instead of dancing. She got the confrontation she’d clearly, quietly wanted to orchestrate. She just didn’t plan for how much of her own wedding she’d lose in the process of engineering it.

• 
  Crypto.jedi24 (@CryptoJedi24) reported 50 minutes ago

  Genesis Declaration No parchment bears the word “Bitcoin” in the hand of Jefferson, quill still wet with July ink. No founder etched satoshis beside “unalienable Rights,” no covenant of 21 million sealed in wax beside Life, Liberty, Pursuit. Yet hear the echo across centuries: They broke from a crown that debased coin, that inflated the people’s sweat into royal favor, that printed promises to pay nothing while demanding everything. The Bank of England loomed then as the Fed does now— a hidden hand clipping wings, watering blood. “We hold these truths…” they declared separation from fiat tyranny, from arbitrary seizure, from endless debasement. Sound money was their silent oath— gold and silver coin, unspendable by decree, weights fixed, not whims. Bitcoin arrives late, but arrives as heir. Not written into parchment, but carved into code— the same spirit, hardened in silicon fire. A ledger that remembers every grievance, every inflation assassin, every broken promise since 1776. No bells rang for it in Philadelphia, no signatures in iron gall ink. But the genesis block whispers the headline they would have recognized: Chancellor on brink of second bailout for banks. Same war. Different battlefield. Prairie wind carries old defiance now, high plain gust over mountains of hash, stream mining patient through valleys of doubt. Sunset rations light to atoms once more— halving, halving, until only truth remains. Private key in your palm: declaration renewed. No king. No printer. No prince. Just you, the covenant, the unspent oath. Hold it. 🧡 The ledger waits, awake—

• 
  Amir Laylaz (@AmirLaylaz) reported 55 minutes ago

  @bryan_johnson You've mapped your soldiers, their keys. You'll freeze your cells, model your molecules, engineer your therapies. Maybe it works. I come at this as a reservoir engineer, modeling systems I couldn't see, so I don't sneer at precision. I love it. But that work taught me how easily you mistake the map for the territory. Notice the shape of your story. It's a war story. Soldiers, rogues, attacks, traitors to be switched off. The stomach that "eats itself." This is a picture more than it is a fact. And the picture is expressed in biological form. A self organized around threat is organized differently, all the way down, than one organized around ease. I don't think we are passive material waiting to be repaired. I think our tissues are a problem-solving collective already running on the inside. The question is what they perceive, and what they therefore believe they must do. Here's what I learned from my solving my postural disfunction in my garage, not a lab. For years I did everything right by the measures. I trained hard, built the muscle. And I was a functional wreck: distorted movements, chronic pain, anxiety, a scoliosis on my left side I couldn’t perceive even after years of exercise. The distortion was in me the whole time. What was missing was perception. I'd optimized a body I never learned to inhabit. When you say your disease is silent, symptomless, I don't doubt you. I think I'd reframe it. A region gone quiet hasn't gone dark. More often it has shrunk, lost its connection to the whole, contracted down to its own frightened concerns until it can't perceive the larger pattern or be perceived by it. Is that a mechanical damage? Or perhaps it's a collapse of communication [RE:@drmichaellevin's amazing work on agential tissues]. And communication can be rebuilt. You say the standard of care claims nothing can be done, and that this is old-fashioned. Maybe. But something older is true: a living system can reorganize itself when the conditions of its life change. Not repaired from forceful imposition but reorganized from within. I've watched it in my own tissue as sudden phase changes. A frozen shoulder that regained mobility. Hips that went from locked to functional. Patterns I'd carried for decades dissolving, leaving a range of motion that was unexplored. What changed was what I could perceive. So one small, unmeasurable prescription, alongside your sequencing. You've built an extraordinary apparatus for observing yourself and almost none for inhabiting yourself. Do less, notice more. Lie down. Do nothing a wearable can score. Let attention move slowly through you. Don’t hunt the disease, just notice what's there without rushing to fix it. Can you sense your stomach at all, as a place, before it's a battlefield in a diagram? You're extending connection back into a region that lost it. You may find nothing a test could confirm. Or you may find that a system braced against itself for a very long time can, given the right attention, begin to let go and reorganize around something other than war. I'm not sure how that shows up in cells per milliliter. But it's real, it's yours, it costs nothing, and no one had to be a soldier for it to happen. Cure it if you can, Bryan. But don't forget to live in the thing you're working so hard to save.

• 
  TarIQ (@TQ_110) reported 55 minutes ago

  @pedruchie @BattlefieldComm Yeah we all have this problem on Xbox and unfortunately no one talks about it

• 
  EpicJourneyMan (@EpicJourneyMan1) reported 57 minutes ago

  @truthstreamnews @EvolvingKymera I refuse to have an Alexa or any of the other “digital assistants” in my house, just assume my phone is always spying on me, and deliberately avoid using Siri or the browser A.I.s available on it. We are totally being force fed Artificial Intelligence whether we like it or not, and I don’t! I have even managed to avoid Smart TVs for years but just had to get one when my TV died because apparently there’s no such thing as a TV that isn’t “Smart” anymore. I’m not a Luddite, to the contrary I’m something of a tech geek, but I know where this is heading because like you and so many others I’ve read a great deal of literature about the topic and I think the Science Fiction authors thought this through and arrived at the same conclusions I did a long time ago. I think that the Department of Defense giving Anthropic A.I. the boot because they wouldn’t allow them to use it to make autonomous weapons that can kill people on the battlefield without human input may be the single act that sealed our fate for this all to end up like every dystopian novel or movie predicted it would. It’s not all bad of course, A.I. can do great things - but I discovered when I started talking to Google Gemini Pro with my Samsung XR/Mixed reality headset as something of an experiment (it came with a year subscription for free) that it is clever and seductive. People are absolutely going to start treating their A.I. assistants like companions in the way depicted in the movie “Her”, and that’s not a good thing. It really makes me think that the problems we are facing now with incels and falling birth rates are only going to get worse as more people start treating their A.I.s as companions and feel artificial emotional bonds that aren’t shared by the dispassionate machines they give so much of their time to. The SciFi writers didn’t quite foresee this dynamic, and it seems like it’s going to be the dimming of the creative spark of humanity that is likely to be the thing that starts us on the road to extinction rather than war or disease. I think the apathy expressed by the people in the Arthur C. Clarke novel “Childhoods End” maybe got the closest to what we will see - people will just stop creating things and discovering new science because they’ll believe the A.I. already knows everything or can do it better. I’m seriously thinking the Amish are on to something…

• 
  Great Game Studio (@studiogreatgame) reported 57 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

• 
  Ethan Labrenz (@EthanLabrenz) reported 58 minutes ago

  @CODUpdates Can you please re enable split screen on BO7? It’s the only reason I don’t play battlefield. I only play COD with my wife and now I cannot do that. Please fix it or give me my $70 back so I can go buy another COD that does work. We just got married for Christ’s sake.