{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/8/2024 5:42:10 PM
7
Hi there, Thanks for reporting.
The team is already aware of this issue and it seems to be caused by the local ISP in your area and not on Bungie's end.
English
-
Hi. Thank you for your efforts but I have to say that this only happened right after the guardian games update and our ISP says they didn't block anything during that time. Also I tried different ISPs here since I move back and forth between two different cities. Still no help. Lastly I have to add we don't have a problem of this sort with any other games and it's very unlikely they just block destiny 2 servers right during that time.
-
Bearbeitet von Cloud: 3/12/2024 10:04:42 PM@BNGHelp10 it can't be ISP, if it was ISP, it would have completely dropped the connection to your servers, which will result in nightingale or centipede error, as I've saw in network monitors, connection is made to your server, then from the reply content game shows tapir error. Also, only signing in steps checks for IP, if I use VPN on this step, I can successfully connect to game directly after that(the one connection which is always open on port 7500 and its disconnection will result in weasel error, could be connected directly) so the connection to your servers are not blocked, it's something on your end(or maybe your third party services like playfabapi,...)
-
its not the isp. everyone with different isps are having this issue which didnt exist before the update
-
Hello there The problem still remains. I'm not sure you're aware that Bungie blocked Iran IPs to access the website, store and even 3rd party apps. Right now I'm replying to your comment using a VPN. So that's not an ISP issue. Please don't deny a big community to access the game.
-
Bearbeitet von BlinkBlade: 3/9/2024 5:39:37 PMits not ISP, its bungie ever since the Guardian games update, the game worked fine just moments before update as i was playing, i also tried with multiple ISPs, and it seems bungie is blocking Ports and some IPs
-
Thanks for your time ISP and all the connection modifications are the same as last week and last month and last year. Before I attempt to bother you, l'd checked with them at first, but all testings show it's all good. Ironically I logged in to D1 and everything PvP and PvE looked good. Only destiny 2...
-
true. its the same for me.
