{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/19/2014 3:25:32 PM
4
Why I think the connection issues are with Bungie's servers
I have been playing destiny a lot since launch without any problems. Yesterday I began receiving the errors flatworm and beaver after making no changes to my network. The errors a first were stopping me from transitioning between zones but then got worse and I couldn't even make it to the tower.
I tried most if not all the troubleshooting methods available too.
First port forwarding, those Bungie specifies and the ones Sony recommends for the PS4.
I have always had a wired connection directly to the modem so no change there. (I have a hybrid modem router device)
I lowered and eventually disabled my firewall.
I finally gave the PS4 a static IP and put it in my DMZ.
None of these fixed the problem and since I wasn't having issues until now I can't help but think this is a Destiny server issue.
-
Ya I'm sure it's them. I have it for both ps4 and xbox360. Ps4 works fine, xbox doesn't last at all. Get caterpillar every time. Both systems use the same internet. Even did all the tweeks for the 360, port forwarding, static ip and other things that iv seen people say that works. Nothing for me. Today even worse. I guess at least it works on my ps4. Unfortunately all my friends are on 360.
-
I think the problem is on their side also, their servers are VERY sensitive, if you are playing on a 30mbps connection and it drops to 20mbps, you will disconnect Try this: https://www.bungie.net/pt/Forum/Post/69790738/0/0
-
2 通の返信ToBadImNotCleverにより編集済み: 9/19/2014 5:41:25 PMStill having the same issue here. It's rendered the game unplayable for me. I forwarded my ports. Gave my PS4 a static IP. Everything. Hasn't changed a single thing. Completely unable to access the tower and get booted from earth regularly. I'm pretty fed up with it at this point. EDIT: To clarify, Beaver error's every single time.
