JavaScript is required to use Bungie.net

Help

Help us help you.
6/8/2023 6:34:29 AM
2

code weasel loop after 2023-06-08 (SGT timezone) maintenance start

Hi, after the today maintenance start, i get weasel code in loop, sometimes after the character selection, sometimes before. loop goes like that : Press Return to play screen -> queue screen -> weasel -> Press Return to play screen Press Return to play screen -> queue screen -> character selection screen -> weasel -> Press Return to play screen got basically 70% queue -> weasel and 30% character selection -> weasel to be honest, my network is working fine, not using wifi, pure ethernet cabling up to the ISP router. good luck troubleshooting, hope you nail it down :)

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • 4
    Hi Im Swat
    Hi Im Swat

    Bungie fan. Been here for 16years! - old

    Bungie is fully aware players are unable to log into Destiny 2 and they are investigating. For the latest service alerts make sure to follow [url=http://twitter.com/Bungiehelp]@BungieHelp[/url] on Twitter. You do not need to create a Twitter account to see their Tweets. [quote]We are continuing to investigate sign on issues for Destiny 2. Please stand by for updates https://twitter.com/BungieHelp/status/1666710115213533184 [/quote]

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • okay, after digging a bit more here's some more info . following the IP Blocks assigned to bungie from that post : https://www.bungie.net/en/Forums/Post/248879896 and doing a netstat when connecting here's the MTR on the two IP i found being owned by Bungie. note : i'm on PC and Windows 11, also MTR using ICMP Ping, that's kinda normal to have loss on IP exchange point, what is interesting is latency i hote that will help you find the problem as all the other games i'm playing just connect fine. ---------- $ netstat -n | grep 192.168 | grep -E "172.97|205" TCP 192.168.x.x:49677 205.209.23.5:443 TIME_WAIT TCP 192.168.x.x:49697 205.209.21.104:7500 CLOSE_WAIT ---------- mtr -n 205.209.21.104 Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 5. 130.105.0.122 0.0% 54 8.5 9.4 6.8 17.7 1.4 6. 130.105.0.18 0.0% 54 9.1 10.5 6.4 53.3 6.6 7. 180.87.54.80 0.0% 54 36.6 36.5 35.1 40.3 1.0 8. 180.87.108.80 61.1% 54 212.5 213.1 212.0 214.8 0.8 11. 120.29.211.2 96.2% 54 107.7 108.6 107.7 109.5 1.3 12. 209.58.86.144 98.1% 54 213.4 213.4 213.4 213.4 0.0 13. 209.58.86.37 98.1% 54 214.5 214.5 214.5 214.5 0.0 14. (waiting for reply) ------- mtr -n 205.209.23.5 Host Loss% Snt Last Avg Best Wrst StDev 5. 130.105.0.122 0.0% 417 9.9 9.3 8.0 27.7 1.4 6. 130.105.0.24 0.0% 417 8.6 8.8 7.7 16.9 1.0 7. 4.14.45.49 84.4% 417 154.6 154.8 153.4 158.0 1.0 8. 4.69.148.126 0.0% 417 179.2 179.4 177.6 205.1 2.4 9. (waiting for reply)

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon