I boot Marathon, punch the login button, and the number on my screen barely creeps forward. You check the clock, then the queue again, and the frustration settles in. For a few minutes you are alone with the slow creep of progress and the question: will I get in?
I’ve tracked server tests and stress events across multiple Bungie launches. I’ll tell you what’s happening, why it’s happening now, and what actually improves your odds of getting into a match sooner.
You hit login and the counter climbs: Why is there a queue to play Marathon?
Short answer: lots of people trying to log in at once. That surge is expected when servers finish maintenance or when a new patch drops and players flood back. The Server Slam open beta is precisely that event — a stress test pegged to times when traffic spikes.
The Server Slam window runs from Thursday, Feb. 26 at 12pm CT to Monday, March 2 at 12pm CT. Bungie described it as a technical stress test: they are opening everything worldwide, inviting as many players as possible, and watching what breaks under pressure.
The login queue acts as a throttling gate. The login queue is a traffic light on a freeway at rush hour — it may slow you, but it keeps the whole system from crashing.
How long will the queue last?
There’s no fixed number. Queues shorten as peak demand fades and Bungie spins up extra capacity. Peak hours — evenings in North America and Europe — will stretch waits. Outside those windows you’ll usually move faster.
Can I skip the queue in Marathon?
No reliable bypass exists. Attempts to spoof regions, spam reconnects, or use multiple accounts often backfire and can reset your spot. Your best move is patience and timing: try off-peak hours or wait until maintenance notices say capacity has increased.
Your screen reports throttling and a freeze-frame error: Marathon – Login services ‘currently being throttled’
During the 2025 closed alpha, players saw the message that login services were being throttled. The screen asked people to remain on it until services stabilized — and the queue eventually cleared. That message is a defensive move by Bungie to prevent cascading failures.
If the queue completes and you still face disconnects or error codes, you may be forced to rejoin the line. That’s the cost of stress testing at scale. Bungie has handled long queues for Destiny 2 for years, so the team is familiar with the failure modes and remedies.
I recommend following official status channels for the fastest updates: the Marathon dev account and server-status feeds on X (Twitter) such as @MarathonDevTeam and @BNGServerStatus. Those accounts tell you when capacity has been increased or when maintenance will close access.
When the servers strain, they behave like a pressure cooker releasing steam — you’ll see throttles, short outages, and scheduled pullbacks while engineers add headroom.
Stay calm, pick your timing, and keep an eye on official channels — or do you think you’ll rage-quit and demand instant access right now?