On screen: There was an error connecting to the platform
This one genuinely goes both ways, so the first job is telling which you are looking at.
No incidents reported. Maintenance is announced for later — see the schedule
This sentence is not a code and Riot publishes no article for it. It is the outer message that prints alongside a numbered code, and the number is where the actual information is.
It has been observed with at least codes 5, 7, 29 and 43, and those have nothing in common: one is an account being signed in elsewhere, one is a firewall blocking traffic, one is a backend timeout.
Which is why every guide that offers a fix list for this message is guessing. Without the number, the message tells you almost nothing.
Look for the code printed near the message, usually directly beneath it, and follow that instead. If there is genuinely no number, note what you were doing — signing in, joining a party, queueing — because that narrows it more than the message does.
Operator documentation: support.riotgames.com. Riot's Valorant code list is the registry for these numbers, and it currently carries their own banner saying it is out of date. Their separate Vanguard registry reuses several of the same numbers for unrelated anti-cheat failures.
This sentence is not a code and Riot publishes no article for it. It is the outer message that prints alongside a numbered code, and the number is where the actual information is.
This one genuinely goes both ways, so the first job is telling which you are looking at.
Start with: Error 5, account was logged into elsewhere. Someone signed in on another session. If it was not you, treat it as a security problem: change the password and enable multi-factor authentication before anything else.