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
La Trinité, Martinique 1
Lyon, Auvergne-Rhône-Alpes 10
Persan, Île-de-France 1
Metz, ACAL 3
Aubais, Occitanie 1
Toulouse, Occitanie 5
Seysses, Occitanie 1
Annecy, Auvergne-Rhône-Alpes 3
Colmar, ACAL 1
Les Sables-d'Olonne, Pays de la Loire 1
Chantonnay, Pays de la Loire 2
Paris, Île-de-France 38
Pringy, Île-de-France 1
Santiago de Querétaro, QUE 1
Duque de Caxias, RJ 1
Parmilieu, Auvergne-Rhône-Alpes 1
Amiens, Hauts-de-France 2
Rouen, Normandy 1
Vienne, Auvergne-Rhône-Alpes 1
Pontoise, Île-de-France 2
Asnières-sur-Seine, Île-de-France 1
Madrid, Madrid 4
Arrondissement de Charleroi, Wallonia 1
Santa Cruz de la Palma, Canary Islands 1
Rennes, Brittany 2
Caxias do Sul, RS 1
Saint-Lubin-des-Joncherets, Centre 1
Aubenas, Auvergne-Rhône-Alpes 2
Annonay, Auvergne-Rhône-Alpes 1
Cruseilles, Auvergne-Rhône-Alpes 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:

  • H_Voice3
    VOH (English) (@H_Voice3) reported

    Former Interior Minister Mohammad Omar Daudzai During Republic: The So-Called Anti-Government Fronts Cannot Be an Alternative for Afghanistan; I Also Oppose the Resumption of War Former Interior Minister during the previous Republic, Mohammad Omar Daudzai, said that the activities of the so-called anti-government fronts cannot provide an alternative for Afghanistan, adding that any war backed by foreign support is not a solution to the country's problems but rather a cause of further disasters. Daudzai stressed that he personally opposes military confrontation and war against the Afghan government. He added that Afghanistan can no longer endure conflict and that armed warfare must not be reignited in the country. According to him, military opposition to the Afghan government is extremely difficult because the government exercises full control within Afghanistan and responds forcefully to any armed resistance. He said that, in the past, these groups were not given space to operate even in neighboring countries, but recently there have been signs that some neighboring states have provided them with an environment in which to resume their activities, leading to their renewed operations. Mohammad Omar Daudzai also stated that Pakistan's military establishment has recently become interested in seeing Afghanistan destabilized due to its deepening disagreements with the Afghan government. He further added that although the leaders of the so-called anti-government fronts are based in Western countries, he believes that Western governments do not seek to turn Afghanistan into a battlefield once again and are unlikely to provide these groups with military support.

  • Djaym0
    Daryn Modien🪶 🇨🇦 (@Djaym0) reported

    @Battlefield @BattlefieldComm my dudes. PLEASE FIX THE BACKING OUT OF GAME BLACK SCREEN CRASH. its been there since beta. come on now. tired of having to relaunch my game 10 times a session. #Battlefield6

  • iranopessimist
    adelvafa (@iranopessimist) reported

    @calvinfroedge This is obviously an out-of-reach upper limit that Iran is using as a starting position. Negotiations will whittle this down into something more realistic, provided the issue is settled on the battlefield.

  • Rottweiler_Red9
    ROTTWEILER_RED95 (@Rottweiler_Red9) reported

    @Battlefield @BattlefieldComm @EA_DICE When Rush was brought back, to BF6 it came with two promisses. 1) Rush was here to stay 2) Rush was returning to it's 12v12 roots. Both of these promisses have been broken. I bought BF 2042 under the promisse that Rush would always be available in Portal...

  • _iKrasnov
    iKrasnov (@_iKrasnov) reported

    Do you know who is going to listen to DICE? Well, people like him certainly don't. Most of these problems make Battlefield 6 boring and disgusting so I am with him 100% in everything he has written here.

  • nmlinguaphile
    WindTalker (@nmlinguaphile) reported

    Most people only know about the Navajo Code Talkers, but the story actually starts much earlier—and involves a lot more tribes than most people realize. In the final months of World War I, the U.S. Army in France was getting hammered by German interception of their communications. Runners were being captured or killed, phone lines tapped, codes broken. Then some officers overheard a handful of Choctaw soldiers from Oklahoma talking among themselves in their own language. That gave them an idea. In October 1918, during the Meuse-Argonne offensive, a group of Choctaw men from the 36th Division became the first official code talkers. They started sending battlefield messages over the field telephones in Choctaw. The Germans couldn’t make sense of it. Other tribes were pulled in around the same time—Cherokee, Cheyenne, Comanche, Osage, Yankton Sioux, and even some Ho-Chunk. It was mostly Type 2 code talking (just speaking the language straight), though the Choctaws developed a few coded terms too. It worked so well that the idea stuck. When World War II came around, the military remembered. This time they got more organized about it. The Army started recruiting early. In late 1940 they brought in 17 Comanche men who developed a formal coded vocabulary of around 250 terms—tanks became “turtles,” machine guns became “sewing machine guns,” and Hitler got the name “Crazy White Man.” Thirteen of those Comanches landed on Utah Beach on D-Day with the 4th Infantry Division and fought all the way across Europe. The code was never broken. Around the same time, the Army also used Meskwaki (Sac and Fox), Chippewa and Oneida speakers, Hopi, and others in smaller groups. Then came the Marines and the Navajo. In 1942, Philip Johnston (who’d grown up around the Navajo) convinced the Corps that the language could work. They brought in the first 29 Navajo recruits—the “Original 29”—who built a sophisticated code with hundreds of terms (eventually over 600). Fighter planes were hummingbirds, bombers were buzzards, submarines were iron fish. By the end of the war, somewhere around 400 Navajo had been trained as code talkers, and they served in every major Marine campaign in the Pacific. At Iwo Jima, one Marine officer famously said the island wouldn’t have been taken without them. Other tribes whose languages were used in WWII include Kiowa, Creek (Muscogee), Seminole, Pawnee, Crow, Assiniboine, Lakota and Dakota Sioux, Menominee, and more. In total, more than 30 Native nations contributed code talkers across both wars. After World War II the need faded fast. Modern encryption technology made spoken language codes less necessary. A few Navajo code talkers did some training exercises after the war, and some individuals served in Korea and Vietnam, but the formal programs effectively ended by the early 1950s. The irony isn’t lost on anyone: these men were asked to use the very languages that boarding schools had tried to beat out of them—and those same languages helped win two world wars. The codes were never broken. Pretty remarkable chapter of American history that still doesn’t get talked about enough outside the Navajo story.

  • LetsArmUKR
    medoyid_ua (@LetsArmUKR) reported

    Zaluzhny just said out loud what Ukrainian soldiers and civilians have been muttering for years: NATO is never taking us in as long as the current lineup of members exists. Twelve years of war and the message is clear. The Alliance will only extend the invitation once Moscovia is no longer a threat. But by then the whole point of joining collapses. If the empire is finished as a military problem, Article 5 becomes a historical footnote rather than a shield we actually need. What Ukraine requires is not another round of performative "irreversible path" rhetoric that sounds like samurai philosophy with no destination. We need concrete partnerships that deliver anti-ballistic systems, deep-strike aviation, real-time intelligence, and joint weapons production right now. And guess what? That is already happening outside the NATO tent with Britain, the Baltics, Scandinavia, Germany, France. Those deals move faster because they skip the endless consensus process. It is time to stop pretending the 32-member debating club is the only legitimate security architecture. Ukraine should lead the creation of a smaller, sharper bloc built for 21st-century war: states ready to sign binding military commitments, pre-plan joint defense, co-produce next-gen drones and missiles, and actually shoot back on day one instead of issuing another strongly worded statement after the third city is leveled. Zaluzhny is right. Declarations are cheap. New coalitions with real teeth are not. Kyiv needs to stop waiting for permission slips from hesitant capitals and start founding the security architecture that matches the battlefield reality we have already paid for in blood. The old structures failed the test. Time to build the ones that will not.

  • web3journal23
    Web3 Journal ✦ (@web3journal23) reported

    @gorgeous4ew The debt load from the JPMorgan financing is the part that stands out most — EA will have to service around $18 billion in new obligations, which almost guarantees aggressive cost discipline that could reshape how long the next Battlefield or Sims cycles take.

  • OhmanEU
    Ohman (@OhmanEU) reported

    @GhostGamingG Anyone who says skill issue is just engagement baiting I swear, this is insanely unhealthy for a game like battlefield

  • DuckTheIrishman
    ヨルダンプロバンス (Jordan Provencial) (@DuckTheIrishman) reported

    @BattlefieldComm Gotta fix the broken grenade indicator. The game straight up doesn't show them and it leads to so many avoidable death.

  • ChibRisky
    Daimeon Kennedy 𓃵 (@ChibRisky) reported

    @Aji_ben72 Even with the comet, Aang is still the biggest problem on that battlefield

  • lakewoodxlegend
    Ju. (@lakewoodxlegend) reported

    @BattlefieldComm Conquest is broken the score won’t move at all

  • TechaGek
    techagek (@TechaGek) reported

    @MrProWestie @StodehTV @BattlefieldComm Had bot lobbies one after another the other night at the weekend consistently, and even found my way in to an NA lobby somehow (I'm UK). It took a full 10 minutes to fill a TDM lobby that I thought I'd give a try, I'm convinced the matchmaker is just another thing that is broken.

  • DennizDream
    D̷R̷E̷A̷M̷E̷R̷ (@DennizDream) reported

    @_iamhabeeb Poverty isn’t always a lack of effort; sometimes it’s a system designed with broken ladders. Blaming victims is easier than fixing the battlefield they entered.

  • BodySumit81060
    Sumit Bishnoi (@BodySumit81060) reported

    @ndtv Parliament isn't a battlefield for egos—it's where the nation's problems should be solved. India deserves debate, not deadlock. 🇮🇳

Check Current Status