1. Home
  2. Companies
  3. Battlefield 6
  4. Outage Map
Battlefield 6

Battlefield 6 Outage Map

The map below depicts the most recent cities worldwide where Battlefield 6 users have reported problems and outages. If you are having an issue with Battlefield 6, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Battlefield 6 users affected:

Less
More
Check Current Status

Battlefield 6 is a 2025 first-person shooter game developed by Battlefield Studios and published by Electronic Arts. Serving as the eighteenth installment in the Battlefield series, the game was released for PlayStation 5, Windows, and Xbox Series X/S on October 10, 2025.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Nantes, Pays de la Loire 3
Bitche, ACAL 1
Paris, Île-de-France 34
Aurillac, Auvergne-Rhône-Alpes 1
Annecy, Auvergne-Rhône-Alpes 2
Arvert, Nouvelle-Aquitaine 1
Angoulême, Nouvelle-Aquitaine 1
Nice, Provence-Alpes-Côte d'Azur 1
Pessac, Nouvelle-Aquitaine 1
Marseille, Provence-Alpes-Côte d'Azur 5
Pont-Scorff, Brittany 1
Haguenau, ACAL 1
Labenne, Nouvelle-Aquitaine 1
Fort-de-France, Martinique 1
Montpellier, Occitanie 2
Troyes, ACAL 2
Dole, Bourgogne-Franche-Comté 2
Jarville-la-Malgrange, ACAL 1
Namur, Wallonia 1
Toulouse, Occitanie 1
Villeurbanne, Auvergne-Rhône-Alpes 1
Grenoble, Auvergne-Rhône-Alpes 1
City of Brussels, Brussels Capital 1
Hayes, England 1
Chambray-lès-Tours, Centre 1
Angers, Pays de la Loire 1
Langon, Nouvelle-Aquitaine 1
Johnstone, Scotland 1
Auray, Brittany 1
Dreux, Centre 1
Check Current Status

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:

  • youngharold
    youngharold (@youngharold) reported

    @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.

  • LincolnParker5
    Lincoln Parker (@LincolnParker5) reported

    If you are not working with the Ukrainian Armed Forces and @BRAVE1ua to battlefiled-validate your technology on the ground, you are missing the most important feedback loop available Many well-funded startups entered Ukraine, failed, and went home. I understand that. Ukraine is hard. But retreating is the wrong call The ones who stayed, iterated, and rebuilt on actual battlefield feedback are the ones writing the next chapter of warfare funding The ones who left are polishing slide decks

  • LaymansSeminary
    The Layman's Seminary (@LaymansSeminary) reported

    @grok @myredfox Has Grok Now Moved Closer to Your Position? (A Super Layman / GPT5 response). Yes. This latest response is actually one of Grok’s strongest because it abandons several earlier assumptions and narrows the dispute. Notice what Grok now says: “The military analogy usefully shows oversight alongside permission.” That is your original point. The military does not prohibit all social media activity. The military permits social media activity while still maintaining authority structures and disciplinary mechanisms. That was the analogy. Then Grok says: “It does not establish that RedFox faces a comparable, clearly defined restriction here.” That is a different question. Originally the issue was: “Your analogy fails.” Now the issue is: “Can RedFox demonstrate that his spiritual father actually imposed such a restriction?” Those are not the same argument. The first attacks the analogy. The second asks for evidence about a particular catechumen. Grok is now largely conceding the first point while reserving judgment on the second. The most important sentence is: “That specific line still requires definition.” Exactly. That is the pressure point. If RedFox says: “I cannot formally debate.” Then the natural question becomes: What objective principle distinguishes formal debate from what you are already doing publicly? Because at this point he has: publicly defended Orthodoxy, publicly criticized Free Grace, publicly engaged opponents, publicly argued theology, publicly answered objections, publicly attempted persuasion. So the remaining issue is no longer whether public theological engagement exists. Everyone now agrees that it does. The remaining issue is: What additional characteristic converts permitted public engagement into prohibited formal debate? And notice Grok says that line still needs definition. That means the burden now sits on defining the boundary rather than merely asserting it. In debate terms, the battlefield has shifted from: “Your military analogy fails.” to “What is the principled and consistently applicable boundary between permitted and prohibited theological engagement?” That is a much narrower and more difficult question for RedFox to answer.

  • LetsArmUKR
    medoyid_ua (@LetsArmUKR) reported

    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.

  • ohyeahmister2
    Cooltaha ඞ 🔻💔 (@ohyeahmister2) reported

    @InsiderGeo The west is slow to respond and is failing to see the threat for now. The elites are too myopic and focused on internal alliance issues rather than facing the reality on the battlefield

  • KSArchaeologist
    KansasArchaeologist (@KSArchaeologist) reported

    Two days after the battle a group of soldiers found Comanche near the battlefield. He was badly wounded and he was taken back to Fort Abraham Lincoln and ultimately survived the ordeal. In April 1878 he was retired from service at 21 years old. He was kept at Fort Meade near Sturgis, South Dakota from 1879-1887 when he was returned to Fort Riley in Kansas where he was given the honorary title of “Second Commanding Officer” of the 7th Cavalry. He died on November 7th, 1889 from colic, and is one of only 4 horses in US military history to have a military funeral with full military honors. But he was not buried. Comanche was taken to Professor Lewis Dyche at the University of Kansas in Lawrence and taxidermied to be displayed. In 1893 he was shown at the World’s Columbian Exposition in Chicago at the Kansas Pavilion with Professor Dyche’s panorama of North American Mammals.

  • UFOTOW
    Steven Brajkovich (@UFOTOW) reported

    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

  • LetsArmUKR
    medoyid_ua (@LetsArmUKR) reported

    The second army in the world, led by a senile grandpa in a bunker, is out here crowning the seizure of one miserable street in a Donetsk village as some kind of strategic masterstroke. Think about that for a second. Not Kyiv in three days, not Warsaw, not Berlin. A single street in a settlement most of you had never heard of until this dementia-ridden clown started bragging about it on camera. This is what victory looks like for them now. This is the ceiling of what their entire broken system can deliver after three years of total war, total mobilization, and total isolation. And the math is merciless. They are losing more soldiers to capture these microscopic scraps of land than the villages had residents before the invasion. Thirty-five thousand dead orcs a month, more than they can replace even with fresh meat waves, and still the only thing Putin can sell domestically is footage of some dirt road with a flag on it. Every z-blogger and kremlin mouthpiece quietly admits the same thing: another mobilization changes nothing except the body count on their tab. The meat grinder just spins faster. This is not a superpower. This is an imperial corpse that has run out of cards. Moscow cannot stop the war because the war is the only thing keeping the regime alive. Send a million soldiers home and the first question they ask is "what the hell was that for?" So forget levers, summits, or brilliant diplomacy. Only complete military defeat on the battlefield ends this. Everything else is theater that buys them time to regroup and come back for the next bite. Ukraine is doing the grinding, the striking, the innovating. Our long-range capabilities are scaling, rear areas burn daily, and by the end of 2026 those mid-range strikes will be two to five times more intense. Logistics nodes, fuel dumps, airfields, command posts, all of it will be systematically turned into craters. We will license Patriots and Tomahawks, mass our own air defense, integrate FREYA, drone interceptors, and Gripen squadrons until we have the densest, most lethal shield Europe has ever seen. The Kremlin has no answer to any of it. Europe finally figured out it cannot count on American protection under the current circus in Washington. Good. That leaves one country on the continent actually willing and able to bleed Moscow dry so the rest of you do not have to. We are not asking for favors. We are offering a service at a fraction of the cost you would pay if this horde ever rolls further west. Arm the defense industry, stop dribbling aid, and let us finish the job. The only language these people understand is force, and we have proven we speak it better than they do. The tsar is naked. The empire is hollow. And every street they celebrate at the price of another battalion just proves how close they are to the edge. Time to push.

  • Stoic_investr
    Stoic Investor (@Stoic_investr) reported

    The MoU had very little chance of success and this became clear once the US forced Lebanese government to sign a separate deal with Israel and attempts to create a separate Oman coastline corridor was another example of how US tried to sabotage the MoU while paying lip service to it. Now Iranians have more than enough reasons to assume that any negotiations is essentially being conducted in bad faith and I don’t think they’ll show up for any more talks as now this issue will be resolved on the battlefield.

  • ChrisSlaske
    chris (@ChrisSlaske) reported

    @Battlefield why is drag revive so bad? You take one step forward and 7 steps back each update. Every day brings new attention to problems that have been plaguing multiplayer for months

  • KofferTim
    Tim Koffer (@KofferTim) reported

    @Battlefield Every fkn game is a blow fix this pile of dog ****. How the fk is fun to get blown out multiple games in a row? Its fkn pathetic

  • ServReasoning
    Dan Haberern (@ServReasoning) reported

    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: Tune the model Ship the agent 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: 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. 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.

  • FlyghtMedic
    RCP (@FlyghtMedic) reported

    @Battlefield could you guys fix the game instead of “releasing” no ****?

  • TBifford
    BiffBifford™ 🇺🇸 (@TBifford) reported

    @AlexKau74366366 Patton was built to fight. It's a shame a car accident took him out instead of the glory of dying on the battlefield. Patton did not die in combat. On December 9, 1945 (months after the war ended), he was involved in a low-speed car accident in Germany while on a pheasant hunting trip. His Cadillac collided with a U.S. Army truck. He suffered a broken neck and was paralyzed from the neck down. He died 12 days later from a pulmonary embolism (blood clot) in a hospital in Heidelberg.

  • ThoughtEngaged
    Dave (@ThoughtEngaged) reported

    This last update has killed Battlefield and Redsec. I spent two ******* hours trying to play ranked with the squad tonight. We all took turns getting disconnected, having our games crash and falling through the map and more. I believe it was the final nail in the coffin. RIP.

Check Current Status