I have to be honest with you, Bungie. I used to have every single error codes from Anteater to Zebra, but the last patch that came out last week seemed to manage to fix all those issues and I haven't had a single disconnection until today, when I literally can't play for more than 3 minutes without being disconnected with the BABOON error, the Bee or the Weasel. I thought those hard times were behind our back, weren't they Bungie? I didn't change a thing from the day the last patch was released, so I believe this has to be a problem on your end. That said, I'll report some specifics of my current setup:
- I got all the required port forwarded and properly triggered on my router.
- I use a wired connection.
- I have 0 packet loss, 1% jitter and 57 ping.
- I'm on a XBOX ONE.
- My xbox live account is good and working.
- The ip on my XBOX is getting the 90% of my Connection thanks to a properly set QoS. No other device can interfere with my Live connection.
- I run a Speedtest a day to check my connection status, and today it appears to be good.
Why am I experiencing this horrible deja vu again? Is anybody else experiencing this same problem as for today?
-
2 RepliesEdited by Dirtdiver: 11/4/2014 12:47:00 AMI was having the same issue. I have a static IP, port forwarding and 0% packet loss on my 360 but was still getting zebra/weasel, bee, anteater and occasionally marionberry. It helped some when I added my console to DMZ on my router. Now I only get weasel but I am getting it every time I play crucible or anytime I go to the tower in a fire team. I occasionally get weasel when I am alone at the tower but it might help you more than me. Good luck with it. Luckily COD is out so I'll have something good to play now until Bungie fixes this mess.