Daily Report - Error Code WEASEL Still Occurring (16 March 2026, 02:46 UTC, PC)
Since day two of the Server Slam and since release I'm consistently hitting the following error. I'm posting this as a daily report because the issue occurred again today. I immediately get kicked out of the tutorial.
"Could not connect to Marathon servers. Check your network configuration and try again. For information on resolving this issue visit help.bungie.net and search for error code: WEASEL."
I'm the only person on my network, on PC, using a wired Ethernet connection. Every other online or multiplayer game works perfectly fine. Nothing in my setup has changed since the first day of the Server Slam when the game worked.
I've gone through both the Marathon Network Troubleshooting Guide and the Error Code WEASEL page and completed every step listed. Below is a full list of everything I've tried:
- Verified game files
- Forwarded all required ports (TCP and UDP)
- Reinstalled the game
- Reinstalled BattleEye
- Restarted my router (full power cycle)
- Changed DNS servers (tested 1.1.1.1 and 8.8.8.8)
- Enabled and disabled UPnP
- Closed all unnecessary background apps and downloads
- No third-party antivirus. Windows Defender only (tested with it temporarily disabled)
- Tested with a VPN (and without)
- Disabled DLSS Override in the Nvidia App
- Tried a different Steam account (during Server Slam)
- Flushed DNS cache (ipconfig /flushdns)
- Ran Winsock reset (netsh winsock reset + netsh int ip reset)
- Ran System File Checker (sfc /scannow) to verify Windows system file integrity
System info:
OS: Windows 11 Pro 23H2
CPU: AMD Ryzen 9 9800X3D
GPU: RTX 4080 (Driver 591.74)
RAM: 32 GB
Router: FRITZ!Box 7490, firmware: FRITZ!OS 7.62
Connection: Wired Ethernet
Country: Germany
ISP: Deutsche Telekom
Bungie Account: Gitorian#9112
Platform: Steam / PC
Traceroute results:
Tracing route to bungie.net [104.17.100.21]
2 17 ms 16 ms 15 ms p3e9bf12c.dip0.t-ipconnect.de [62.155.241.44]
3 24 ms 24 ms 24 ms b-eh3-i.B.DE.NET.DTAG.DE [62.153.188.118]
4 23 ms 23 ms 22 ms ae10.edge5.ber1.sp.lumen.tech [4.68.62.205]
5 24 ms 24 ms 24 ms dialup-212.162.17.178.frankfurt1.mik.net [212.162.17.178]
6 25 ms 24 ms 24 ms 104.17.100.21
Tracing route to active session endpoint observed during gameplay (205.234.118.78)
2 18 ms 16 ms 17 ms p3e9bf12c.dip0.t-ipconnect.de [62.155.241.44]
3 25 ms 25 ms 24 ms f-ed11-i.F.DE.NET.DTAG.DE [62.154.18.18]
4 25 ms 24 ms 24 ms 80.157.128.21
Additional diagnostic test (pathping):
1 fritz.box [192.168.178.1]
2 p3e9bf12c.dip0.t-ipconnect.de [62.155.241.44]
3 f-ed11-i.F.DE.NET.DTAG.DE [62.154.18.18]
4 80.157.128.21
Packet loss observed: 0% within the local network and ISP backbone.
The traceroute to the session endpoint stops after the Deutsche Telekom backbone. This is expected behavior because many game servers and relay networks intentionally drop ICMP packets and traceroute probes for security reasons. However, there is no packet loss or abnormal latency visible within the ISP network path.
Additional context:
I have exhausted all user side troubleshooting steps documented in the official guide and commonly suggested by the community. My local network, hardware configuration, and ISP connectivity appear stable, and other online games function normally, which suggests the issue may be related to backend connectivity, authentication, or session routing affecting certain players.
I am aware that the issue has been acknowledged by BungieHelp and that it is currently under investigation. This report is being submitted for documentation purposes in case additional network information from EU players using Deutsche Telekom is helpful.
Additional Diagnostic Information:
To provide further troubleshooting data, I have attached a full export of all Windows services running on my system.
It was generated using ServiWin v1.72 and contains a complete list of services, including their status, startup type, display name, and executable path. This is intended to help identify any potential service conflicts, security software, network filters, or background components that might interfere with the game's networking or anti-cheat systems.
Comments
Bungie Account Name: CloudyMinds#6190
Platform: Steam/PC (Windows 10 Pro LTS 22H2 build 19045.6937)
Error Code: WEASEL (consistent, every session)
Issue: I am being repeatedly disconnected from Marathon servers with error code WEASEL. This has been happening consistently since launch. I have gone through every step listed in the official Network Troubleshooting Guide and then some, and have now conducted advanced network diagnostic analysis including Wireshark packet capture and pathping. The evidence conclusively points to a server-side session management issue on Bungie's infrastructure. I am submitting this fully documented report for escalation.
System Specs:
Everything I have tried (none resolved the issue):
Tracert Outputs:
1. Direct trace to Marathon game server (205.234.118.195 — confirmed via Wireshark capture):
This tracert was run directly to the Marathon game server IP confirmed via Wireshark packet capture analysis. Charter/Spectrum handles hops 1–10 cleanly with consistent latency (1–37ms) and zero timeouts, confirming the client-side network path is fully healthy. At hop 11, traffic enters Akamai Prolexic (206.223.116.136), a DDoS mitigation and traffic scrubbing service that Bungie uses to protect their game servers. Hops 12–16 time out as expected — Prolexic deliberately obscures the path beyond their scrubbing infrastructure for security purposes. Importantly, this means all game session traffic passes through Prolexic's filtering layer before reaching Bungie's backend servers. The session keepalive failures documented in the Wireshark analysis below may be occurring at this Prolexic filtering layer or at Bungie's session management layer behind it, either of which is entirely outside the client's control.
2. Direct trace to bungie.net
A second tracert run directly to bungie.net (199.189.118.227) shows the full path reaching Bungie's network edge at hop 15. Charter/Spectrum handles hops 1–8 cleanly with consistent latency (2–44ms, with hop 7 showing a single spike to 44ms that did not persist). Hops 9–10 timing out is consistent with standard ICMP filtering. From hop 11 onward, traffic is handed off to Zayo, a third-party backbone transit provider, routing through Los Angeles and Las Vegas before terminating at Sinap-tix (hop 15), which sits at the edge of Bungie's network. Latency stabilizes cleanly at 23ms by hop 15. While the route completes without obvious breaks, tracert only measures ICMP traffic — any packet loss affecting UDP game traffic specifically would not be visible here and could still be occurring silently between Zayo, Sinap-tix, and Bungie's game servers.
Pathping Output (to bungie.net 199.189.118.227):
Note: Elevated ICMP loss at hops 3, 5, and 6 (19%, 17%, 11%) is worth flagging, though backbone routers commonly deprioritize ICMP under load. Hops 7 and 8 return to 0% loss, and latency throughout remains stable. The route completes cleanly to Spectrum's LAX egress point.
Wireshark Packet Capture Analysis:
A full Wireshark capture was conducted covering one minute before game launch through to post-disconnect. The capture was analyzed programmatically for IP flows, protocol distribution, and traffic patterns. Key findings:
Identified game server IP: 205.234.118.195 (Marathon game server, TCP port 7500)
Traffic pattern timeline:
OUT=3, IN=12— a disproportionate spike of 12 inbound packets against 3 outbound, inconsistent with normal session trafficCritical 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.
I am aware that Bungie/@BungieHelp has publicly acknowledged they are investigating WEASEL errors. It has now been over 10 days since launch with no resolution and no communicated timeline. Multiple players remain completely unable to access the product they paid for.
Regarding previous support responses on this thread: Prior responses directed me to check minimum system requirements (my system exceeds them significantly: Ryzen 7 9800X3D, RTX 5070 Ti, 32GB DDR5), install the game on another disk, noted the game is unsupported on laptops (I am on a desktop), and provided Windows 11 recovery steps despite my OS being clearly listed as Windows 10 Pro in every submission. These responses did not reflect the contents of my report. I have run both
sfc /scannowandDISM /Online /Cleanup-Image /RestoreHealthas the Windows 10 equivalent — no issues were found.I am respectfully but firmly requesting escalation to a senior support agent or network engineer who can review the technical evidence provided. The Wireshark analysis in particular represents definitive proof that this issue is not client-side and cannot be resolved through any further user-side troubleshooting. The fix must come from Bungie.
Happy to provide the raw Wireshark capture file or any additional diagnostic data upon request.
Please sign in to leave a comment.