iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If Marathon disconnects or crashes during a run, Bungie says your shell remains in the game world and you can relaunch the game and try to reconnect. That does not guarantee your starting gear will be returned: Bungie limits gear returns to certain server- or network-infrastructure errors and excludes losses caused by your internet connection or client-side problems. For lag, failed matches, or recurring disconnects, first identify whether the symptom points to your home network, the wider internet path, Bungie’s service, or a matchmaking or client issue.
Start by identifying what failed
“Connection problem” can describe several different failures, and the right next step depends on which one you see. A crash may leave you needing to relaunch and reconnect. Lag may mean delayed responses or data loss. A failed match or unexpected queue may involve matchmaking state rather than a weak connection. Avoid treating every symptom as proof that Bungie’s servers are down—or that your home network is at fault.
- Crash or disconnect during a run: prioritize relaunching and attempting to reconnect to your shell. A disconnect does not itself establish whether the cause was Bungie-side, the internet path, or your device.
- Delayed actions or rubber-banding: consider latency, packet loss, or both. They are distinct problems and can have different causes.
- Wrong queue, failed match start, or a queue that appears stuck: consider a matchmaking-state or client issue as well as connectivity. Bungie documented and patched one Solo Queue state issue in 2026.
- Repeated server connection errors: a speed test or a working browser connection does not, by itself, rule out intermittent packet loss, local hardware problems, or trouble elsewhere between your home and the game service.
Bungie’s Marathon-specific networking article covers reconnect behavior and the limited conditions for a gear return. Its detailed latency and router guidance is written for Destiny, not Marathon. The latter can inform cautious general network checks, but it is not a Marathon-specific error-code guide or guarantee of a fix.
If you crash or disconnect during a run
Bungie’s Marathon Dev Team says that after a crash or disconnect, your shell remains in the game world and your crew may protect it while you are away. The intended recovery path is to relaunch Marathon and attempt to reconnect to that shell. If your connection itself appears to have dropped, restoring it before relaunching may help you make that attempt.
#1 Best Overall
- Blazing-fast WiFi 7 boosts tri-band throughput up to 12000 Mbps with 320 MHz channels of 6 GHz band, Multi-Link Operation (MLO) and 4K-QAM
- Powerful wired network capacity of up to 20G with one 2.5G WAN port and seven 2.5G LAN ports.
- High-performance quad-core 2.0GHz CPU with robust cooling, 2GB RAM and eight internal antennas providing up to 3000 sq. ft. of range.
- Smart Home Master makes it easy to set up functional subnetwork (up to 3 SSIDs) for IoT devices and VPNs
- ROG-exclusive Gaming Network streamlines Triple-Level Game Acceleration setup and connections through convenient SSIDs
- Restore a working connection. If your device has lost network access, reconnect it before starting the game again. This is a practical prerequisite for a reconnect attempt, not a promise that every interruption can be recovered.
- Relaunch Marathon. Return to the game and look for the available way to rejoin the interrupted run. The published networking article describes the reconnect path but does not provide a platform-by-platform menu walkthrough.
- Attempt to reconnect to your shell. Your shell remains in the world according to Bungie, and your crew can protect it. The crew’s ability to protect it is not a guarantee that the shell will remain safe in every situation.
- If reconnection fails, record what happened. Note whether the game crashed or closed normally, when the failure occurred, what error appeared, and whether other devices or services also lost connectivity. These details help distinguish a game failure from a broader connection problem when seeking help.
Do not assume that reconnecting—or being unable to reconnect—automatically entitles you to restored gear. Bungie says it will attempt to return starting gear for a subset of errors involving Bungie’s server or network infrastructure. The policy excludes losses due to internet connectivity and client-side problems, and it does not promise a return for every crash or disconnect. See Bungie’s Marathon: Networking and Security article for the stated conditions.
Diagnose lag: latency is not the same as packet loss
Lag is the player-facing symptom of delay between an action and a response from the server. High latency means data takes too long to travel; packet loss means some data fails to arrive. Either can make play feel unstable, and they can happen together. A connection may also work well for a brief speed test yet suffer intermittent problems during a match.
Rank #2
- Beyond-fast WiFi 7 (802.11be) with new 320MHz channels in the 6 GHz band and 4096-QAM significantly increases network capacity and throughput, with speeds of up to 30 Gbps
- Multi-link Operation links to multiple bands at the same time to ensure stable internet connections and efficient data transfers
- Cutting-edge external dual-feeding antennas boost coverage by providing high efficiency and significantly enhanced signal strength
- Maximized wired connectivity and flexibility with dual 10G ports and quad 2.5G ports
- Triple-Level Game Acceleration - The GT-BE98 Pro boosts your PC gaming traffic every step of the way, from your PC gaming port all the way to the game server.
Bungie’s explanation of latency and packet loss is in a Destiny support article, so treat its factors and suggestions below as general diagnostic guidance rather than Marathon-specific instructions. Bungie lists congestion, Wi-Fi instability, geographic distance, older hardware or firmware, and possibly damaged hardware among potential contributors. None of those factors alone diagnoses a particular Marathon player’s problem.
Run low-risk checks first
- Reduce competing network traffic. Pause large downloads, streaming, or other heavy network activity on your home connection, then see whether the symptom changes. This is a diagnostic comparison, not proof that the other traffic was the sole cause.
- Compare Wi-Fi with Ethernet if feasible. Try a wired connection for a session or other comparable test. Bungie’s Destiny guide recommends wired Ethernet as a way to help rule out Wi-Fi signal strength or stability. If the issue improves, Wi-Fi may be contributing; it does not establish a specific router fault.
- Check that network equipment is current and functioning. Review the router or modem maker’s normal process for firmware updates and check for obvious equipment or cable problems. Bungie’s Destiny material identifies older firmware and damaged hardware as possible factors; it does not provide Marathon-specific equipment settings.
- Compare another device or service cautiously. If several devices lose connectivity at once, the problem may be local or with the internet provider. If other apps appear normal, intermittent loss or a route-specific issue can still affect a game connection. A single successful speed test does not rule those out.
For background on these general factors, consult Bungie Help’s Optimizing Connections: Improving Latency and Packet Loss. It is explicitly Destiny guidance; it should not be read as a Marathon port list, error-code reference, or guarantee that a particular change will resolve the issue.
Rank #3
- 𝐅𝐮𝐭𝐮𝐫𝐞-𝐑𝐞𝐚𝐝𝐲 𝐖𝐢-𝐅𝐢 𝟕 - Designed with the latest Wi-Fi 7 technology, featuring Multi-Link Operation (MLO), Multi-RUs, and 4K-QAM. Achieve optimized performance on latest WiFi 7 laptops and devices, like the iPhone 16 Pro, and Samsung Galaxy S24 Ultra.
- 𝟔-𝐒𝐭𝐫𝐞𝐚𝐦, 𝐃𝐮𝐚𝐥-𝐁𝐚𝐧𝐝 𝐖𝐢-𝐅𝐢 𝐰𝐢𝐭𝐡 𝟔.𝟓 𝐆𝐛𝐩𝐬 𝐓𝐨𝐭𝐚𝐥 𝐁𝐚𝐧𝐝𝐰𝐢𝐝𝐭𝐡 - Achieve full speeds of up to 5764 Mbps on the 5GHz band and 688 Mbps on the 2.4 GHz band with 6 streams. Enjoy seamless 4K/8K streaming, AR/VR gaming, and incredibly fast downloads/uploads.
- 𝐖𝐢𝐝𝐞 𝐂𝐨𝐯𝐞𝐫𝐚𝐠𝐞 𝐰𝐢𝐭𝐡 𝐒𝐭𝐫𝐨𝐧𝐠 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧 - Get up to 2,400 sq. ft. max coverage for up to 90 devices at a time. 6x high performance antennas and Beamforming technology, ensures reliable connections for remote workers, gamers, students, and more.
- 𝐔𝐥𝐭𝐫𝐚-𝐅𝐚𝐬𝐭 𝟐.𝟓 𝐆𝐛𝐩𝐬 𝐖𝐢𝐫𝐞𝐝 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 - 1x 2.5 Gbps WAN/LAN port, 1x 2.5 Gbps LAN port and 3x 1 Gbps LAN ports offer high-speed data transmissions.³ Integrate with a multi-gig modem for gigplus internet.
- 𝐎𝐮𝐫 𝐂𝐲𝐛𝐞𝐫𝐬𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐂𝐨𝐦𝐦𝐢𝐭𝐦𝐞𝐧𝐭 - TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
Work out which part of the connection may be responsible
Use the pattern of failures to choose what to check next, not as a definitive diagnosis. The same visible error can have different causes, and the available Marathon-specific materials do not map every error to a cause.
| Possible source | Clues worth checking | What the evidence establishes |
|---|---|---|
| Local Wi-Fi or home network | Whether a wired comparison changes the symptoms; whether other devices on the same connection have trouble; whether local equipment appears unstable. | Bungie’s Destiny networking guidance identifies Wi-Fi, congestion, older firmware, and damaged hardware as possible contributors. These are general clues, not a Marathon diagnosis. |
| ISP or internet path | Whether repeated problems persist after basic local checks; whether the connection looks normal at a glance despite intermittent game errors. | In a June 2026 forum exchange about a Marathon player report, Bungie Help said local hardware, packet loss, or ISP-level problems could be involved even if the connection seemed fine at a glance. That response does not identify the cause for every player. |
| Bungie-side service or infrastructure | Whether the failure is associated with a server or infrastructure error, rather than only a local connection symptom. | Bungie’s Marathon article says starting-gear returns apply to a subset of server- or network-infrastructure errors. It does not establish that any particular disconnect was Bungie-side. |
| Matchmaking state or game client | Whether the selected queue differs from the queue you enter, or a match fails to start despite an apparently working connection. | Bungie’s July 2026 update documents a past Solo Queue state bug and its fix. It does not prove that the bug is recurring now. |
The comparison is useful because it prevents a common troubleshooting dead end: changing router settings when the issue is a queue-state bug, or assuming a server failure because one match did not start. Change one variable at a time where possible, and note whether that test actually changes the symptom.
Rank #4
- Tri-band 2.4GHz + 5GHz + 6GHz; latest WiFi 6E supports 8-streams on tri-band simultaneously, up to 6.6Gbps speed
- AI QoS; satisfies all users' needs by automatically prioritizing data packets
- Powerful processor; 1.8 GHz quad core processor delivers ultra fast and reliable connections
- Mystic light; sync RGB light effects with mystic light compatible products
- Game accelerator; provides an uninterrupted WiFi connection for immersive gaming experiences
If Solo Queue or matchmaking selects the wrong mode
Bungie’s Marathon Update 1.1.0.5, dated July 9, 2026, says Bungie fixed a problem where selecting Solo Queue could fail to update matchmaking state. Players could consequently remain in a different queue or unexpectedly end up in a crew-based queue.
This is a documented historical bug and fix, not evidence that the same issue is currently recurring. If your selection and resulting queue do not match, check current Marathon patch notes or Bungie support announcements for newer information. If no current notice explains it, record the selected mode, what queue the game entered, and whether the problem repeats; do not assume that changing your router will correct a matchmaking-state problem.
Best Value
- DUAL-BAND WIFI 6 ROUTER: Wi-Fi 6(802.11ax) technology achieves faster speeds, greater capacity and reduced network congestion compared to the previous gen. All WiFi routers require a separate modem. Dual-Band WiFi routers do not support the 6 GHz band.
- AX1800: Enjoy smoother and more stable streaming, gaming, downloading with 1.8 Gbps total bandwidth (up to 1200 Mbps on 5 GHz and up to 574 Mbps on 2.4 GHz). Performance varies by conditions, distance to devices, and obstacles such as walls.
- CONNECT MORE DEVICES: Wi-Fi 6 technology communicates more data to more devices simultaneously using revolutionary OFDMA technology
- EXTENSIVE COVERAGE: Achieve the strong, reliable WiFi coverage with Archer AX1800 as it focuses signal strength to your devices far away using Beamforming technology, 4 high-gain antennas and an advanced front-end module (FEM) chipset
- OUR CYBERSECURITY COMMITMENT: TP-Link is a signatory of the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Secure-by-Design pledge. This device is designed, built, and maintained, with advanced security as a core requirement.
When connection errors keep returning
If basic comparisons do not resolve recurring disconnects, collect details that make the problem easier to describe: the time and frequency, whether it happens during matchmaking or a run, the exact error text if shown, and the results of any wired or other-device comparison. Avoid treating a passing speed test as proof that intermittent packet loss is absent.
In a June 2026 Bungie Help forum exchange about a player reporting repeated Marathon server errors and disconnects, Bungie Help pointed to possible local hardware, packet loss, or ISP-level issues, recommended Bungie’s networking material, and advised contacting the ISP if problems persisted. That is support guidance in response to one report, not a Marathon-specific error-code playbook or a diagnosis of your connection. You can review the exchange at Bungie.net Help Forums: “Constant server errors and disconnects”.
When contacting your ISP, describe the recurring timing and symptoms and the checks you already made; ask whether they can investigate intermittent packet loss or connection instability. If you contact Bungie support, include the same observations and the exact error message rather than guessing that a particular component is responsible.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchDo not apply Destiny router instructions to Marathon by assumption
Bungie’s Network Troubleshooting Guide covers Destiny, including advanced topics such as UPnP, port forwarding, and NAT troubleshooting. The Marathon-specific materials cited here do not establish Marathon port numbers, platform-specific network settings, or a current Marathon error-code troubleshooting table. Do not copy Destiny port-forwarding rules into a Marathon setup on that basis alone.
Advanced router changes can affect other devices and services, so use only settings Bungie has verified for Marathon or your platform and router makers have documented for your equipment. If you cannot confirm the relevant Marathon-specific details, stick to the low-risk connection comparisons above and seek support rather than guessing at ports or NAT changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
