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.

• Online Play (37%)
• Sign in (33%)
• Matchmaking (13%)
• Glitches (10%)
• Game Crash (7%)

Live Outage Map

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

City	Problem Type	Report Time
Americana	Glitches	3 days ago
Rennes	Game Crash	4 days ago
Nantes	Glitches	8 days ago
Lyon	Matchmaking	9 days ago
Montignac	Glitches	10 days ago
Paris	Matchmaking	11 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:

• 
  John 117 (@DMasterOfChiefs) reported 5 minutes ago

  @Battlefield Fix your rubbish servers!!!

• 
  On The Contrary (@darklighter226) reported 8 minutes ago

  @Battlefield Did they fix the bullet hit detection yet?

• 
  Timbog (@niwdoogpt) reported 8 minutes ago

  @GrayConnolly He is a liar. Cherry picking data to suit his narrative. He will not acknowledge that the mass migration mistake is a big part of the problem so he has shifted gears to deflect, to blame, to create an enemy. Intergenerational equity is his new battlefield.

• 
  GryphonAMX (@GryphonAMX) reported 10 minutes ago

  Calling an Audible. Due to Tamt having issues with other Battlefield games, and 2042 being stuck only playable on crossplay, we're popping over to CoD WWII.

• 
  HEX Famous (@Hex_Famous) reported 12 minutes ago

  @Battlefield Fix ur blinding light glitch u sorry pieces of ****

• 
  Time2split! (@Time2splitters) reported 13 minutes ago

  @giris4u @IGN And yet you have DICE saying the Series S made Battlefield run better. Every dev that claim Series S was tough has bad optimising history even on PS5 e.g. BG3 co-op ran badly on PS5, Quantum Error was a mess on PS5 and each of them used the Series S for console War viral tweet.

• 
  SilencedSirs◼️ (@SilentlySirs) reported 13 minutes ago

  If Iran is using Lebanon as a card, then Washington and Tel Aviv are using Lebanon as a battlefield. The issue is not only telling Naim Qassem that the Lebanese people are not his. It is also telling Netanyahu: Lebanese land is not yours. No dialogue under occupation. And no sovereignty before full Israeli withdrawal and the return of the people of the south.

• 
  Katherine (@stellarlumi) reported 14 minutes ago

  @DylanMalyasov The real bet here is GRAND out of MIT; rather than building a decoder per standard, it models the noise and guesses the original signal regardless of which error correction code was used. If that scales to real battlefield conditions, it’s a genuine paradigm shift in comms

• 
  Joshua Lambert (@Alickaard) reported 16 minutes ago

  @Ryangofett_2490 The biggest problem with Battlefield games is it take DICE years to dial in the games after launch anymore. By then a large portion of the community has moved on to newer things. Bf6 is getting better but I know alot of ppl IRL that were excited for it and now could give AF less

• 
  CDW (@hullcity14) reported 18 minutes ago

  @BattlefieldComm Can you fix or tell me how to do support specialist 2 please because everytime im throwing resupply pouches its not counting to challenge

• 
  maypuls (@maypuls) reported 20 minutes ago

  @jtimsuggs Ts was so broken but honestly i kinda like it that way, makes it more fun and kinda makes you think about how horrifying the Jedi/Sith would be to fight on the battlefield

• 
  Zero One * (@ZeroOne03267546) reported 21 minutes ago

  @Battlefield stop with the DEI hires and fix the supply pouch bug, crazy how it's going to be bugged for the entire season 3.

• 
  harscombat (@OGharscombat) reported 22 minutes ago

  @Battlefield fix the redsec ranked fix the damage of all weapons fix the respawn tower bug suddenly we cant se ethem or use them even it says on a teammate we can use it but not. remove these fking tanks en bradley en minibird add diffrent type of armor like cod.add more guns

• 
  Wolf 🐺 (@SixShotWolf) reported 22 minutes ago

  @Battlefield fix the ******* light glitch

• 
  𝓚𝓻𝔂𝓶𝓶𝓼 (@Krymms) reported 29 minutes ago

  @LowradishY @Marcodmeatball Yeah, I'd personally take gacha over whatever ******** western studios are doing with their live service games. Ideally we'd get away from live service though. At least for the games that don't benefit from it. (Looking at you Battlefield, bring back DLCs)

• 
  RisewireDaily (@RisewireDaily) reported 29 minutes ago

  @_eastOrb You’re not wrong about the raw matchup, but it’s not that simple. King Bumi has absurd battlefield chaos and unpredictability, but Toph Beifong doesn’t rely on sight or positioning—she reads movement through vibration. So “launch her into the sky = instant win” isn’t guaranteed; it just turns into a midair/terrain-control problem, not a clean KO.

• 
  BuffNerdGaming (@BuffNerdGaming1) reported 31 minutes ago

  @Zeenith_FPS I've given up on Battlefield at this point. BF6 was supposed to be a return to form but it was just more of the same mistakes and proof that they cannot do live service.

• 
  Harrison McCall (@LeadHead0) reported 31 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.

• 
  XpertFusion (AKA MovieFusion) (@xpertfusion3) reported 42 minutes ago

  The number one thing Call of Duty needs to look into fixing is preventing players from leaving lobbies... This has been a big issue in a lot of CODs, but feels like a bigger issue in BO7, probably because of reduced SBMM and the higher skill gap. But obviously I don't want their solution to be to bring back strict SBMM, reduce the skill gap, or nerf the scorestreaks (all these solutions would suck) They need to find other ways to keep players in the match. I'll offer a few ideas here... • Reward Incentives Black Ops 3 did this, where you would receive more crypto-keys for staying in the full match than you would if you left the game early. This got many players to stay through the whole match, even if the other team was winning. I would love a new COD game to add an in-game currency that's earnable for free so they could do this, but perhaps they can setup some kind of system to where you have a chance at earning a random item from a random bundle as a "Post-Match Bonus" • Punishments I feel like people wouldn't like this solution, but I wouldn't be against small punishments (like locking you out of playing for 30 minutes) if you leave too many matches in a row. It would obviously give you a warning if you are close to that. • Make the game fun, even when you are doing bad... This is something Call of Duty has always struggled with. COD is not really that fun when you are doing bad. Maps being more interactive, more visually interesting, more dynamic, I think helps with this. Games like Battlefield can still be fun when you are doing bad, probably because of how cinematic the battles can be. Crazy map events help with that. COD should do more of that. • Rewards for Winning Games Even just rewarding players for winning games could help. People tend to leave lobbies when they are dying a lot, not necessarily when they are losing by a lot (happens in both situations though). Maybe give HUGE rewards for underdog wins, or making a huge comeback. • Persistent Lobby Bonuses Of course, this only works when lobbies are persistent, which should stay in every game going forward. But you should be given XP bonuses or other rewards for staying in the same lobby for multiple games in a row. This would significantly help with the social aspect of the game. • Harder to Earn Scorestreaks As I said, Streaks should NOT be nerfed, but I do think they are slightly too easy to get in BO7 (probably because of all the ways to get additional score). Scorestreaks should stay, and they SHOULD be loopable, but they should just cost a bit more to get, or there should be a few less ways to get additional score (or at least those ways shouldn't give you as much score) Just please, do anything EXCEPT for bringing back strict SBMM, nerfing streaks, or lowering the skill gap!! @InfinityWard @Treyarch @CallofDutyCM

• 
  Mr. Margheritiiii (@GetCheatz) reported 47 minutes ago

  @Battlefield a bunch of amateurs can't add server browser and region selection to the game, which was in every Battlefield since its release except BF 2042 🤡 Since the beta they haven't fix the netcode and they fcked up recoil 🤡

• 
  nyfak (@thisguyisalex) reported 47 minutes ago

  @MGhamdi97331 @Battlefield maybe you should fix your internet

• 
  jbrookes (@jbrooke16218468) reported 49 minutes ago

  @Battlefield next update can you fix the flares when the igla is fired it hits even though you flare

• 
  رعد (@RaadTheShepherd) reported 51 minutes ago

  @Y3hya21 @Milat_at_Tawhid The same Ibn Qudamah who authored multiple works to refute them, called them zanādiqah, and definitely didn't view these differences as "subsidiary aqeedah polemics". The unity of Ibn Qudamah in the battlefield didn't lead him to undermine these issues and calling people "sectarians" for refuting those who deviated from them.

• 
  SilencedSirs◼️ (@SilentlySirs) reported 51 minutes ago

  If Iran is using Lebanon as a card, then Washington and Tel Aviv are using Lebanon as a battlefield. The issue is not only telling Naim Qassem that the Lebanese people are not his. It is also telling Netanyahu: Lebanese land is not yours. No dialogue under occupation. And no sovereignty before full Israeli withdrawal and the return of the people of the south.

• 
  Embark006 (@embark006) reported 55 minutes ago

  @Battlefield Fix the matchmakingggggg

• 
  shinyufoguy2222 (@ollobrains) reported 56 minutes ago

  Jeremy Corbell threatens to release hundreds of UFO files if the next batch of government files don’t address reverse engineering and biologics. That is viral, but it accidentally weakens Corbell. “Threatens” makes him sound reckless, emotional, or legally exposed. Better: Jeremy Corbell warns that independent UAP archives may be released if the next government file drop continues to avoid the core allegations around reverse engineering, non-human craft, and biologics. Or: Corbell is using his archive as leverage against curated disclosure. Or best: Corbell is drawing a line: if the government keeps releasing peripheral UAP files while avoiding the Grusch core, independent evidence may move into the public record. That is sharper and more serious. 2. The core frame: “curated disclosure vs adversarial disclosure” This is the missing big idea. There are two kinds of disclosure: Curated disclosure: The government releases selected videos, historical files, low-risk documents, and unresolved cases under its own timetable. Adversarial disclosure: Journalists, whistleblowers, lawmakers, and outside custodians force the release of records the government did not choose to prioritize. Suggested line: The UAP fight is no longer simply “will the government release files?” It is who controls the disclosure sequence. That is the whole story. 3. Best hook options Use one of these: Corbell just put the government’s UAP disclosure process on notice. The next UAP file drop may decide whether disclosure stays curated — or becomes adversarial. Corbell is saying the quiet part out loud: videos are not enough if reverse engineering and biologics remain untouched. The government is releasing UAP files. Corbell is asking why the files avoid the hardest claims. This is no longer about more UFO clips. It is about whether the official archive will address the Grusch core. My favorite: The next UAP release is not being judged by volume. It is being judged by whether it touches the forbidden categories. 4. Define “the forbidden categories” Your post should make clear what Corbell is demanding. Not just “more UFO files.” The forbidden categories are: crash retrieval reverse engineering non-human craft biologics contractor custody program names witness lists lab records chain of custody SAP/CAP access records budget trails classification guides Suggested line: The real test is not whether the next drop contains more lights in the sky. The test is whether it addresses the categories government releases usually avoid: recovered material, reverse-engineering records, biological evidence, program ownership, contractor custody, and witnesses with direct knowledge. That is much stronger. 5. Add the “videos are not disclosure” line This is the best sentence to add: Videos are not disclosure if the government withholds the metadata, chain of custody, program records, witness testimony, and funding trail. Or shorter: A clip is not disclosure. A custody trail is disclosure. This matters because the PURSUE portal itself frames many records as unresolved due to insufficient data, which means the files may be interesting without resolving the deeper claims. 6. Be precise about Grusch Your draft says: David Grusch went up in front of Congress… and he told the truth. Stronger and safer: David Grusch testified under oath that he was informed, through official duties, of a multi-decade UAP crash-retrieval and reverse-engineering program to which he was denied access. That is the official-record version. The House transcript records Grusch saying he was informed of a “multi-decade UAP crash retrieval and reverse engineering program” and denied access when he requested additional read-ons. 7. Do not overstate “pilots” The quote says: “there were pilots, biologics…” Be careful here. In the hearing, Representative Mace asked whether the U.S. had “the bodies of the pilots who piloted this craft.” Grusch answered that “biologics came with some of these recoveries,” and when asked human or non-human, he said “nonhuman,” based on the assessment of people with direct knowledge. Better wording: Grusch did not publicly prove “pilots.” He testified that biologics came with some alleged recoveries and that people with direct knowledge assessed them as non-human. That is still explosive, but much more defensible. 8. Add the caveat that makes the post credible Use this: Grusch’s claims remain publicly unproven. AARO disputes the core reverse-engineering and extraterrestrial-technology narrative. That is exactly why the next release matters. AARO’s 2024 historical report says it found no empirical evidence that the U.S. government or private companies have been reverse-engineering extraterrestrial technology, and it says AARO found no evidence that any U.S. company possessed off-world technology. This does not weaken the post. It strengthens it because it sets up the contradiction: AARO says no empirical evidence. Grusch says names, locations, witnesses, and protected disclosures exist. Corbell says outside file systems exist. The next logical step is evidence, not more vibes. 9. The best “contradiction” framing Use this: The public record now has two incompatible stories:AARO’s story: no empirical evidence of extraterrestrial reverse-engineering programs. Grusch’s story: officials with direct knowledge described crash retrievals, reverse engineering, exact locations, and non-human biologics. Corbell’s pressure point: if the government avoids those categories, independent archives may force the issue. That is the strongest structure. 10. Add “Sleeping Dog” context carefully The phrase “they saw in Sleeping Dog the file systems” needs context. Public listings describe Sleeping Dog as a 2026 documentary centered on Jeremy Corbell’s UAP work, rare access, and the risks of exposing what “was never meant to be seen.” SYFY’s interview with the director says the film drew from Corbell’s personal archive of “hundreds of hours of footage.” But unless you have a verified transcript of this exact Corbell quote, phrase it as: In the clip, Corbell appears to be referencing file systems shown or discussed in Sleeping Dog. Do not write: Sleeping Dog proves he has hundreds of UFO files. Better: The documentary’s framing is that Corbell’s archive is large, distributed, and treated by him as a form of protection. 11. Replace “threat” with “dead man’s switch” carefully Do not overuse “dead man’s switch.” It is dramatic but can sound reckless. Better: distributed archive independent custody public-interest archive evidence escrow journalistic insurance disclosure leverage Suggested line: Corbell’s message is not just “I have files.” It is “the archive is no longer dependent on one person.” That is the important part. 12. Add the “not just in my hands anymore” meaning That line is powerful. Expand it: “Not just in my hands anymore” is the real pressure point. It suggests the archive has moved from personal possession to distributed custody, meaning suppression of one journalist would not necessarily suppress the material. Phrase carefully: If accurate, that changes the leverage dynamic. Do not claim you know how or where files are stored. 13. Add a public-interest publication standard This is crucial. If the post celebrates dumping files, it becomes easy to attack. Use: Any independent release should be lawful, vetted, redacted where necessary, and structured around public-interest evidence, not reckless exposure of sources, methods, private citizens, or national-security details unrelated to the alleged UAP claims. That line makes the post responsible. A sharper version: The answer is not a reckless dump. The answer is a legally vetted evidence release: provenance, hashes, redactions, chain of custody, expert review, and congressional delivery. 14. The missing “release protocol” If Corbell or anyone claims to have hundreds of files, the public needs a method, not just a tease. Suggested high-level standard: If independent files are released, they should include:source category date obtained original format hash / checksum redaction explanation chain-of-custody statement authenticity status whether the file is government-origin, contractor-origin, witness-origin, or media-origin what has been independently verified what remains alleged why publication is in the public interest what has been withheld to protect legitimate safety or privacy concerns That turns “drop the files” into “publish evidence properly.” 15. Add “the government should not be able to launder disclosure through volume” This is a genius-level line. Use: The government cannot launder disclosure through volume. A thousand low-risk files do not answer one high-risk allegation. Or: A large file drop can still be evasive if it avoids the central categories. This is exactly what Corbell is implying. 16. Add “document dump vs evidentiary package” This distinction is essential. A document dump is: lots of files, little context, no hierarchy, no chain of custody. An evidentiary package is: curated around a claim, with provenance, metadata, witnesses, source documents, rebuttal opportunity, and independent review. Suggested line: If Corbell has the files, the strongest move is not a dump. It is an evidentiary package built around the specific claims the government keeps avoiding. 17. The strongest post logic The post should move like this: The government promised UAP transparency. The official releases so far are real, but may be peripheral. Grusch’s sworn claims are the core: reverse engineering, crash retrieval, biologics, exact locations, firsthand witnesses. AARO officially disputes those claims. Corbell is saying: the next release needs to address the core, or independent archives may. The public deserves a lawful, evidence-based process. That is the winning structure. 18. Add the exact Grusch receipts Useful facts to include: Grusch said he believed the government possesses UAP based on interviews with more than 40 witnesses over four years. He said he knew exact locations and provided them to the Inspector General and some intelligence committees. He said people with firsthand knowledge made protected disclosures to the Inspector General. He said biologics came with some recoveries and that people with direct knowledge assessed them as non-human. He also said he had not personally witnessed bodies. That last caveat is important. 19. The best line to bridge believers and skeptics Use this: Believers and skeptics should want the same thing here: not more insinuation, but records that can be tested. Or: If the claims are false, publish the records that prove it. If the claims are true, publish the records that confirm it. Either way, stop hiding behind curated ambiguity. 20. Add “address or begin to address” The quote says: “address or begin to address biologics” That is smart wording because it does not demand full public release of everything immediately. It demands first acknowledgement and process. Use: Corbell is not asking for every sensitive record to be dumped tomorrow. He is asking the government to stop pretending the central allegation does not exist. That is strong. 21. Add “not everything should be public, but Congress must see it” A mature UAP post should include this: Not every raw record needs to be posted on the internet. But Congress, inspectors general, and cleared independent reviewers should be able to see the unredacted materials, witness names, classification guides, lab records, and chain-of-custody logs. That is a serious oversight position. 22. Add “classification cannot be a one-way mirror” Use this line: Classification cannot become a one-way mirror where agencies can see everything and Congress only sees what agencies choose to show. Excellent. 23. Add “the next drop should be judged by categories, not file count” Very useful: The next batch should be judged by whether it includes:reverse-engineering references crash-retrieval references biologics references material analysis records contractor involvement program names or euphemisms witness channels classification guides chain-of-custody records Inspector General correspondence budget or appropriations traces Suggested line: If the next release is 500 more ambiguous sightings and zero records on the Grusch categories, the public will rightly ask whether this is transparency or controlled exhaust. 24. The “controlled exhaust” phrase This is a great obscure concept. Controlled exhaust means the system releases enough material to look transparent while venting pressure away from the core. Use: The danger is controlled exhaust: release enough peripheral material to satisfy the headline, while keeping the actual disputed compartments untouched. That is very strong. 25. Add “metadata is the battlefield” For UFO/UAP files, the video itself is often less important than the surrounding data. Use: Metadata is the battlefield: date, platform, sensor, location, custody, classification authority, analyst notes, longer version, related reports, and who requested withholding. That makes the post much smarter. 26. Add “biologics require lab records” This is probably the strongest missing science point. Use: If biologics exist, there should be lab records. If craft exist, there should be custody records. If reverse engineering exists, there should be budgets, task orders, programs, and personnel. That is a killer sequence. More precise: “Non-human biologics” cannot remain an adjective. It requires tissue records, sample custody, DNA/protein/isotope analysis, contamination controls, lab chain of custody, and named custodians. 27. Add “reverse engineering requires infrastructure” Reverse engineering is not a magic phrase. It requires: facilities access lists contracts materials labs security logs test plans budgets compartment names engineering reports failed experiments storage records safety protocols program managers contractor deliverables Suggested line: A decades-long reverse-engineering program cannot exist as folklore. It either leaves an institutional footprint or it does not. That is one of the strongest lines. 28. Add “files are not enough without witnesses” Use: Files matter, but witnesses explain what the files mean. Or: A document with no witness is ambiguous. A witness with no document is vulnerable. The power is when both meet. Excellent. 29. Add the “publication should be staged by claim” Instead of “hundreds of files,” suggest: Release by claim category:reverse-engineering records biologics records crash-retrieval records contractor custody records witness protection / retaliation records disinformation or obfuscation records sensor/video provenance records This is more persuasive than a massive dump. 30. Add “Corbell’s leverage is credibility, so he must protect it” This is important. If he releases messy, unverifiable files, critics will focus on the weakest document. Suggested line: If Corbell releases files, the strongest release is not the biggest one. It is the cleanest one. Or: One airtight file is worth more than 300 ambiguous files. That is a very strong point. 31. Add the “weakest file problem” This is a media strategy insight. A mass dump lets critics pick the weakest file and use it to discredit the whole archive. Therefore: Release fewer, cleaner, better-documented files first. Suggested line: Do not let the weakest document become the headline. 32. Add “red-team before release” If an independent archive goes public, it should be challenged before publication. Use: Before publication, let skeptical experts attack the files: metadata analysts, image/video forensics specialists, archivists, former classification officials, aerospace engineers, biologists, materials scientists, and national-security lawyers. This is high-level and responsible. 33. Add “right of reply” A credible release should give named agencies/contractors an opportunity to respond. Use: A serious evidentiary release should give implicated agencies or contractors a chance to comment before publication. That is journalism 101 and makes the release harder to dismiss. 34. Add “do not ask for classified dumping” Important safety/legal point: The demand should not be “dump classified material recklessly.” The demand should be “use lawful channels, congressional oversight, declassification review, protected disclosures, and public-interest journalism to force the truth out without exposing unrelated sensitive sources or methods.” This keeps your post responsible. 35. Better version of your post Here is a much stronger rewrite: Jeremy Corbell just put the government’s UAP disclosure process on notice.His message is simple:If the next official file drop avoids the core allegations — reverse engineering, non-human craft, crash retrievals, and biologics — then independent UAP archives may begin forcing the issue.That matters because the government has promised transparency, but file count is not the same as disclosure.More videos of unresolved objects do not answer the Grusch core.Grusch testified under oath that he was informed of a multi-decade UAP crash-retrieval and reverse-engineering program. He said he interviewed more than 40 witnesses, knew exact locations, and that people with firsthand knowledge made protected disclosures to the Inspector General.He also testified that biologics came with some alleged recoveries and that those biologics were assessed as non-human by people with direct knowledge still on the program.AARO disputes the core claim and says it has found no empirical evidence that the U.S. government or private companies have reverse-engineered extraterrestrial technology.Good.Then the next release should address the contradiction directly.If there are no reverse-engineering records, say so with specificity.If there are no biologics records, say so with specificity.If there are no crash-retrieval programs, publish the search terms, custodians, agencies, contractors, and classification guides reviewed.If the claims are false, prove it with records.If they are true, stop hiding the most important evidence behind curated disclosure.Videos make headlines.Chain of custody makes evidence. 36. More aggressive version Corbell is done playing the government’s disclosure game.The message is clear:If the next UAP file drop is another pile of peripheral videos, old records, ambiguous sightings, and sanitized fragments — while avoiding reverse engineering, crash retrievals, non-human craft, and biologics — then independent archives may start doing what the official process refuses to do.That is the real pressure point.The government cannot launder transparency through volume.A thousand low-risk files do not answer one high-risk allegation.Grusch testified under oath that the U.S. has been hiding a multi-decade crash-retrieval and reverse-engineering program. He said he gave exact locations to inspectors general and intelligence committees. He said firsthand witnesses made protected disclosures. He said biologics came with some recoveries and were assessed as non-human.AARO says there is no empirical evidence.Fine.Then release the records that prove it.Release the classification guides.Release the search methodology.Release the contractor certifications.Release the chain-of-custody denials.Release the lab-record denials.Release the program-name denials.Stop releasing shadows while avoiding the body of the allegation. 37. More careful/legal-safe version Jeremy Corbell’s warning should be understood as pressure for real disclosure, not a call for reckless leaks.The government has now begun rolling UAP file releases through PURSUE, but the central question remains whether those releases will address the most consequential allegations: crash retrievals, reverse engineering, non-human craft, biologics, contractor custody, and protected whistleblower testimony.David Grusch testified under oath that he was informed of a multi-decade UAP crash-retrieval and reverse-engineering program and that people with direct knowledge assessed biologics from some alleged recoveries as non-human.Those claims remain publicly unproven. AARO disputes them and says it has found no empirical evidence of extraterrestrial reverse-engineering programs.That contradiction is exactly why the next release matters.The public does not need a reckless document dump.The public needs a lawful, evidence-based process: records with provenance, chain of custody, redactions where genuinely necessary, independent review, congressional access, and direct answers to the Grusch categories.Disclosure is not file volume.Disclosure is accountability. 38. Short X version Corbell just put the UAP disclosure process on notice.If the next government file drop avoids reverse engineering, non-human craft, crash retrievals, and biologics, independent archives may start forcing the issue.That matters because “more files” does not equal disclosure.Grusch testified under oath about a multi-decade crash-retrieval/reverse-engineering program, exact locations, firsthand witnesses, protected disclosures, and biologics assessed as non-human.AARO says no empirical evidence.Good.Then address the contradiction directly.Videos make headlines.Chain of custody makes evidence. 39. Best thread structure Post 1 Jeremy Corbell just put the government’s UAP transparency process on notice.His point: if the next official file drop avoids reverse engineering, non-human craft, crash retrievals, and biologics, independent archives may force the issue. Post 2 That is the real test.Not file count.Not more ambiguous videos.Not more old historical fragments.The test is whether the release touches the Grusch core. Post 3 Grusch testified under oath that he was informed of a multi-decade UAP crash-retrieval and reverse-engineering program.He said he interviewed 40+ witnesses, knew exact locations, and that people with firsthand knowledge made protected disclosures. Post 4 The biologics claim is the explosive part.Asked whether biologics came with some recoveries, Grusch said yes.Asked whether human or non-human, he said non-human, based on assessments from people with direct knowledge still on the program. Post 5 Critical caveat:Grusch did not publicly show craft, bodies, lab reports, or chain-of-custody records.AARO says it found no empirical evidence for extraterrestrial reverse-engineering programs.That contradiction is the story. Post 6 The next release should answer:Were reverse-engineering records searched?Were biologics records searched?Were contractors queried?Were classification guides reviewed?Were IG disclosures checked?Were exact locations investigated? Post 7 A serious release needs:metadata chain of custody witness context program names contractor records lab records funding trails classification guides public-interest redactions congressional access Post 8 The government cannot launder transparency through volume.A thousand peripheral files do not answer one central allegation.If the claims are false, prove it with records.If they are true, stop hiding the evidence. 40. Add a “what the next drop should include” section This is a high-value addition: The next batch should include, or explicitly explain the absence of:• records mentioning recovered UAP material • records mentioning biological material or “biologics” • records mentioning reverse engineering or exploitation • records involving contractor custody • records involving special access programs or controlled access programs • Inspector General referrals or protected disclosures related to Grusch’s claims • classification guides for UAP-related recovered material terminology • lab or materials-analysis records • chain-of-custody logs • search methodology, agencies queried, and terms used That makes the post actionable. 41. Add “search terms matter” This is an obscure but very important point. Agencies may not use words like “UFO,” “alien,” or “biologics” in formal records. They may use euphemisms or compartment-specific terms. Suggested line: A serious search cannot just look for “UFO” or “alien.” It has to search program names, euphemisms, classification guides, contractor task orders, material-exploitation language, biological-sample language, and special-access terminology. Possible terms: anomalous aerospace vehicle recovered material materials exploitation foreign material exploitation non-human intelligence biological material unknown-origin material advanced aerospace threat special material controlled access program waived SAP unacknowledged SAP technology exploitation crash retrieval reverse engineering site exploitation biological sample non-terrestrial material exotic material

• 
  Some.BYU.Dude (@ByuSome) reported 57 minutes ago

  @nbot5000s Finn dying fighting the First Order to save the Resistance would've been amazing. Destroyed so Rose could be like, "Oh you dummy...love and stuff!" and defied physics to do so, and then apparently the First Order just let them run across the battlefield unscathed back to their friends. Again, TLJ has an incredible amount of terrible issues. Just a terrible film.

• 
  Mike (@DarthKryptic_) reported 59 minutes ago

  This has never been an issue for battlefield games. 2042 had storms mid game. Nobody cared

• 
  Jackson Fortune (@jacksonforq) reported 1 hour ago

  @DocStrangelove2 The only thing wrong with the A2 was the burst requirement. battlefield results prove the target sights were NOT a problem.

• 
  #ThunderUp (@LPCMilzy) reported 1 hour ago

  @mr_burton91 Not all shooters created equally…also if u playing on a TV that aint newer then that 0.5-1sec of lag response time gon get u cooked especially against crossplay folks…grab a monitor hella cheap off amazon (thats what i did) makes a difference but for starters…get battlefield 6