Bungie’s extraction shooter Marathon launched with the kind of potential that keeps you queueing run after run — until the rubberbanding yanks you back mid-gunfight, your loot disappears to a desync, or your frames crater right when it matters most. If you’re dealing with Marathon lag, you’re not alone. The community has been vocal about connection drops, CENTIPEDE and ANTEATER errors, and FPS stuttering even on solid hardware. This guide walks through every Marathon lag fix that actually works, from network-level changes to PC settings tuned for the Tiger engine.
What Type of Marathon Lag Are You Dealing With?
Marathon lag isn’t one problem — it’s usually one of three:
- Network lag (high ping, rubberbanding): You see enemies teleporting, shots not registering, or your character snapping backward. This is a connection issue between you and Bungie’s servers.
- FPS stuttering (frame drops, micro-stutters): Your game hitches or freezes for a fraction of a second, especially during firefights or when loading new areas. This is a local performance issue.
- Input delay: Your mouse or controller feels sluggish, like there’s a buffer between your actions and what happens on screen.
Each type has a different fix. Start by pressing your in-game network stats overlay to check your ping and packet loss, then work through the section that matches your symptoms.
Fix Marathon Network Lag and High Ping
High ping in Marathon means the data between your PC and Bungie’s servers is taking too long to travel. Anything above 80ms and you’ll start noticing delayed hit registration and rubberbanding during extractions.
Choose the Right Server Region
Marathon uses regional data centers. In your game settings, look for the Server Region option and select the one closest to your physical location. Connecting to a server across the ocean adds 100-200ms of latency that no amount of tweaking can fix.
Switch to a Wired Connection
Bungie explicitly recommends a wired Ethernet connection for Marathon. Wi-Fi introduces jitter, packet loss, and latency spikes that cause the rubberbanding players have been reporting since launch. If you can’t run Ethernet, check out our guide on getting the best Wi-Fi signal for gaming on PC.
Fix Your NAT Type
A Strict or Type 3 NAT is one of the most common causes of the CENTIPEDE error code in Marathon. You need an Open NAT for reliable connections.
- Log into your router admin panel (usually 192.168.1.1 or 192.168.0.1).
- Enable UPnP (Universal Plug and Play). Bungie recommends UPnP over manual port forwarding.
- If multiple devices on your network play Marathon simultaneously, UPnP is required — port forwarding won’t work for two Marathon instances on the same connection.
- If UPnP isn’t available and only one device plays Marathon, use port forwarding as a fallback.
Important: Never enable both UPnP and port forwarding at the same time. This causes conflicts that make connectivity worse. For a full walkthrough, see our NAT type fix guide for PS5, Xbox, and PC.
Reduce Network Congestion
Every device sharing your internet connection competes for bandwidth. During a Marathon session:
- Pause downloads, updates, and cloud syncs on all devices.
- Close streaming apps (Netflix, YouTube, Twitch) on other devices or set them to lower quality.
- Enable QoS (Quality of Service) on your router to prioritize your gaming device’s traffic. Most modern routers have a gaming priority toggle — use it. Our QoS settings guide covers this step by step.
Switch Your DNS Server
Your ISP’s default DNS can be slow and inconsistent. Switching to a faster DNS won’t dramatically lower your ping, but it speeds up initial connections and can reduce DNS-related timeouts:
- Cloudflare: 1.1.1.1 / 1.0.0.1
- Google: 8.8.8.8 / 8.8.4.4
Change this in your network adapter settings or directly on your router. For a full comparison, read our best DNS servers for gaming breakdown.
Fix Packet Loss
If your in-game overlay shows packet loss above 1%, that’s the source of your rubberbanding and desync. Packet loss means data is being dropped between you and the server.
- Run a traceroute to identify where packets are being lost: open Command Prompt and type
tracert marathon-servers.bungie.net(or use a visual traceroute tool like WinMTR). - If packet loss occurs at the first few hops, the issue is your local network — check cables, restart your modem and router, or bypass your router temporarily.
- If packet loss occurs mid-route, it’s an ISP routing issue. Contact your ISP with the traceroute data and ask them to investigate. Our packet loss fix guide has the full diagnostic process.
Fix Marathon Error Codes
Marathon inherited Bungie’s animal-themed error code system. Here’s what the most common ones mean and how to fix them:
| Error Code | Meaning | Fix |
|---|---|---|
| CENTIPEDE | General networking error — lost connection to Marathon servers | Check NAT type (must be Open), switch to wired, restart network hardware |
| ANTEATER | Client unable to establish server connection | Disable Wi-Fi and use Ethernet, check for ISP outages, flush DNS cache |
| BABOON | Packet loss detected between you and Marathon servers | Run traceroute to isolate the hop, reduce network congestion, contact ISP |
| WEASEL | Authentication or account-level disconnection | Restart the game, verify game files, check Bungie server status |
If you’re seeing BABOON or ANTEATER repeatedly, Bungie has acknowledged ongoing investigations into these errors. Check the Bungie server status page before troubleshooting — the issue might be on their end.
Still lagging after trying everything?
WTFast reroutes your game traffic through optimized servers — cutting ping by 30-50% for most players.
Fix Marathon FPS Drops and Stuttering on PC
Marathon runs on Bungie’s Tiger engine, which streams map geometry continuously during gameplay. This means your storage speed, VRAM, and CPU thread handling all affect frame delivery in ways that aren’t obvious from the settings menu.
Recommended Graphics Settings for Stable FPS
These settings prioritize consistent frame delivery over maximum visual quality:
| Setting | Recommended Value | Why |
|---|---|---|
| Resolution | Native or one step down | Dropping to 1080p frees significant GPU headroom |
| Upscaling | DLSS Quality (NVIDIA) / FSR Quality (AMD) | ~25% FPS gain with minimal image quality loss |
| Frame Generation | On (RTX 40/50 series only) | Smooths frame pacing and boosts average FPS |
| Shadow Quality | Medium | Shadows are the single most expensive setting in the Tiger engine |
| Motion Blur | Off | Reduces GPU load and improves target tracking |
| Film Grain | Off | Purely visual — no performance cost, but reduces clarity |
| Chromatic Aberration | Off | Same as film grain — turn it off for competitive play |
| Texture Quality | High (8GB VRAM) / Ultra (12GB+ VRAM) | Ultra textures use 8-10GB VRAM at 1440p — 8GB cards will stutter |
| VSync | Off | Adds input lag — use a frame cap instead |
Cap Your Frame Rate Properly
Don’t run Marathon with uncapped frames. The Tiger engine delivers smoother frame pacing when you set a ceiling:
- Set your frame rate cap to 3 below your monitor’s refresh rate (e.g., 141 FPS for a 144Hz monitor).
- Use RTSS (RivaTuner Statistics Server) for the most consistent frame cap — it’s more reliable than in-game limiters.
- If you have an NVIDIA GPU, enable NVIDIA Reflex (set to On + Boost) to reduce render queue latency.
Fix Shader Compilation Stutters
The first time you enter a new area or encounter a new visual effect, Marathon compiles shaders on the fly. This causes 50-200ms freezes that feel like micro-stutters.
- NVIDIA users: Open NVIDIA Control Panel → Manage 3D Settings → Set Shader Cache Size to Unlimited. This lets your GPU store compiled shaders permanently instead of recompiling them.
- Run through the game’s training area once after updating drivers to pre-compile common shaders.
Disable Windows 11 MPO
Multiplane Overlay (MPO) is a Windows 11 feature that causes frame pacing issues in many games, including Marathon. Disabling it fixes stuttering for a significant number of players.
Open Registry Editor and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm
Create a new DWORD (32-bit) value named OverlayTestMode and set it to 5. Restart your PC.
Ensure You’re Running an SSD
Marathon requires SSD-speed storage. The Tiger engine streams world geometry continuously — an HDD or slow SATA SSD will cause persistent micro-stutters and texture pop-in. If you’re on an HDD, moving Marathon to an NVMe or SATA SSD is the single biggest performance upgrade you can make.
System-Level Tweaks
- Enable Hardware-accelerated GPU Scheduling (HAGS) in Windows Settings → Display → Graphics → Change default graphics settings. This helps smooth out 1% lows.
- Close background applications — especially browsers, Discord overlay, and recording software. Marathon is CPU-intensive, and background processes steal threads.
- Make sure you have 32GB RAM if possible. Marathon’s asset streaming is aggressive, and 16GB systems will hit swap more frequently during extended sessions.
Fix Marathon Lag on Console (PS5 and Xbox)
Console players don’t have graphics settings to tweak, but network fixes apply equally:
- Use a wired connection. This is the single most impactful change on console. See our console Ethernet setup guide if you need help running cable.
- Set your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) in your console’s network settings.
- Enable UPnP on your router. If your NAT type shows as Strict or Moderate, this is likely the issue.
- Rebuild your database (PS5) or Clear persistent storage (Xbox) to fix corrupted game data that can cause stuttering.
- Check for game updates. Bungie has been pushing optimization patches post-launch — make sure you’re running the latest version.
For platform-specific network fixes, check our PS5 high ping fix and Xbox Series X lag fix guides.
Still lagging after trying everything?
WTFast reroutes your game traffic through optimized servers — cutting ping by 30-50% for most players.
FAQ
Why is Marathon so laggy even with good internet?
Marathon lag with good internet is usually caused by ISP routing issues, a Strict NAT type, or packet loss at an intermediate hop between you and Bungie’s servers. Run a traceroute to identify where the delay is happening. High download speed does not guarantee low latency — ping and packet loss matter more for online gaming.
What does the CENTIPEDE error code mean in Marathon?
CENTIPEDE is a general networking error in Marathon that means your client lost connection to Bungie’s servers. The most common causes are a Strict or Type 3 NAT, Wi-Fi instability, or ISP-level packet loss. Switch to Ethernet, enable UPnP on your router, and restart your modem to fix it.
What are the best Marathon PC settings for high FPS?
Set Shadow Quality to Medium, enable DLSS Quality or FSR Quality for upscaling, turn off Motion Blur and VSync, and cap your frame rate 3 below your monitor’s refresh rate using RTSS. If you have an 8GB GPU, keep Texture Quality at High instead of Ultra to avoid VRAM overflow stuttering.
Does Marathon need an SSD?
Yes. Marathon’s Tiger engine streams map geometry continuously during gameplay, and an HDD cannot keep up. Running Marathon on a hard drive causes persistent micro-stutters and texture pop-in. An NVMe SSD is ideal, but a SATA SSD works fine.
How do I fix rubberbanding in Marathon?
Rubberbanding in Marathon is caused by packet loss or high ping. Switch to a wired Ethernet connection, enable UPnP on your router, close bandwidth-heavy applications on your network, and select the server region closest to your location. If the issue persists, run a traceroute to check for packet loss at your ISP level.
What to Do Next
Start with the basics: wired connection, correct server region, and Open NAT. Those three changes fix the majority of Marathon lag issues. If your ping is fine but you’re still stuttering, move to the PC optimization section — Shadow Quality on Medium, shader cache set to Unlimited, and a proper frame cap will smooth out most frame delivery problems. And if your ISP routing is the bottleneck, a game path optimizer like WTFast can reroute your traffic through faster nodes to cut latency where your ISP won’t.
