2 of those errors (baboon and weasel) indicate packet loss. Thus, while your connection may be fairly quick, it is not stable. Destiny only requires a min 1 Mb up/down, so speed isn't usually a factor when dealing with the connection. Packet loss can occur due to many reasons (wifi interference, faulty wiring/hardware on your end or with your ISP, congested network hub along the route your connection has to take...just to name a few).
English
-
Thanks for responding, the issue should not be hardware. I am hardwired with CAT6 into an ASUS RT-AC88U wireless router that is connected to NetGear CM1000 modem. I work from home and got this setup as we should eventually go to gigbit in my area (300mb is what I'm paying for now). Can you or anyone else suggest anything else I can test other then detailed test on my xbox one, to see if the problem is with my ISP. Again, I'm not seeing major latency (24ms) and 0 packet loss.
-
Might not be on your end or Bungie's end. It could be all the connections in between.
-
Edited by dc213baseball: 6/13/2017 11:01:01 PMThe detailed network statistics feature on xb1 would probably be the most accurate, but it only gives a snapshot of the statistics at time of testing. There may be a site that I'm not familiar with that can track through xb1 to give an overall rundown of the network statistics while playing. Your isp should be able to track while playing as well. Also, does your router have a upnp setting to enable? If so, i believe that will be better than port forwarding...but I'm not 100% sure on this.
-
I do see some network performance apps on xbox, will look into that and UDNP - think I originally started the UDNP route but went with port forwarding and static IP as that was what Bungie suggested. Appreciate you suggestions.
-
Ok. Good luck. And it very well may not have anything to do with your setup/connection, it may be something wonky with your isp or anywhere else along the route. All you/I/we can do is make sure our own setup isnt the problem.
-
Sad but true