Marathon lag usually comes from one of three places: matchmaking putting you on a far-away data centre, your own connection, or server problems during busy periods. Bungie's extraction shooter doesn't let you pick a server, but it does have one setting that makes a big difference to ping, especially if you live in a region with fewer players. Here's how to use it, how to check your connection without an in-game network graph, and the fixes for rubber-banding and packet loss.
What ping is good for Marathon?
| Ping | How it plays |
|---|---|
| Under 50 ms | Ideal: fights feel instant |
| 50–80 ms | Fine for most players |
| 80–120 ms | Close-range fights and abilities feel late |
| Above 120 ms | You lose trades you should win |
In an extraction shooter, lag costs more than one fight: if you die to a late hit, you lose what you were carrying out. That's why a steady connection matters more here than in a game where you just respawn.
Step 1: Check Bungie's server status
Before changing anything, check whether the problem is on Bungie's side:
- @BNGServerStatus on X posts maintenance, incidents and fixes.
- The Marathon help site lists known issues and has a network troubleshooting section.
If there's an incident, everyone lags or disconnects at once, and no setting on your side will help. Lag right after an update or at the start of a new season is also often server load.
Step 2: Set Connection Quality to prioritise local matches
This is the most important Marathon-specific setting:
- Open Settings.
- Find Connection Quality.
- Set it to prioritise local matches.
Bungie's explanation: with this setting, matchmaking waits longer for a nearby server before expanding to other regions. Queue times can be longer, but you're much less likely to end up on another continent.
Two things to know:
- In a crew, the leader's setting applies. If you're grouped up, the crew leader has to change it.
- Low-population regions feel it most. Players in Latin America, Oceania and parts of Asia have reported constant high ping, and Bungie has acknowledged routing and regional availability problems. Bungie has also adjusted regional matchmaking since launch to balance queue times and latency; it's a trade-off, because a bigger player pool can mean higher ping.
Getting fewer far-away matches
If you're in a region with fewer players, a few habits help on top of the setting:
- Play at your region's busy hours. In the evening there are more local players, so matchmaking finds a nearby server without expanding.
- Group with players from your region. A crew spread across continents forces someone onto a distant data centre.
- Check the leader's setting before you queue. The crew leader's Connection Quality decides for everyone, so make sure it's set to prioritise local matches.
- Give the queue a little longer. Cancelling and requeueing quickly doesn't help; the setting works by waiting.
Step 3: Test your connection
Marathon shows very little detailed connection information in game, so test your line from outside it. With the game running, open Command Prompt on Windows and run:
ping -t 1.1.1.1
Watch the numbers when the game lags. Spikes at the same moment point to your connection. For packet loss, run:
pathping 1.1.1.1
Loss that starts at your router or your ISP's first hops is on your side; loss that continues to the end points to the route. A ping booster's overlay also shows live ping and loss.
| What you find | What it means |
|---|---|
| Ping to 1.1.1.1 steady and low, game feels laggy | Far-away data centre or the route to it |
| Ping jumps or shows loss | Your connection: Wi-Fi, other traffic, router |
| Everyone in the match rubber-bands | Server problem |
| Game hitches, ping steady | FPS drops on your device |
Step 4: Fix your home connection
Bungie recommends a wired home connection for Marathon, and its troubleshooting advice follows the same lines as for its other games.
- Use Ethernet. Wi-Fi is the most common cause of spikes and loss. See Wi-Fi vs Ethernet for gaming.
- Don't play on a mobile hotspot. Mobile connections are much less stable and usually come with strict NAT. If it's your only option, see mobile hotspot for gaming.
- Pause downloads and uploads on every device: launchers, console updates, cloud backups, streams and video calls.
- Turn on SQM or QoS on your router if other people use the connection while you play. Why: bufferbloat.
- Restart your router and modem, and update the router's firmware.
- Disconnect any VPN you don't need. It can make matchmaking think you're somewhere else.
Step 5: Set up UPnP or port forwarding, not both
Marathon, like Bungie's other games, works best with an open NAT. If several devices in your home play online, UPnP is the simplest way to keep them all working. Port forwarding works for a single device, but don't combine UPnP and manual port forwarding for the same console or PC: the two can conflict and cause connection problems.
- When to use which: UPnP on or off for gaming.
- How to forward ports: port forwarding for gaming.
- If your NAT is strict on Xbox: Xbox NAT type strict.
- If you have two routers, check for double NAT.
Step 6: Rule out FPS drops on PC
If the game stutters while your ping stays steady, it's your frame rate, not the network.
- Cap your frame rate at what your PC holds in busy fights.
- Lower effects and shadows first, and turn on upscaling if your GPU struggles.
- Update your GPU driver and close background apps.
- Turn off overlays you don't use, including the Steam overlay, if you see hitches or crashes.
Still unsure? See input lag.
Repair the install if problems started suddenly
If Marathon was fine and started lagging, hitching or disconnecting after an update while other games run normally, the install may be damaged:
- Steam: right-click Marathon → Properties → Installed Files → Verify integrity of game files.
- PS5 and Xbox: fully restart the console (not rest mode), and check for a pending game update.
- Graphics driver: if the problem started after a driver update, try a clean install of the current version.
Then restart your router as well, so you test with a clean connection.
Lag after updates and at season start
New seasons and big patches bring the most players back at once, and they also change the game. Expect some server-side lag in the first hours, and on PC, the first matches after an update can hitch while shaders rebuild. If lag starts right after a patch, check @BNGServerStatus and Bungie's known issues before you start changing your setup; if it's a known problem, the fix is on Bungie's side.
On PS5 and Xbox
- Use a cable, and pause downloads in the background.
- Check NAT type in the console's network settings, and use UPnP on your router if you can.
- Set Connection Quality the same way as on PC.
More: how to lower ping on PS5 and Xbox.
When a booster helps
Marathon has no server picker, so a ping booster can't move you to a different data centre. What it can do is improve the route between your ISP and the data centre you're placed on. That's useful when your home network is clean, Connection Quality is set to local and ping or loss is still bad, especially in the evening. ExitLag and GearUP support Marathon; test a free trial at the same time of day you normally play.
Quick diagnosis
| Symptom | Likely cause | Fix |
|---|---|---|
| Everyone lags, disconnects | Servers | Check @BNGServerStatus, wait |
| Steady high ping, often far region | Matchmaking expanding | Connection Quality: prioritise local |
| High ping only in a crew | Leader's setting | Crew leader changes Connection Quality |
| Spikes and loss | Wi-Fi, hotspot or busy network | Ethernet, pause downloads, SQM |
| Party or join problems | NAT | UPnP or port forwarding, not both |
| Only you lag, evenings, clean network | ISP or route | pathping, booster trial |
Other extraction shooters have similar problems: see ARC Raiders lag. For lag that snaps you back, see rubber-banding explained. The best boosters for this game are on the Marathon page.



