There’s a new Valorant error in town and it’s been bugging many players. Meet Valorant error 136, an error code that randomly pops up kicking players midgame and prompting them to restart the game client.
Many players lost competitive matches due to this error but what’s even more frustrating is that there is really not much information about it.
For some players, restarting the game client worked. However, for many more gamers restarting the game didn’t help at all and they kept on getting error 136 or error 84 for that matter.
What’s even more frustrating is that error 136 disconnects players midgame although there is nothing wrong with their Internet connection. On the contrary, they have a blazing fast connection that works perfectly for playing other games or streaming video content.
As you can see, error 136 does not indicate there’s something wrong with your home network. It seems this is a server-side error.
Riot Games recently acknowledged a similar problem but they did not mention any particular error code:
We’re aware of a problem causing players to disconnect from their games and are investigating the problem.
And they also confirmed they’re working on fixing it.
Just with any server errors, if you’re sure your Internet connection is working properly and you already restarted your modem and computer, all you can do is wait until Riot has fixed their server problems.
We hope error 136 won’t rear its ugly head again any time soon. Meanwhile, be patient, Riot is working on a hotfix.
⇒ These troubleshooting guides may come in handy:
Due to this van-136 i got temporary ban of 5 days from valorant….due to constant crashes.
Same!!!!
Dude same
It is happening in dec wtf riot
i got banned for a whole week ;-; multiple times now ;-;
I got a month’s competitive restriction for this error.
Same 7 days ban.. its not even my fault!! And they eont unban it
I got a 100 year Ban because of this error
This is completely unfair to ban player if such error occurs cause this isn’t there issue in the first place.
Its happening again ;(
2023, and this error still occures