Renegades update has been plagued with the above codes since release. Definitely not a problem with my ip or router. Spend some money on better servers instead of cars bungle….
-
1 ReplyHi there, Thanks for reaching out! Error code: BABOON is a general networking error, and is automatically reported to us when it occurs. Please see our guide below for details and troubleshooting about this error code: https://help.bungie.net/hc/en-us/articles/360049195151-Error-Code-BABOON If you continue seeing this error, or the WEASEL error, we recommend you refer to our Network Troubleshooting Guide to explore potential solutions to your problem: https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide
-
Destiny 2: Return of the [b]BABOON.[/b] [i]Bungie is actively tracking this general networking error. Your disconnect was reported the moment it occurred[/i]. [b]What an utter load of bull dust[/b]. [quote]Pinging bungie.net [104.17.100.21] with 32 bytes of data: Reply from 104.17.100.21: bytes=32 time=2ms TTL=59 Reply from 104.17.100.21: bytes=32 time=2ms TTL=59 Reply from 104.17.100.21: bytes=32 time=2ms TTL=59 Reply from 104.17.100.21: bytes=32 time=3ms TTL=59 Ping statistics for 104.17.100.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 3ms, Average = 2ms[/quote] [quote]Tracing route to bungie.net [104.17.100.21] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 2 ms 2 ms 2 ms ndcm1-bng1.vic.leaptel.network [172.31.0.36] 3 1 ms 2 ms 1 ms 172.31.1.70 4 3 ms 3 ms 2 ms 162.158.0.22 5 3 ms * 33 ms 162.158.0.12 6 2 ms 2 ms 2 ms 104.17.100.21 Trace complete.[/quote] [b]NBN [/b]= Australia's National Broadband Network shows no issues. My [b]ISP [/b]also shows no issues on their side of network. Only conclusion is the [b]mix of peer-to-peer (P2P)[/b] connections for gameplay and some server-side handling for matchmaking, which makes network stability crucial. Is absolute garbage and needs to be abandoned.