**Subject: Persistent WEASEL during character selection — TCP 7500 remote FIN/RST confirmed with Wireshark** Hello Bungie Support, I am reporting a persistent WEASEL issue on Destiny 2 PC that occurs a few seconds after reaching character selection. I have performed extensive troubleshooting and collected packet-level evidence showing that the TCP connection on port 7500 is being closed by the remote endpoint immediately before WEASEL occurs. ### Reproduction - Platform: PC / Steam - Destiny 2 reaches the character selection screen normally. - WEASEL occurs shortly afterward, before I can successfully proceed into the game. - The issue is reproducible. - The issue also occurred with a different Bungie account. - The issue also occurred while using a completely different Internet connection through a mobile phone hotspot. ### Troubleshooting already performed I have already tested/rechecked the following: - Steam file verification completed successfully: all 2492 files validated. - Winsock/IP network reset performed. - IPv6 was temporarily disabled and the issue persisted; IPv6 was subsequently re-enabled. - Radmin VPN was disabled; the issue persisted. - Windows Firewall was checked for Destiny 2/BattlEye blocking rules. - BattlEye service is running normally. - BattlEye driver installation was observed in Windows Event Viewer without corresponding service/Code Integrity failures. - No relevant Windows Service Control Manager or Code Integrity errors were found at the time of the failure. - The problem occurs on both my normal wired Internet connection and a mobile hotspot. - I also tested another Destiny/Bungie account, with the same result. - Saved Bungie.net loadouts had already been deleted previously. ### Network observations Basic connectivity is healthy: - IPv4 ping to bungie.net: 0% packet loss. - IPv6 ping to bungie.net: 0% packet loss. - TCP 443 connectivity to bungie.net succeeds. - The route to Bungie/Cloudflare completes normally. - The problem is not a general loss of Internet connectivity. The Destiny 2 process remains running after WEASEL, but its TCP connections disappear. ### TCP 7500 evidence I captured the connection directly with Wireshark. During the failure, Destiny establishes a TCP connection to a Bungie endpoint on port 7500. The critical packet sequence immediately preceding WEASEL was: ```text 22247 214.028837000 172.97.56.39 -> 192.168.0.10 TCP 7500 → 58706 [FIN, ACK] Seq=113178 Ack=40199 Win=261888 Len=0 22248 214.028910900 192.168.0.10 -> 172.97.56.39 TCP 58706 → 7500 [ACK] Seq=40873 Ack=113179 Win=65280 Len=0 22249 214.039575200 172.97.56.39 -> 192.168.0.10 TCP 7500 → 58706 [RST, ACK] Seq=113179 Ack=40873 Win=0 Len=0 22250 214.131716700 172.97.56.39 -> 192.168.0.10 TCP 7500 → 58706 [RST] 22254 214.204383000 172.97.56.39 -> 192.168.0.10 TCP 7500 → 58706 [RST] ``` The important point is that the first termination packet is **inbound**: ```text 172.97.56.39:7500 → my PC FIN, ACK ``` My PC acknowledges it normally. Approximately 10.7 ms later, the same remote endpoint sends: ```text RST, ACK ``` followed by additional RST packets. This is consistent with the TCP socket transitioning to CLOSE_WAIT after the remote side initiates the connection shutdown. ### ETW evidence I also captured a Windows `netsh trace` during a WEASEL reproduction. The ETW trace showed the Destiny 2 process (PID 19032) on a TCP connection to a `172.97.56.x:7500` endpoint. Immediately before termination, Windows recorded: ```text TCP Tail Loss Probe TCP connection: 192.168.0.10:50856 -> 172.97.56.199:7500 connection terminated: received RST shutdown initiated: 0xC000020D (NT = The transport connection has been reset) PID = 19032 ``` Windows subsequently closed the socket. A later event showed the endpoint no longer existed, which is consistent with the socket already having been terminated by the RST. ### Why I am requesting server-side investigation The issue does not appear to be a generic loss of Internet connectivity. The evidence shows that the Destiny TCP 7500 session is being terminated from the remote side immediately before the WEASEL error. I am aware that WEASEL is normally a general connectivity error, so I am not claiming that this packet alone proves a Bungie server fault. However, I would like Bungie's networking/engineering team to check the server-side logs for the affected session. In particular, please investigate: 1. Why the TCP 7500 session to `172.97.56.39` is being closed with `FIN` and then `RST`. 2. Whether the server is intentionally terminating the authentication/session connection. 3. Whether there is a timeout or failed server-side state transition immediately before the disconnect. 4. Whether there is an account/profile/character-state issue associated with the session. 5. Whether the same issue is currently affecting other PC players. There are also Bungie forum reports from 2026 describing a very similar pattern involving WEASEL, TCP port 7500, remote FIN packets, and CLOSE_WAIT. Bungie support previously acknowledged an increase in reports and stated that the issue was being investigated. For example, one report documents the same general behavior of a remote `172.97.56.x:7500` endpoint sending FIN immediately before WEASEL, and another reports the same issue across different PCs/networks. I can provide the complete Wireshark capture and ETW trace if required. Please escalate this to the appropriate networking/server engineering team rather than treating it solely as a generic local-network troubleshooting issue. Thank you.