Around noon central standard time i started getting the error codes. Power cycled everything, bo luck. Tried changing things around on my router, no luck. Tried changing my router, no luck. I have no clue whats wrong with this situation. I can play BL3 amd Remnant no problems. After 4 hours of struggling it finally started just saying Destiny 2 servers could not be reached. Someone be my hero. I have deleted the game amd now im reinstalling it. Hoping beyo d a hope it fixes the problem.
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
What is the make and model of your modem and who is your ISP? Does your ISP provide you phone service (VOIP) with your internet services?
由Hoax1331編輯： 11/19/2019 12:31:59 PMI have the exact same problem as you, however on XBOX ONE. I have done all the steps you have also done, now I am requesting a port release on my ISP and I will see if it will resolve. If so, I'll be back here to tell you. I am also waiting for a new update in Destiny 2 that maybe can also fix this, because by my research this error is fixed and has problems again in the future.