Question Help with routing issues regarding valorant

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
 
It really depends where you are. Find the closest Riot server and run a tracert command with the IP address in a command prompt. For example 104.160.151.182 is in Dallas and I reach it in 6 hops with low latency, that's about 200 miles from me.

I got that address with a tracert to the main US server address: 104.160.131.3 and it listed a couple near me by IP address. This will give you a pretty good idea if it is your ISP or Riot, but I expect that your ISP may be the issue.
 
It would not be uncommon for a game company to prevent ping with their firewalls. Too many so called "competitive" gamers living in moms basement attempt denial of service attacks against game companies.

You can verify the "routing" with a tracert command to the servers. You will be able to easily tell if it actually leaves your ISP.

It is likely a tech that doesn't know what he is talking about. It would imply that your ISP did not have a data interchange agreement with one of the multiple ISP riot uses.

Not something that happens any more...maybe 20 years ago all isp were not interconnected but now the worst that happens is you might have a slow/longer latency connection than one that takes the shortest path.

It all doesn't matter you can do nothing at all about the routing on the internet. Your only option is to send and receive data on the wire that comes to your house. Anything past that is completely out of your control.
 
1 ms <1 ms <1 ms
2 37 ms 37 ms 37 ms 184-102-32-254.crls.qwest.net [184.102.32.254]
3 37 ms 37 ms 36 ms crls-agw1.inet.qwest.net [75.160.220.225]
4 40 ms 67 ms 55 ms 4.68.127.210
5 * * * Request timed out.
6 41 ms 42 ms 42 ms RIOT-GAMES.bear1.Washington111.Level3.net [4.14.103.174]
7 106 ms 106 ms 106 ms ae3.er02.chi01.riotdirect.net [104.160.159.126]
8 101 ms 100 ms 108 ms ae2.er02.lax01.riotdirect.net [104.160.159.186]
9 100 ms 100 ms 100 ms ae1.er01.lax01.riotdirect.net [104.160.151.134]
10 100 ms 100 ms 100 ms 104.160.141.51
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * *
a traceart ran to their man servers
It really depends where you are. Find the closest Riot server and run a tracert command with the IP address in a command prompt. For example 104.160.151.182 is in Dallas and I reach it in 6 hops with low latency, that's about 200 miles from me.

I got that address with a tracert to the main US server address: 104.160.131.3 and it listed a couple near me by IP address. This will give you a pretty good idea if it is your ISP or Riot, but I expect that your ISP may be the issue.
It would not be uncommon for a game company to prevent ping with their firewalls. Too many so called "competitive" gamers living in moms basement attempt denial of service attacks against game companies.

You can verify the "routing" with a tracert command to the servers. You will be able to easily tell if it actually leaves your ISP.

It is likely a tech that doesn't know what he is talking about. It would imply that your ISP did not have a data interchange agreement with one of the multiple ISP riot uses.

Not something that happens any more...maybe 20 years ago all isp were not interconnected but now the worst that happens is you might have a slow/longer latency connection than one that takes the shortest path.

It all doesn't matter you can do nothing at all about the routing on the internet. Your only option is to send and receive data on the wire that comes to your house. Anything past that is completely out of your control.
 
1 ms <1 ms <1 ms
2 37 ms 37 ms 37 ms 184-102-32-254.crls.qwest.net [184.102.32.254]
3 37 ms 37 ms 36 ms crls-agw1.inet.qwest.net [75.160.220.225]
4 40 ms 67 ms 55 ms 4.68.127.210
5 * * * Request timed out.
6 41 ms 42 ms 42 ms RIOT-GAMES.bear1.Washington111.Level3.net [4.14.103.174]
7 106 ms 106 ms 106 ms ae3.er02.chi01.riotdirect.net [104.160.159.126]
8 101 ms 100 ms 108 ms ae2.er02.lax01.riotdirect.net [104.160.159.186]
9 100 ms 100 ms 100 ms ae1.er01.lax01.riotdirect.net [104.160.151.134]
10 100 ms 100 ms 100 ms 104.160.141.51
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * *
a traceart ran to their man servers
also valorant was working very well before it just randomly stopped working
 
The issue is clearly in riots network. The second problem you have is they might be block trace and ping with their firewalls so it may not represent the actual reason the game does not work. Hard to say you are actually going to have to call and ask riot what is going on. Maybe they banned the IP you running on, not sure if they are dumb enough to try to ban IP addresses. Even if you didn't do anything someone else might have and your IP will change from time to time so you could get the IP that has the ban. That is why it is a dumb idea to do IP bans.
You could try a vpn.
 
The issue is clearly in riots network. The second problem you have is they might be block trace and ping with their firewalls so it may not represent the actual reason the game does not work. Hard to say you are actually going to have to call and ask riot what is going on. Maybe they banned the IP you running on, not sure if they are dumb enough to try to ban IP addresses. Even if you didn't do anything someone else might have and your IP will change from time to time so you could get the IP that has the ban. That is why it is a dumb idea to do IP bans.
You could try a vpn.
already tried a vpn and it didn't work
 
If it doesn't work on a VPN then it almost has to be something with your account or some issue with the program on your machine. When you use a vpn you in effect are changing your ISP. The traffic goes to the vpn company data center using your ISP but the IP address is then changed and your traffic then appears as if you live in the VPN companies data center and your traffic appears to come from whoever they use for their ISP traffic. It is almost like you put your pc into a car and drove over to the VPN companies office. When you have the same failure on 2 different networks it can't really be a network issue.
 
If it doesn't work on a VPN then it almost has to be something with your account or some issue with the program on your machine. When you use a vpn you in effect are changing your ISP. The traffic goes to the vpn company data center using your ISP but the IP address is then changed and your traffic then appears as if you live in the VPN companies data center and your traffic appears to come from whoever they use for their ISP traffic. It is almost like you put your pc into a car and drove over to the VPN companies office. When you have the same failure on 2 different networks it can't really be a network issue.
I've reinstalled it like 4 times so it's not the program
 
In Valorent have you tried the server select function that came in with patch 1.10? If you are in Pennsylvania, there seem to some closer or perhaps less trafficked than LA:
  • US West (Oregon)
  • US West (N. California)
  • US East (N. Virginia)
  • US Central (Texas)
  • US Central (Illinois)
  • US Central (Georgia)
the game doesn't open it gets stuck on the opening screen and the sound plays but it doesn't go to the menu
 
If it doesn't work on a VPN then it almost has to be something with your account or some issue with the program on your machine. When you use a vpn you in effect are changing your ISP. The traffic goes to the vpn company data center using your ISP but the IP address is then changed and your traffic then appears as if you live in the VPN companies data center and your traffic appears to come from whoever they use for their ISP traffic. It is almost like you put your pc into a car and drove over to the VPN companies office. When you have the same failure on 2 different networks it can't really be a network issue.
In Valorent have you tried the server select function that came in with patch 1.10? If you are in Pennsylvania, there seem to some closer or perhaps less trafficked than LA:
  • US West (Oregon)
  • US West (N. California)
  • US East (N. Virginia)
  • US Central (Texas)
  • US Central (Illinois)
  • US Central (Georgia)
traceart of a vpn in new york
Tracing route to 104.160.131.3 over a maximum of 30 hops

1 583 ms 409 ms 490 ms 10.2.0.1
2 418 ms 318 ms 915 ms unn-138-199-52-205.datapacket.com [138.199.52.205]
3 469 ms 239 ms 273 ms vl213.nyc-tlx3-core-1.cdn77.com [169.150.194.90]
4 360 ms 329 ms * vl1107.fra-eq5-edge-1.cdn77.com [138.199.0.97]
5 401 ms 563 ms 517 ms vl1101.par-itx5-core-2.cdn77.com [185.229.188.6]
6 534 ms 475 ms * stc-par.cdn77.com [84.17.32.101]
7 * * * Request timed out.
8 282 ms 310 ms 325 ms 178.86.50.103
9 357 ms 484 ms * ae5.er02.cai01.riotdirect.net [104.160.154.21]
10 265 ms 497 ms 267 ms ae4.er02.mil01.riotdirect.net [104.160.154.17]
11 291 ms 265 ms 265 ms ae1.er01.mil01.riotdirect.net [104.160.151.222]
12 293 ms 282 ms 293 ms ae11.er01.fra02.riotdirect.net [104.160.151.234]
13 369 ms 288 ms 427 ms ae14.er01.ams02.riotdirect.net [104.160.159.156]
14 1657 ms 458 ms 490 ms ae1.er02.ams02.riotdirect.net [104.160.151.147]
15 307 ms 438 ms 512 ms ae2.er01.lon01.riotdirect.net [104.160.151.207]
16 487 ms 523 ms 382 ms ae1.er02.lon01.riotdirect.net [104.160.151.159]
17 277 ms 289 ms 298 ms ae12.er02.nyc01.riotdirect.net [104.160.159.104]
18 282 ms 463 ms 472 ms ae1.er01.nyc01.riotdirect.net [104.160.143.250]
19 321 ms 268 ms 274 ms ae6.er01.chi01.riotdirect.net [104.160.159.136]
20 291 ms 319 ms 353 ms ae1.er02.chi01.riotdirect.net [104.160.143.91]
21 447 ms 381 ms 596 ms ae2.er02.lax01.riotdirect.net [104.160.159.186]
22 352 ms 352 ms 365 ms ae1.er01.lax01.riotdirect.net [104.160.151.134]
23 319 ms 372 ms * 104.160.141.51
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
 
traceart of a vpn in new york
Tracing route to 104.160.131.3 over a maximum of 30 hops

1 583 ms 409 ms 490 ms 10.2.0.1
2 418 ms 318 ms 915 ms unn-138-199-52-205.datapacket.com [138.199.52.205]
3 469 ms 239 ms 273 ms vl213.nyc-tlx3-core-1.cdn77.com [169.150.194.90]
4 360 ms 329 ms * vl1107.fra-eq5-edge-1.cdn77.com [138.199.0.97]
5 401 ms 563 ms 517 ms vl1101.par-itx5-core-2.cdn77.com [185.229.188.6]
6 534 ms 475 ms * stc-par.cdn77.com [84.17.32.101]
7 * * * Request timed out.
8 282 ms 310 ms 325 ms 178.86.50.103
9 357 ms 484 ms * ae5.er02.cai01.riotdirect.net [104.160.154.21]
10 265 ms 497 ms 267 ms ae4.er02.mil01.riotdirect.net [104.160.154.17]
11 291 ms 265 ms 265 ms ae1.er01.mil01.riotdirect.net [104.160.151.222]
12 293 ms 282 ms 293 ms ae11.er01.fra02.riotdirect.net [104.160.151.234]
13 369 ms 288 ms 427 ms ae14.er01.ams02.riotdirect.net [104.160.159.156]
14 1657 ms 458 ms 490 ms ae1.er02.ams02.riotdirect.net [104.160.151.147]
15 307 ms 438 ms 512 ms ae2.er01.lon01.riotdirect.net [104.160.151.207]
16 487 ms 523 ms 382 ms ae1.er02.lon01.riotdirect.net [104.160.151.159]
17 277 ms 289 ms 298 ms ae12.er02.nyc01.riotdirect.net [104.160.159.104]
18 282 ms 463 ms 472 ms ae1.er01.nyc01.riotdirect.net [104.160.143.250]
19 321 ms 268 ms 274 ms ae6.er01.chi01.riotdirect.net [104.160.159.136]
20 291 ms 319 ms 353 ms ae1.er02.chi01.riotdirect.net [104.160.143.91]
21 447 ms 381 ms 596 ms ae2.er02.lax01.riotdirect.net [104.160.159.186]
22 352 ms 352 ms 365 ms ae1.er01.lax01.riotdirect.net [104.160.151.134]
23 319 ms 372 ms * 104.160.141.51
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
another tracert of my connection to the N virgina servers which is what i would play on if i could play the game
Tracing route to 192.207.0.1 over a maximum of 30 hops
1 1 ms <1 ms <1 ms
2 155 ms 195 ms 111 ms 184-102-32-254.crls.qwest.net [184.102.32.254]
3 41 ms 42 ms 57 ms crls-agw1.inet.qwest.net [75.160.220.225]
4 54 ms 50 ms 55 ms 4.68.127.210
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26
 
That is very bizzare. You seem to have picked the worst vpn you could have.
The latency is crazy high even to the first hop. This has damaged the latency so bad it is hard to tell what it really is. This might be a vpn software client issue.

At first I figured you picked a vpn site in say austrailia but the first ip that resolves in hop 2 does appear to be in newyork.

It though is extremely strange. None of the other sites will respond to me and I can't get locations on them until we get to RIOT.

9 357 ms 484 ms * ae5.er02.cai01.riotdirect.net [104.160.154.21]

At first I look and said that can't be cairo, a lot of vendors use airport codes in their router names. After some checking on latency from my house that router does appear to be in cairo egypt. I get 220ms from my house to that router.

So why would the vpn you are using connect to riots network in egypt rather then in new york.

In any case I would ignore any of these vpn results something is even more messed up.
 
  • Like
Reactions: RealBeast
That is very bizzare. You seem to have picked the worst vpn you could have.
The latency is crazy high even to the first hop. This has damaged the latency so bad it is hard to tell what it really is. This might be a vpn software client issue.

At first I figured you picked a vpn site in say austrailia but the first ip that resolves in hop 2 does appear to be in newyork.

It though is extremely strange. None of the other sites will respond to me and I can't get locations on them until we get to RIOT.

9 357 ms 484 ms * ae5.er02.cai01.riotdirect.net [104.160.154.21]

At first I look and said that can't be cairo, a lot of vendors use airport codes in their router names. After some checking on latency from my house that router does appear to be in cairo egypt. I get 220ms from my house to that router.

So why would the vpn you are using connect to riots network in egypt rather then in new york.

In any case I would ignore any of these vpn results something is even more messed up.
the latency could be due to my internet just being really <Mod Edit> it goes worse when it rains and it has been raining for like 2 days. Is there anything else I should try?
 
Last edited by a moderator:
the latency could be due to my internet just being really <Mod Edit> it goes worse when it rains and it has been raining for like 2 days. Is there anything else I should try?
im actually at a loss lol, ive called my isp my 20 times and its always someone who doesnt know what their doing that either says they cant do anything or they just hang up
 
im actually at a loss lol, ive called my isp my 20 times and its always someone who doesnt know what their doing that either says they cant do anything or they just hang up
also the tracert to 192.207.0.1 also says request timed out at hop 5


1 <1 ms <1 ms <1 ms
2 119 ms 156 ms 191 ms 184-102-32-254.crls.qwest.net [184.102.32.254]
3 156 ms 170 ms 196 ms crls-agw1.inet.qwest.net [75.160.220.225]
4 180 ms 148 ms 172 ms 4.68.127.210
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
 
also the tracert to 192.207.0.1 also says request timed out at hop 5


1 <1 ms <1 ms <1 ms
2 119 ms 156 ms 191 ms 184-102-32-254.crls.qwest.net [184.102.32.254]
3 156 ms 170 ms 196 ms crls-agw1.inet.qwest.net [75.160.220.225]
4 180 ms 148 ms 172 ms 4.68.127.210
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
the 4.68 ip seems to be the issue
 
Turns out your ISP is not a tiny ISP. It is somewhat unclear what parts were sold when brightspeed was created/renamed.
Brightspeed is actually a combination of a bunch of fairly major ISP. Level3 being the largest. They also acquired century link as well as qwest. They used to be called luman.

So riotgames actually uses level 3 as their major provider of ISP servers. This link show the ISP the peer with. Many are international ISP.

https://bgp.he.net/AS6507

What this means is your ISP directly sells service to Riotgames. It is obviously a completely different division than the one that run your house.

So this tool lets you actually issue some commands from the routers in your ISP network (ie level3). Note you will get a warning because they are using HTTP rather than HTTPS. It is not a security issue unless you are going to type something other than IP addresses into their web page.


I ran a tracert from their router in washington dc. You will notice it matches your trace exactly starting in hop 6. I suspect the router in hop 5 of your trace is actually the router I ran the trace from.

WASHINGTON DC USA Traceroute results for: 104.160.131.3 (104.160.131.3)

Tracing route to 104.160.131.3 1 0.0.0.0 (0.0.0.0) * * *
2 RIOT-GAMES.bear1.Washington111.Level3.net (4.14.103.174) 1ms 1ms 1ms
3 ae3.er02.chi01.riotdirect.net (104.160.159.126) 60ms 60ms 60ms
4 ae2.er02.lax01.riotdirect.net (104.160.159.186) 60ms 60ms 60ms
5 ae1.er01.lax01.riotdirect.net (104.160.151.134) 59ms 59ms 60ms
6 104.160.141.51 (104.160.141.51) 57ms 57ms 57ms
7 0.0.0.0 (0.0.0.0) * * *
8 0.0.0.0 (0.0.0.0) * * *

=======================================


You can play around with some more traces from other locations but I am not sure what you can do.

I strongly suspect this is a firewall in riotgames network blocking the traffic. It just means the tracert tools are not valid test tools to determine why something doesn't work. Your traffic obviously can get deep into riots network.

I seriously doubt there is any major routing issue between riotgames and their largest internet provider.
 
Turns out your ISP is not a tiny ISP. It is somewhat unclear what parts were sold when brightspeed was created/renamed.
Brightspeed is actually a combination of a bunch of fairly major ISP. Level3 being the largest. They also acquired century link as well as qwest. They used to be called luman.

So riotgames actually uses level 3 as their major provider of ISP servers. This link show the ISP the peer with. Many are international ISP.

https://bgp.he.net/AS6507

What this means is your ISP directly sells service to Riotgames. It is obviously a completely different division than the one that run your house.

So this tool lets you actually issue some commands from the routers in your ISP network (ie level3). Note you will get a warning because they are using HTTP rather than HTTPS. It is not a security issue unless you are going to type something other than IP addresses into their web page.


I ran a tracert from their router in washington dc. You will notice it matches your trace exactly starting in hop 6. I suspect the router in hop 5 of your trace is actually the router I ran the trace from.

WASHINGTON DC USA Traceroute results for: 104.160.131.3 (104.160.131.3)

Tracing route to 104.160.131.3 1 0.0.0.0 (0.0.0.0) * * *
2 RIOT-GAMES.bear1.Washington111.Level3.net (4.14.103.174) 1ms 1ms 1ms
3 ae3.er02.chi01.riotdirect.net (104.160.159.126) 60ms 60ms 60ms
4 ae2.er02.lax01.riotdirect.net (104.160.159.186) 60ms 60ms 60ms
5 ae1.er01.lax01.riotdirect.net (104.160.151.134) 59ms 59ms 60ms
6 104.160.141.51 (104.160.141.51) 57ms 57ms 57ms
7 0.0.0.0 (0.0.0.0) * * *
8 0.0.0.0 (0.0.0.0) * * *

=======================================


You can play around with some more traces from other locations but I am not sure what you can do.

I strongly suspect this is a firewall in riotgames network blocking the traffic. It just means the tracert tools are not valid test tools to determine why something doesn't work. Your traffic obviously can get deep into riots network.

I seriously doubt there is any major routing issue between riotgames and their largest internet provider.
well from what i have found out i called lumen which owns the 75.160.220.225 ip and the hop after that enters brightspeeds network and the guy from lumen said it would be an issue with one of their servers so i am waiting for a call back from one of brightspeeds higher up people that can do routing so we will see how that goes
 
well from what i have found out i called lumen which owns the 75.160.220.225 ip and the hop after that enters brightspeeds network and the guy from lumen said it would be an issue with one of their servers so i am waiting for a call back from one of brightspeeds higher up people that can do routing so we will see how that goes
also brightspeed is more of a banner name as the companies arent connected persay as some of century links servers are owned by lumen now.
 
Status
Not open for further replies.