Platform: Steam (though have seen others report it on Xbox and Playstation) Issue: Game will intermittently show "Contacting Destiny 2 Servers" when performing certain actions, listed in Steps to Reproduce, when the action doesn't go through immediately. System Info: CPU: i7-10700K GPU: MSI 3080 Ti OS: Windows 10 ISP: Spectrum, wired connection to router Steps to Reproduce: 1. Login to your character 2. Navigate to your Character screen (viewing your weapons/armor on character) 3. Attempt the following: A. Applying a mod to armor or weapons B. Applying a shader to armor or weapons C. Swapping equipped armor or weapons D. Changing pre-set Loadouts (not the weasel error issue that is from finisher mods) (Alternate Steps to reproduce from other areas with similar behavior) A. Clicking on a bounty to complete it B. Clicking to claim a reward from a vendor C. Traveling via fast-travel D. Traveling from one world area to another (including entering/leaving a lost sector) Expected Behavior: The mod is applied, shader equipped, armor/weapon swap occurs, Loadout change occurs, bounty is completed, reward/purchase received, travel occurs normally. Actual Behavior: A. The mod/shader/(armor/weapon)/loadout change/swap does not occur immediately, slot for the above can appear blank for 3-5 seconds. Following this, "Contacting Destiny 2 Servers" will appear on screen and the action will go through usually the instant this appears. B. For bounty completion, bounty will have the animation play halfway before freezing in place for a moment, same with rewards from vendors. C. Travel will have this happen shortly before seeing the text in the lower left corner for the new area, or after being on the black screen with class symbols in lower right for about 5 seconds before the message appears. Links: The following are other reports of this behavior happening over time. Post that contains Video of the behavior: https://www.bungie.net/en/Forums/Post/262160964?sort=0&page=0 https://www.bungie.net/en/Forums/Post/262157430?sort=0&page=0 https://www.bungie.net/en/Forums/Post/262182339?sort=0&page=0 https://www.bungie.net/en/Forums/Post/262219510?sort=0&page=0 https://www.bungie.net/en/Forums/Post/262370987?sort=0&page=0 https://www.bungie.net/en/Forums/Post/262582207?sort=0&page=0 https://www.bungie.net/en/Forums/Post/262625377?sort=0&page=0 https://www.bungie.net/en/Forums/Post/262645839?sort=0&page=0 ^ This last post was co-opted by replies for a server issue on that day, but the OP confirmed their issue was not the server problem of the day but an ongoing issue. I made this post a while back, including it just for completeness: https://www.bungie.net/en/Forums/Post/262099988?sort=0&page=0 Notes: This issue is not persistent, meaning it cannot be replicated every time (depending on the person experiencing the issue). It seems to have times when every action will result in "Contacting Destiny 2 Servers" appearing, and other times when you can do any of the above mentioned actions and not have it replicate. I've seen reports of this both here on the forums, on Twitter (searching for Contacting Destiny 2 Servers) and on a few subreddits. Not linking to those as I'm uncertain on the rules for linking outside of the forums for non image/video links. In the course of this behavior happening since the 30th anniversary update for me, I have checked the following things when it is occurring: 1. If this is an issue with too much usage during peak hours in my area. Behavior occurs regardless of time of day, can be during peak hours or in the middle of the day/night. 2. Checking for reduction in internet speed/jitter/packet loss. My bandwidth both up and down remain consistent, with 0 packet loss or late packets and low jitter. This is testing against servers in Seattle, not local servers as I'd expect a stronger connection locally than across half the country. 3. Reviewed the connections guide Bungie has provided. I have tried enabling UPnP, port forwarding (these two both at the same time and separately), changing my DNS and flushing it. 4. I have ensured that my antivirus is not affecting the game. I have at different times removed my antivirus, ensured that the entire Steam folder for Destiny 2 is excluded from everything and the same for Battleye. 5. Monitored the in-game connection bar on the roster when behavior is occurring. Connection bar never wavers from being full when this happens, and friends in-fireteam and not confirm that I don't seem to be lagging when it happens. 6. Contacted my ISP to see if they detect anything happening, got lucky and replicated the behavior once while on the phone with them. They state that from their examining of my traffic that nothing is being blocked on my end, and they weren't detecting anything abnormal about my connection. All of the above have been checked/tested and the behavior continues to occur separately and with combinations of testing. Thoughts: From everything that I've tested and reviewed over the past year+ (started just after the 30th anniversary update and has slowly gotten worse over time), it seems like there is some problem that can occur when the game is making a call to the servers that maintain player inventory and/or player location for planetary instance (for the travel replications). The game will idle with that action for a few moments, then reattempt it which is when "Contacting Destiny 2 Servers" appears. That reattempt succeeds which is why the action goes through normally the instant the message appears. (I say normally as the worst time it ever happened it took about 3 seconds after the message appeared for the mod to be applied). I'd also like to note that aside from times when there is widespread issues with the game/servers I do not receive this message nor any error codes. Getting this message has not ever led to any error code, the action simply takes long enough to go through that it does a reattempt. Also, and this could just be random chance that it happened. When the problem with the Steam datagram relay was fixed by Valve the issue seemed to not happen for about a week. Could be that the issue is somehow involved with that, or like I said just random chance that I didn't encounter it in that timeframe. Lastly, this does not have any correlation with the problems that happened today (June 6th, 2023). Had been seeing this more lately and was going to post in this forum earlier today but waited because of those problems. And my apologies for the long bug report, I've had this happening for a while and wanted to detail things as best I could.