Daily Report – Error Code WEASEL Still Occurring (Mar 11, 2026 | PC)
Report Date: 10 March 2026, 17:21 UTC
Since day two of the Server Slam and since release I'm consistently hitting the following error. I'm posting this as a report because the issue occurred again today as well.
"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/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
- Flushed DNS cache (ipconfig /flushdns)
System info:
OS: Windows 11 Pro 23H2
CPU: AMD Ryzen 9 9800X3D
GPU: RTX 4080 (Driver 591.74)
RAM: 32 GB
Country: Germany
ISP: Deutsche Telekom
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. Listing everything below for full transparency.
System Specs:
Everything I have tried (none resolved the issue):
Tracert Outputs:
1.
Tracing route to 198.199.23.1 over a maximum of 30 hops
1 3 ms 1 ms 1 ms 192.168.50.1
2 11 ms 12 ms 11 ms int-1.sntlcasm03m.netops.charter.com [142.254.176.173]
3 15 ms 19 ms 15 ms lag-58.sntlcaga02h.netops.charter.com [76.167.28.153]
4 27 ms 13 ms 11 ms lag-19.hcr02sntlcaga.netops.charter.com [76.167.5.0]
5 10 ms 14 ms 10 ms lag-47.mcr11vnnzca24.netops.charter.com [76.167.5.2]
6 * * * Request timed out.
7 * * * Request timed out.
Network path to the internet is clean with solid latency (10–27ms). Hops 6–7 timing out is consistent with routers configured to silently drop ICMP packets, not indicative of a break in connection.
2.
Tracing route to bungie.net [199.189.118.227]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.50.1
2 8 ms 18 ms 12 ms int-1.sntlcasm03m.netops.charter.com [142.254.176.173]
3 47 ms 17 ms 15 ms lag-58.sntlcaga02h.netops.charter.com [76.167.28.153]
4 12 ms 14 ms 11 ms lag-19.hcr02sntlcaga.netops.charter.com [76.167.5.0]
5 14 ms 16 ms 12 ms lag-47.mcr11vnnzca24.netops.charter.com [76.167.5.2]
6 16 ms 14 ms 14 ms lag-29.rcr01tustcaft.netops.charter.com [72.129.13.2]
7 19 ms 16 ms 44 ms lag-36-10.tustca4200w-bcr00.netops.charter.com [66.109.6.202]
8 16 ms 18 ms 23 ms lag-1.pr2.lax10.netops.charter.com [66.109.5.241]
9 * * * Request timed out.
10 * * * Request timed out.
11 24 ms 24 ms 26 ms ae8.cs1.lax112.us.zip.zayo.com [64.125.28.44]
12 22 ms 23 ms 20 ms ae24.mpr2.las15.us.zip.zayo.com [64.125.25.101]
13 32 ms 20 ms 21 ms ae12.mpr2.las1.us.zip.zayo.com [64.125.21.240]
14 25 ms 23 ms 30 ms 128.177.113.122.IPYX-090920-ZYO.zip.zayo.com [128.177.113.122]
15 23 ms 23 ms 23 ms be1761.las-sagg9s3-1.sinap-tix.com [199.189.116.202]
16 * * * Request timed out.
17 * * * Request timed out.
A second tracert was run directly to bungie.net (199.189.118.227) to get a more complete picture of the route to Bungie's infrastructure. The full path is visible and reaches 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 and not indicative of packet loss. From hop 11 onward, traffic is handed off to Zayo, a third-party backbone transit provider, which carries it 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 itself completes without obvious breaks, it is worth noting that tracert only measures ICMP traffic — any packet loss or routing issues affecting UDP game traffic specifically (which Marathon uses for live sessions) would not be visible here and could still be occurring silently between Zayo, Sinap-tix, and Bungie's game servers. This is consistent with a scenario where the connection appears healthy on paper but game sessions are being dropped at the authentication or session layer on Bungie's backend.
Additional context:
During Marathon's Server Slam / FTP period, a patch was deployed mid-event that appeared to resolve the WEASEL issue for me at the time — I was able to play without disconnects after that patch. Since the full launch, the issue has returned and is persistent every session regardless of what I try.
I am not looking for basic troubleshooting suggestions — I have genuinely exhausted every user-side fix documented by Bungie and the community. Based on the tracert results, my Open NAT status, and the fact that a server-side patch previously resolved this for me, I believe this is a backend authentication or routing issue on Bungie's end affecting certain ISPs or network configurations.
I am aware that issue has been acknowledged via BungieHelp Twitter/X & Discord, and that they are investigating WEASEL errors. I am submitting this for documentation purposes to help expedite the investigation. Happy to provide any additional diagnostic info if it helps.
Please sign in to leave a comment.