1. Home
  2. Companies
  3. Battlefield 6
Battlefield 6

Battlefield 6 status: server issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

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.

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.

At the moment, we haven't detected any problems at Battlefield 6. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

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

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

Live Outage Map

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

CityProblem TypeReport Time
Americana Glitches 1 day ago
Rennes Game Crash 3 days ago
Nantes Glitches 6 days ago
Lyon Matchmaking 7 days ago
Montignac Glitches 8 days ago
Paris Matchmaking 10 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:

  • SimeonePrime
    Fallen_Soul / Maxwell (Name Of The Muse) (@SimeonePrime) reported

    @NanashiSukii *While She Tries To Make A Run For It, She Doesn't Get Far. As Maxwell's Wing Wraps Around Her.* Jeez, Calm Down Sukii. Running Away From Your Problems {and the battlefield} Isn't Exactly The Best Idea.

  • LonelyDragon84
    Paul Johnson (@LonelyDragon84) reported

    @BattlefieldComm Redsec light glitch???? It's sometimes unplayable

  • FPS_DeviL96
    FPS_DeviL96 (@FPS_DeviL96) reported

    @Battlefield been out since October I’m Dumping half a mag into people and getting no hit registration? How can a AAA title be released in such a broken state like this! Yet you’re so ******* slo to release and update. The game is finished if you don’t fix this ****.

  • OrangeVol1321
    Orange_Vol1321 (@OrangeVol1321) reported

    @Aussiegamerhd2 @Battlefield If you're refusing to play because of "skins" we don't need you in the game. There's 200 bugs or problems with the gameplay/graphics and most of it has been there since release. It's a FPS, you can't even see your skin. Lmfao

  • RobeJoa
    Robe Joa (@RobeJoa) reported

    @Battlefield One of the support soldier assignments is broken. The one where you have to dispense ammo pouches. The counter won’t go up (I play on PS5) idk if it’s happening in the background or not but it’s not moving.

  • LeadHead0
    Harrison McCall (@LeadHead0) reported

    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.

  • Ussan_Ankon
    Ankon (@Ussan_Ankon) reported

    Being blocked by yuritards is like earning medals for service on the battlefield.

  • ChrisSlaske
    chris (@ChrisSlaske) reported

    @BattlefieldComm Audio still awful. RPGs have been broken since the speed nerf. Red sec is still **** run by sniper rats and the light glitch makes it unplayable. Go from 500 matches in seasons 1 and 2. Only to play 3 matches so far in season 3. **** off with ranked wasting everyone's time

  • swaguley
    Swaguley (@swaguley) reported

    Saying that players who don't like certain movement mechanics in Battlefield because they're just "bad at the game" is a non-sequitur. I agree, the movement isn't difficult, and killing players slide-jumping isn't either. That's not the issue. The real problem is this. - It changes the pace of combat and alters the feeling of gunfights to where they become less readable, and more annoying to play fundamentally; and more importantly: - It shifts the tone of Battlefield from the "grounded in authenticity" mantra Battlefield had, which players have come to expect from it in the market, to something much arcadier I'm happy to support more movement options as long as they fit an authenticity and believability line, but it seems even asking THAT is too much for some reason. We praise vehicle design when they move naturalistically, why is infantry combat an exception? The heart of the argument here is about Battlefield's tone, which affects how the gameplay is designed, not because some players can't "get good". You don't get players complaining about emergent movement mechanics in Rocket League, even from trash cans, because they expect it from the game's tone, Battlefield players do not. And no, citing bugs like BF3's aim stabilization jump, BF4's various movement exploits, etc. as prooftexts to justify any and all future crackhead movement mechanics in Battlefield, doesn't work either. Should we also then bring back Battlepacks just because they were in BF4 too? I get there are those of you that don't care about Battlefield's tone, therefore there is no "movement line" to cross, but you're ignoring massive swaths of players that DO care and will just straight up not play the game as a result, as you often recommend them to do. A vast amount of players come to Battlefield to play a combined arms military shooter with the "appearance of realism without being a simulator" gameplay loop that Battlefield UNIQUELY offered as a middle ground in the market, but EA and DICE have abandoned that middle ground to trend chase other games. This is why it's annoying and there's so much complaining about things like movement and skins. You can continue to attack the caricature of a 0.5 KD player crouch walking to bolster your position, but you still can't define a well-reasoned upper limit for movement mechanics because you DON'T have a standard. An appeal to the skill gap is not a standard, and it does not define an upper limit for movement whatsoever. What then would be keeping DICE from adding wall running, double jumps, or even phasing through walls if it can be argued those could potentially take a vague amount of skill to perform? The bounds are defined by Battlefield's supposed authentic tone, which has been erased in favoring of emulating other games. If you just enjoy Battlefield's metamorphosis into a movement slop shooter like every other FPS out there, that's fine. We can disagree. Just don't expect the franchise to be anything more than a cheap, more plasticky Call of Duty substitute going forward.

  • AlaineF0922
    Alaine Ferreira (@AlaineF0922) reported

    @MAGAVoice You can't fix stupid and if anyone knows about this it is @GovSherrillNJ These morons are screaming for a medic like they are on a battlefield after someone was hit by a car, rightfully deserved. These stupid elected officials are craving national attention.

  • HonAbutoDave
    𝕄𝕒𝕤𝕔𝕦𝕝𝕚𝕟𝕚𝕥𝕪 ℝ𝕖𝕥𝕣𝕒𝕔𝕖𝕕 𝔸𝕓𝕦𝕥𝕠 (@HonAbutoDave) reported

    The irony is that the man now finds himself defending against accusations instead of solving the actual issue that existed. Asmall misunderstanding becomes a full emotional battlefield because emotional discipline was absent.

  • RodBuzetti
    Rodrigo Buzetti (@RodBuzetti) reported

    @BattlefieldComm This is the last Battlefield i ever play, we got so much better stuff with Hell Let Loose, Squad, Tarkov and now infantry coming to War Thunder. Fix the bugs and then talk about new maps and updates nobody asked for as a priority.

  • MEDIK861
    MEDIK86 (@MEDIK861) reported

    @Battlefield How bout you fix your game before you push more paid content why do I see glare when I get revived it's like your trying to piss us off

  • KillaRoy22
    NoLimitToSavagery (@KillaRoy22) reported

    @BattlefieldComm @Battlefield Fix the damn lighting issue!!!! Legit about to stop playing this ****!

  • BarrileroMunoz
    JABM (@BarrileroMunoz) reported

    @Battlefield Fix the brigness error....

  • QuSaYii
    Qusai (@QuSaYii) reported

    @BattlefieldComm When will the Middle East servers be working? We are currently experiencing issues with the European servers.

  • dipapip
    justinatime ☂️🇬🇧🇺🇦 (@dipapip) reported

    @NOELreports What's the point of it because putin will just string them along too! He doesn't want peace and until hes made to stop on the battlefield or financially broken 💩🇷🇺 then nothing can be done 🙄

  • researchUSAI
    U.S.A.I. 🇺🇸 (@researchUSAI) reported

    🇮🇷 The First Order Consequence: Iran’s Supreme Leader, after saying an enemy had been defeated on the battlefield, warned that attempts to undermine public resolve or spark pessimism would “directly aid the enemy,” signaling a push for tighter domestic information control and messaging to reduce frustration-driven unrest 🇮🇷 The Second Order Consequence: Iranian state-aligned authorities and media outlets would likely intensify monitoring and restrictions on dissenting commentary, while opposition figures and citizen networks could face higher risk of retaliation, contributing to reduced open debate but potentially faster alignment around official narratives, reflected in measurable trends such as fewer public protest announcements and fewer viral accounts documenting shortages or security incidents 🇮🇷 Discernment: Past instances of government crackdowns on criticism following battlefield or security milestones would likely be treated as evidence that fear and uncertainty suppress mobilization, shaping future strategy toward preempting pessimism rather than responding after public sentiment turns 🇮🇷 Reasoning: The Supreme Leader’s framing suggests a current focus on sustaining morale through state messaging, which may produce short-term stability measurable by lower reported street confrontations and fewer coordinated online calls to action, while also increasing long-term decay risks such as public distrust if official accounts diverge from daily conditions like inflation or service disruptions 🇮🇷 Judgement: The warning aims to preserve collective cohesion by discouraging frustration, but the approach risks trading openness for stability; group growth would be supported if public communication improves and grievances are addressed, while group decay would be supported by evidence like sustained reductions in credible, verifiable information and persistent reports of harassment that discourage participation in civic problem-solving

  • BlankpaperV
    Blank paper Ⓥ (@BlankpaperV) reported

    @pinkfilesss @nayana317668 @NawItsMaestro Lmao you won’t even view the ones on the battlefield the same as ice anyway lol so what’s your point the soldiers who fix the plane that bombs children are also culpable obviously the soldiers who provide logistics for the murder are obviously directly culpable

  • darklighter226
    On The Contrary (@darklighter226) reported

    @Battlefield Did they fix the bullet hit detection yet?

  • ustonymc
    ustonymc (@ustonymc) reported

    "Blazing Inferno" OMAHA BEACH June 6 1944 It took General Gerow's V Corps spearheads 3 hours to reach Omaha Beaches, and by then, most of the men had thrown up their breakfasts, all were drenched, and many were seasick, covered in puke and caked with salt. Gerow's soldiers were boated in darkness 12 miles from the beach, rather than 7 like the British. Even 7 was quite a distance for troops in LCVP's to travel, especially in choppy 10 knot seas off Omaha. But 12 in rough waters was a serious error of judgement. Omaha Beach gave a dreadful and deadly demonstration of Murpty's Law; all that can go wrong, will go wrong, at the wrong time. * In this sector, American bombers fearing to hit their own craft and troops had delayed their drop until the bombs crashed uselessly behind German defenders. * Here Rommel stationed the 352 Division, one of his finest. * Here too, the Germans held the strongest natural positions facing the entire Overlord assault; hills and cliffs rising steeply up to up to 200 feet from the beach and seawall above it. At Omaha was the largest concentration of enemy fire on the 60-mile invasion front. * Gerow loaded down his men with 90 pounds of gear. Even the best conditioned athletes in the world couldn't go careening around the battlefield for hours so encumbered. * Attempts to land artillery was a disaster, losing 26 guns. * 32 tanks were launched in heavy seas 3 1/2 miles out. Five reached the beach, and 27 sank like stones, drowning most of the crews. * Without tanks to take enemy fortifications under fire, the infantry had to storm the beaches themselves, flesh against fire. When the 5 tanks did arrive, they came behind, not in front of the 8 spearhead companies-1,450 soldiers in 36 landing craft. Heavy machine gun and mortar fire greeted these men as the waded ashore, many were wounded before they could reach dry land and had to struggle painfully up the beach heading for protection of the seawall. A wall of wrecked vehicles built up so quickly on the beach, soldiers were taking cover from scything German fire. One of them a soldier with a flamethrower took a direct hit to his fuel tank. The explosion catapulted his dying body into the sea and set a vessel on fire. A company of 270 specially trained demolition men followed the infantry ashore planning to blow up the boat obstacles before the tide covered them so that the following waves of 25,000 men and 4,000 vehicles might have an unimpeded path ashore, but German gunfire killed or wounded nearly half of them. Among the infantry huddled beneath the seawall or strewn among the debris, collapse of command followed quickly upon the destruction of communications HQ, which took a direct hit. Too many of the American Jr officers on Omaha that morning had been paralyzed by that same immobilizing dread that had come over their men. Offshore aboard the cruiser Augusta, Omar Bradley had his binoculars trained on Omaha Beach. The 1st Army commander anxiety deepened upon receipt of fragmentary reports suggesting disaster at Omaha. He was shocked at the loss of 27 tanks and 26 artillery guns lost. When V Corps reported at noon the situation, "still critical." Bradley considered diverting follow up forces to other sectors. Bradley realized that all depended on "that thin wet line of Khaki" that had struggled ashore and was so desperately clinging to its precious hold. Although the German defenders at Omaha possessed the power to impede or disorganize the American advance, they were neither numerous or strong enough to halt or destroy it. Throughout the battle they fought a static defensive fight. So, when the Americans gained ground or seized a toehold, they held it. The Germans never attempted to retake it. Like pieces being slowly fitted into a jigsaw puzzle, the Americans slowly expanded their hold. They were now fighting better and with more skill and better judgement. Now the battle experience of the 1st Infantry Division on the left began to have its effect. Small groups of soldiers from the "Big Red One" had begun to advance up the narrow valleys mounting local attacks against the Germans in their pillboxes and communication trenches. They fought their way onto high ground and began to hammer the Germans on their flanks. By their valor and rising momentum, they gave encouragement to the inexperienced and all but paralyzed 29th Infantry Division on their right. When General Norman "Dutch" Cota arrived on Omaha with his 29th Infantry command group he found chaos and paralysis. Cota moved among his dazed troops coming upon a group of pinned down Rangers, he asked who they were. "Rangers" came the reply. "Then goddamnit if you're Rangers, get up and lead the way!" Stung, they leaped ***** and began blasting paths through the German wire with bangalor torpedoes. The road at the top of the cliff was reached and the Americans had gotten behind some of the Germans strongest positions killing the enemy or taking him prisoner. When Cota found another group of Rangers apparently pinned down, he deliberately walked ahead of them to show there was no enemy fire. There was, but it didn't kill Cota. And because the Americans had such men-soldiers who didn't point the way but cried, "Follow me!" the near disaster that had been Omaha had been reversed. At 1:30 pm a vastly relieved Omar Bradley read Gerow's message, "Troops formally pinned down on beaches Easy Red, Easy Green, Fox Red advancing up heights beyond beaches." By nightfall the Americans controlled and area a mile deep beyond Omaha where the highest casualties occurred, 2,000-2,400 Americans were killed, wounded or missing.

  • xpertfusion3
    XpertFusion (AKA MovieFusion) (@xpertfusion3) reported

    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

  • BlackIceSheep
    🇬🇹(J.K.O.)🇲🇽 (@BlackIceSheep) reported

    @Voodoo_Hendrix "Battledads" are the safe fall guy catch all term for is ultimately a wider issue of the CoD brand trying desperately to appeal to other markets and not understanding that doesn't work. Battlefield and CoD should be different games but both EA and Activision just look foolish.

  • QuSaYii
    Qusai (@QuSaYii) reported

    @Battlefield When will the Middle East servers be working? We are currently experiencing issues with the European servers.

  • Spacers_Guild
    SpacersGuild (@Spacers_Guild) reported

    @ReforgeGaming Get tf outta here with your lies you wanna know how you can refute all of this??? BATTLEFIELD 6 if BATTLEFIELD 6 ran so smooth all because of the series S then its not the series S thats the issue its the devs who can't optimize for the hardware

  • AngelMOV25
    Mau Ortega (@AngelMOV25) reported

    @Battlefield And will the problem with the green notification dots not disappearing be fixed?

  • Time2splitters
    Time2split! (@Time2splitters) reported

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

  • buzzeyeview
    buzzeyeview (@buzzeyeview) reported

    @BattlefieldComm Update every two weeks it seems, I have update fatigue! Still not fixing the many issues BF6 has. What a joke!

  • RainbowNailGal
    Iam Thee (she/it) (@RainbowNailGal) reported

    @BattlefieldComm Bf 2042 is a forewarning of what "live service" is. Release a half *** game, you build "with the community" then after it's perfect, abandon it for the next title and don't support past titles whatsoever. At this point give me a new season in 2042 I'm over BF6

  • KeepYoHeadUppp
    M.D. (@KeepYoHeadUppp) reported

    @Battlefield fix your stupid ******* game!