{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Lord Saladinnerplateにより編集済み:
9/26/2022 2:37:11 PM
13
Incessant "bee" and "anteater" errors
Today only, I've been getting a ridiculous number of Bee and Anteater errors. The odd part is, I get the error only between rounds of PvP, then I load back into the next round. After about five seconds, I get booted with a "bat" error code.
I played Friday briefly with zero issues, and have never had problems with errors kicking me until today. My network is the same as it has been, and all tests on my end are coming up clean as a whistle. Other games function fine.
Anybody else having this issue, and anybody having luck with workarounds? I wanted the adept bow but I won't be able to if I get tossed out every other match or more often.
Again, *NEVER* had this issue before now. Didn't change settings at home. Everything works fine everywhere but D2. Got my first "quitter timeout" in years today because of it. Also of note, I play on PC.
-
15 通の返信Hi there, Thanks for reaching out. What region are you playing out of? We are currently tracking increases in BEE, ANTEATER, and WEASEL errors out of certain ISPs over the weekend. Please also refer to our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]network guide[/url], [url=https://www.bungie.net/en/Support/Troubleshoot?oid=13603]optimization guide[/url], and [url=https://www.bungie.net/en/Support/Troubleshoot?oid=13610]advanced troubleshooting[/url] for assistance on minimizing connection issues and best optimizing your connection to Destiny 2.
-
This same exact thing happened to me multiple times yesterday. Couldn't even play trials. Would get to 3 wins and it would happen. It's a little pathetic they can't get the bugs out of this game. Every patch they do creates 5 more problems
-
Same thing since Friday night. On strike playlists and such, I get black screened with bee, and load back in. In trials I get black screened on the end of round with bee, then load into the round for about 5 seconds before bat gets me. Everything is fine with my stuff here at home. Internet checks out, all other games are fine. It's only D2.
-
1 返信
-
1 返信Ive been kicked with wrror code bee every 5 or 10 minutes for 2 days straight making playing impossible its so bad i got quitter penalty from trials and didnt quit one game error code every time so im being penalized for bungies poor servers and my internet has been good over 200mbps on lan entire time even in pve i get kicked and bee or bat guess wont get the bow or anything done bc bungies killed their servers
-
Wolverine101により編集済み: 9/27/2022 9:43:44 PMReporting the same issues here in TN as well. Middle TN and it is getting very annoying. Tried fixing my DNS settings and that only caused more issues. Constant BEE and ANTEATER errors on 600 mbps down. It's NOT my internet. I am hardwired Also on Xfinity
-
You aren’t alone. Happened to me until I got suspended. Went back a few hours later for it to happen again and get suspended longer. Frustrating af if I’m being honest that it’s been about 24 hours now for myself and still no peep from bungo.
-
1 返信HolyChewbeccaにより編集済み: 9/26/2022 8:47:49 PMSame here! Perfect internet connection and keep getting booted with anteater and then bee. Then put in timeout due to "leaving games" that I was booted from. Also lots of contacting servers now that the time out is over.
-
Update: Using a VPN server in a region outside those mentioned regarding this issue seems to have solved it. Must be a bad node somewhere in those regions that's messing with our traffic. A couple matches as well as some PvE due to a timeout later with the VPN and so far no issues, not even "contacting servers" messages.
