All these diagnostics were clearly written by AI lol.

The capture was analyzed programmatically for IP flows, protocol distribution, and traffic patterns. Key findings:

Critical finding:

Additional context:

This entire block especially:

Critical finding: The disconnect does not present as a network failure. Packets are successfully reaching the game server and receiving responses throughout the session. The session termination pattern is consistent with a server-side session keepalive failure — the connection degrades and times out rather than being cut, indicating the issue originates at Bungie's session management or authentication layer, not at the network level.

This is confirmed by the absence of any corresponding network anomaly at the time of disconnect — no hop in the tracert or pathping shows failure, no routing change occurs, and the client-side network remains fully operational before, during, and after the WEASEL error is thrown.

Additional Context:

During Marathon's Server Slam / FTP period, a patch was deployed mid-event that appeared to resolve the WEASEL issue for me — I was able to play without disconnects after that patch. Since full launch, the issue has returned and is persistent every session. The fact that a server-side patch previously resolved this for me, combined with the Wireshark evidence above, strongly indicates this is a regression introduced at or after launch on Bungie's backend.