Destiny 2 down? Current status, problems and outages

Problems in the last 24 hours

The graph below depicts the number of Destiny 2 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 Destiny 2 users through our website.

• Sign in (81%)
• Online Play (9%)
• Glitches (4%)
• Hacking / Cheating (3%)
• Game Crash (3%)
• Matchmaking (1%)

Live Outage Map

The most recent Destiny 2 outage reports came from the following cities:

City	Problem Type	Report Time
Port Talbot	Online Play	4 days ago
Nouméa	Online Play	13 days ago
Wadsworth	Sign in	13 days ago
Ashburn	Sign in	13 days ago
Brisbane	Sign in	14 days ago
Cannes	Online Play	14 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.

Destiny 2 Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Sebastian Lewandowski (@RealNrxb) reported 7 minutes ago

  @TrueVoltz @mattplotner @BungieHelp Okay stop crying then. I’m sorry that you most likely glided through the raid with barely any error codes

• 
  Resonosity (@resonosity) reported 14 minutes ago

  @TazlynnQ @TheRealMutewalk @DestinyTheGame Wrong. A lot of people kept getting Guitar and Anteater error codes towards the beginning of the raid because increased "entities" (i.e. orbs, wells, etc.) were too much for the game's engine. No cheating was taking place. Watch what you claim.

• 
  Kratos (@GhostOfSparta1_) reported 17 minutes ago

  @OfficialXboxU That’s EXACTLY what I’ve been trying to tell people! This is 343’s first ever live service game and needs a lot of work, but look at how Bungie started with Destiny. Destiny was bland and had very little content and now look at it. Halo will be perfectly fine

• 
  Tony (@excited_panda10) reported 18 minutes ago

  @DestinyTheGame My question is, how many of the teams who had error code problems also had team members who glitched into the raid early and previously got guitars days ago? Punishments should be given to those who try to cheat and cheese.

• 
  Sykes (@Sykesee) reported 19 minutes ago

  @SiggiRiggi @DestinyTheGame I had the same issue, what's the native resolution of the monitor, I changed the games res to that and it sorted it right out

• 
  Sebastian Lewandowski (@RealNrxb) reported 20 minutes ago

  @KNoals @BungieHelp Yeah critically thinking is gonna work so well coding wise mhm. You do realise the teams already been put under pressure for the error codes. So why would they go out of their way to add another mode for just 24 hours

• 
  Max (@BrokeCommies) reported 21 minutes ago

  @stonesandsnakes @DestinyTheGame Wait until all the error codes, the blm emblems and sjw nonsense and it'll drop back to 10k

• 
  Sebastian Lewandowski (@RealNrxb) reported 22 minutes ago

  @The_Squatso @BungieHelp What about all the people who cancelled plans today but can’t play the game due to error codes

• 
  Dylan (@VIIIFears) reported 24 minutes ago

  @BungieHelp im running into an issue with the cross save feature and need help because i made an error and now i i cant do anything for 6 months

• 
  🍂NTC WarStarNinja🍂 (@thawarstarninja) reported 26 minutes ago

  Really frustrating to deal with lag every time I stream or just Destiny servers todays

• 
  Max (@BrokeCommies) reported 28 minutes ago

  @pierredemery @DestinyTheGame @Bungie Amazing watching the servers Biden built keep producing errors, LGB !

• 
  Kanishk Singh (@gon2thegallows) reported 32 minutes ago

  @BungieHelp Please look into CALABRESE error as well

• 
  Barrett Rayan (@Punk_ROC) reported 33 minutes ago

  @An_Illusionist @PorterShogren @DestinyTheGame Imagine thinking this race was fair at all. Some teams definitely got more errors than others. That is just a fact

• 
  Ren Althea (@RenAlthea2) reported 37 minutes ago

  @DestinyTheGame how the f* bungie fix this now?

• 
  ThePopFather (@joshprice78) reported 38 minutes ago

  @TheRealMutewalk @DestinyTheGame Mute we nvr had one issue we r streaming on 3rd encounter so no not everyone having issues

• 
  Hoggy077 (@Hoggy077) reported 39 minutes ago

  @TheRealMutewalk @DestinyTheGame This has to be one of the most idiotic & paranoid things ever. "Oh no, server instability! WF didn't have issues, but I did and others are so they MUST be cheating, MUST BE! Bungies out to get me and my teams and all those other players!"

• 
  GodUsopp (@PorterShogren) reported 39 minutes ago

  @xxthexjacobxx @TevesTV @DestinyTheGame Because everyone had bugs and error codes…

• 
  Tim👀 (@TheTim04) reported 40 minutes ago

  @TazlynnQ @TheRealMutewalk @DestinyTheGame stop talking ****, we also got much error codes without cheating

• 
  Savvy (@ThenamesSavvyy) reported 41 minutes ago

  @TheDantastic1 @Levious_Dick @BungieHelp Wow you sound quite mad over such a tiny problem

• 
  Svart (@SvartUlfer) reported 42 minutes ago

  @DavidC09225476 @xxjennyxxa @DestinyTheGame I guess the question is, did they use their own cp after a disconnection. I know my team did that once. If so, I don't see an issue. If they earned the cp & used it to start where they were booted from, what's the issue?

• 
  uno puch mon (@mastoid45) reported 43 minutes ago

  @Ghawk2412 @BungieHelp You do realize that there were people being kicked because of error codes. It held back multiple teams for hours since they got kicked everytime

• 
  Sebastian Lewandowski (@RealNrxb) reported 45 minutes ago

  @jiakaice @BungieHelp No because it’s completely unfair on the people who had been error coded the whole time

• 
  Tazlynn (@TazlynnQ) reported 49 minutes ago

  @lilparadoxv3 @TheRealMutewalk @DestinyTheGame I mean if your confident in your entire fire team not cheating then it's just connection error. I said "probably" not factually, it was more of a suggestion. Seeing as bungie stated they took extra precautions to block anyone using cheating site's for the raid

• 
  madge (@StalkerPepega) reported 50 minutes ago

  @TazlynnQ @TheRealMutewalk @DestinyTheGame Wtf u talking about there were massive problems with it

• 
  Jacob Thomas (@JacobTh29429437) reported 52 minutes ago

  @BungieHelp I'm on ps4 and have not been able to play D2 for a week, anytime i try and open the game I get the error code MARMOT, I've tried uninstalling and reinstalling the app, but still wont work. any tips?

• 
  Yamainboi (@Yamainboi3) reported 55 minutes ago

  @prof_hardscope @foulta_Xbox @BungieHelp Money issue

• 
  Sebastian Lewandowski (@RealNrxb) reported 55 minutes ago

  @MinatoN91617112 @BungieHelp Awww boohooo you’re too **** to complete the contest mode and now you’re complaining while majority of the community has to sit and suffer error codes back to back

• 
  martyn george (@Rainbow_Dargon) reported 58 minutes ago

  @TheRealMutewalk @DestinyTheGame Anteater errors were caused by the volatile flow artifact mod

• 
  uno puch mon (@mastoid45) reported 59 minutes ago

  @TypikalSpike @BungieHelp Anteater error codes plagued the race for hours, not allowing some people to even get past first encounter

• 
  Jessica Heggie (@JessicaRMyers) reported 1 hour ago

  @DestinyTheGame My team ran for almost 6 hours and we only got an error code once…. The server actually seems to hold out more than in the past