Some of these guys are mostly correct about P2P.... but it is a bit different than it was in D1... the game depends more on cloud servicing than it has in the past. On consoles, no client has authority over another... they share data directly with each other over P2P, but the authoritative host is either in the cloud or Bungie itself in Bellevue, Washington. On PC the roles are more similar to D1, bit still split as well... one client is predicting/assuming some elements, but more critical elements are still ultimately managed by a server. If the elevated client assumed something that the server tracked differently, it can override the gamestate. Basically, you can have up to around 20 or so unique connections in play at once. Up to 11 will be other players, the rest are Bungie and cloud servers. Only a couple will be persistent (the ones to Bungie). The rest can change every time you queue an instance. Testing connectivity to one location (like a speed test run or something) is not going to give a good representation of what you are up against. Need to either be monitoring the data in real time as you are playing, or try to simulate a wide array of connections to various locations all in the same time frame. Run the latency test at testmy.net: https://testmy.net/latency Click the icon with the eye on it to run all the tests back to back. Watch what the line graphs are doing. If they are continually spiking really high and you keep getting high deviation numbers, then you may have a latency/jitter problem for your ISP to investigate. Each of the individual test graphs will note the address it tested, so you can look closer at that particular route (run traces and such)... sometimes a certain exchange point is a common denominator they can look at. There is another batch ping test you can run at dslreports.com for extra comparison as well: http://www.dslreports.com/tools/pingtest Yes, I know many of the test locations are a long way away and the core latency will be too high for the game... what you are testing for is the consistency of the latency. If there is too much jitter or packet loss, the game will boot you. Also need to make sure your local network is in line with Bungie's network guide: https://www.bungie.net/en/Support/Troubleshoot?oid=12915

When seeking help with networking issues, you can start with the network troubleshooting guide or you can provide the following info in your post so we can have an idea of where to start. -Internet provider -Modem/router brand -Download/upload speed(tested, not advertised) -Connection type(Hardwired/Wi-fi : Cable/DSL/Fibre/Satelite) -Ping/Latency -Packet loss -What steps you have already taken to try and aleviate your issues Network Troubleshooting Guide - [url]https://www.bungie.net/en/Support/Troubleshoot?oid=12915[/url] Restriction - This is for having a consistenly bad connection that has been reported by other players and confirmed by Bungie staff. The first is a warning, then two weeks, then two months, and finally a permanent restriction from all matchmade activities. Some sites for testing your connection. [url]https://www.speedtest.net[/url] [url]https://testmy.net/latency[/url] [url]http://www.dslreports.com/tools/pingtest[/url]

Hi Apollyon6949 Sounds like you are experiencing internet issues. The connection to Destiny 2 relies on a stable connection to the game. It's p2p. Your xbox acts as the server in a way. If you don't have a stable connection, you'll experience issues. Head to the test page in settings. There you'll see your upload/download, ping and latency after you run the test. I would also try resetting your router and xbox at the same time. Make sure you are using a wired connection too