Valorant 59

On screen: LoginQueueFetchTokenFailure

What it actually means

The client could not fetch a token from the login queue. The queue is the mechanism Riot uses to meter sign-ins under load, so this code is a direct symptom of that load.

Riot specifically clarifies that this one is VAL 59, the game's error, rather than VAN 59 in their Vanguard registry — they use it as their own example of why the two registries get confused.

It clusters after patch deployments and during peak hours, which makes it one of the better early signals that Valorant's login is struggling.

How to tell which one you have

If several players in your region hit it within the same few minutes, it is the queue and not you. The live status above and Riot's banners will usually confirm within the hour.

Fixes, in the order worth trying

1. Wait five to ten minutes, then try once — The queue drains. This is the fix.
2. Do not restart repeatedly — Each new attempt puts you at the back of the queue. Hammering the client is actively counterproductive for this specific code, which is the opposite of the advice given for most errors.
3. Check Riot's banners — Login queue problems are the kind Riot posts about.

Operator documentation: support.riotgames.com. Riot's Valorant list carries their own out-of-date banner, and their Vanguard registry uses VAL 59 as the example when explaining the difference between the two namespaces.

Common questions