I've been experiencing this issue for two days straight now, and i've already done literally every troubleshooting method used in every forum i could find both on Bungie's forums, as well as many other third part forums.
I attempt to sign in and after about 30 seconds or so, i get an "attention" message stating that the Destiny 2 servers are unavailable. After about 2-3 hours of waiting to see if it changes, i get a new message saying i've been signed out of Destiny 2 for inactivity.
Important things to note are that I've not had the chance to even get to the character creation screen. My specs are well above the minimum requirements for this game. I've gone as far as uninstalling and reinstalling everything from the game to my graphics drivers. I played in the beta with zero issues, not even any disconnects.
I'm trying to get in contact with anyone who can help fix or troubleshoot this issue.
Edit 1: I was able to find a fix that i hadn't seen on any of the forums, or on Reddit.
(these instructions are for Windows 10 users)
> Right click your network icon
> open the Network and Sharing Center
> go to "Change Adapter Settings"
> right click your network (either Ethernet or wireless)
> properties
> select without checking the box "Internet Protocol Version 4 (TCP/IPv4)"
> click on the "properties" button
> make sure the "obtain an IP address automatically" and the "obtain DNS server address automatically" radio buttons are both checked, and then hit "ok".
> repeat the previous two steps for "Internet Protocol Version 6 (TCP/IPv6)" as well.
After accomplishing both of these things (and restarting my computer for good measure) i was able to resolve my issue and have been playing the game flawlessly. From what i understand, this has to do with DSN servers not responding. i followed the instructions in the link below to correct my issue. Hope this helps you guys out!
https://support.microsoft.com/en-us/help/2779064/-your-computer-appears-to-be-correctly-configured--but-the-device-or-r
-
Just wanted to say thanks a million! This is exactly what was happening for me. I had set static IP and DNS to play some LAN doom a while back, never would have found this as the issue.