Question Help with routing issues regarding valorant

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Jan 3, 2024
45
0
30
so i have a very sucky ISP brightspeed and throughout the past few months ive had many issues with them and the last time my internet was not working for no reason valorant stopped working, and after they fixed it valorant has stopped working and valorant support says it is a routing issue with my isp and when i contacted my isp they said it is out of their realm and i have no idea what to do. im not exactly sure what info to provide but i am desperate for help so if you have any questions ask thanks in advance
 
Noted. You are not getting the point of trying to isolate your ISP out of the equation.

Good luck.
I get the point I just can't what so ever my computer does not have a wifi card all my friends and family use the same isp I live in the middle of no where with 1 isp and no cell service
 
The guy at valorant is a idiot.....or more accurately he is a customer services rep for a game company. If he had the network knowledge to understand what he actually said to do he would likely make 3 or 4 times the money he does a network engineer.
The ISP guy answer is much more accurate.

Go look up what CCIE means. I held that cert for more than 15 years and only let it go when I retired. I am telling you the routing between your ISP and RIOT is fine. There is no problem until it enters the riot network.
There really is nothing your ISP can change that will affect the path inside the riot network. Even if they could the way companies and ISP interconenct is not purely a technically issue. To get changes made they need to get the lawyers involved. Typing the in the commands to actually change routing is the trivial part. When I used to do this type of thing we would scope out the technical change and then hear nothing for 6 months before we got approval to actually do something.

Although you tried a vpn I would try a different one. Try one of the big ones like nord where you have many different data centers to try. Your goal here is to try to get a different path between your house and riots network.
just a few questions and hypotheticals. for one its always a different agent responding to my emails and the only thing they tell me to do. but hypothetically if it was truly a routing issue couldn't riot figure out a way to contact my isp. also another issue I have with this whole situation is how come a vpn isn't working I used nord vpn from several different states and still only got to the loading screen and didn't get to the main menu. also another interesting thing which idk if it's relevent is when checking my task manager cpu gpu and ram usage seems normal like how it would be when loading the game but network is always at 0.0 mpbs well at least as far as I'm aware. it just bugs me how riot Denys my concerns and my immense effort into calling my isp it took many many phone calls and hours of talking to basic employees to even find a guy that could confirm my suspicions that it wasn't an isp issue and even after telling riot support this they keep telling me to contact my isp and for me to tell them to look at their peeringdb and to talk to a high tier agent which I did and he said it was their issue but they don't listen so at this point I'm at a loss unfortunately I can't refund all the transactions I made with the game.
 
it's not a performance issue what so ever I run the launcher then I open valorant and it gets stuck on the first loading screen even though the initial sound plays there is also no pop up saying no connection I've done everything from uninstalling all the files reinstalling, disabling all start up apps except for the ones required to play valorant I've updated drivers. and valorant support says it's a isp issue even though it's not obviously.
So I see this in the middle of the latest replies. This is kinda different issue. I guess it could be the actual game server itself but it does appear you can talk to riot servers if you even get to the first loading screan. It would be extremely strange that some servers work and others do not.

This thread is very long so I am not sure what has been tried and what has not. This is what a windows firewall issue looks like when it thinks you are on a public network. I would first try to disable the windows firewall temporarily. The only thing that makes me doubt this is running a vpn creates a new network and windows should set it to private network.
 
So I see this in the middle of the latest replies. This is kinda different issue. I guess it could be the actual game server itself but it does appear you can talk to riot servers if you even get to the first loading screan. It would be extremely strange that some servers work and others do not.

This thread is very long so I am not sure what has been tried and what has not. This is what a windows firewall issue looks like when it thinks you are on a public network. I would first try to disable the windows firewall temporarily. The only thing that makes me doubt this is running a vpn creates a new network and windows should set it to private network.
I will try this but it is a very peculiar situation as at the time it stopped working there was a internet outage at my house so I can't exactly pin point when it stopped.
 
A symptom like this is where you can get to say the login server but not the game world servers. It can in theory be routing issue but you would have to dig around with something like wire shark to see exactly what ip and ports are attempting to be used.

The reason something like the windows firewall stands out is when the network is running in public mode it allows stuff like web port like 80, 443, and dns port 53 but not much else. Games tend to use other ports many times using UDP on these. So you can in general connect to the server and log into the authentication servers but can not actually play the game.

There is also a rare chance it is some kind of firewall in the router.

If you really want you could run wireshark and see exactly the IP addresses and the ports. Maybe you can talk nice to one of your friends and they can give you a capture when it works correctly.

You would then at least know if you really were using the same exact server ip.
 
A symptom like this is where you can get to say the login server but not the game world servers. It can in theory be routing issue but you would have to dig around with something like wire shark to see exactly what ip and ports are attempting to be used.

The reason something like the windows firewall stands out is when the network is running in public mode it allows stuff like web port like 80, 443, and dns port 53 but not much else. Games tend to use other ports many times using UDP on these. So you can in general connect to the server and log into the authentication servers but can not actually play the game.

There is also a rare chance it is some kind of firewall in the router.

If you really want you could run wireshark and see exactly the IP addresses and the ports. Maybe you can talk nice to one of your friends and they can give you a capture when it works correctly.

You would then at least know if you really were using the same exact server ip.
I tried disabling the firewall it didn't work and the only response I get from riot is to contact my isp even though I have alot.
 
A symptom like this is where you can get to say the login server but not the game world servers. It can in theory be routing issue but you would have to dig around with something like wire shark to see exactly what ip and ports are attempting to be used.

The reason something like the windows firewall stands out is when the network is running in public mode it allows stuff like web port like 80, 443, and dns port 53 but not much else. Games tend to use other ports many times using UDP on these. So you can in general connect to the server and log into the authentication servers but can not actually play the game.

There is also a rare chance it is some kind of firewall in the router.

If you really want you could run wireshark and see exactly the IP addresses and the ports. Maybe you can talk nice to one of your friends and they can give you a capture when it works correctly.

You would then at least know if you really were using the same exact server ip.
copy paste of what riot said past and that this is a frustrating situation to be in, but considering there are no reported server issues on our end, which you can always check on our Service Status Page and the packet loss is specific to the nodes related to 'qwest.net' this is an issue your ISP is facing on their end and is why we have to insist that they are the ones who reach out to us through the info on our PeeringDB page. Thank you for your understanding.
 
Status
Not open for further replies.