The problem may be inside or outside of your network. Perhaps both.
Run tracert and ping via the Command Prompt targeting valorant.com
Post the results.
Here are my test results just to show you the resulting output and format.
The specific times and IP addresses will be different for your location.
============
PS C:\Users\ Username> tracert valorant.com
Tracing route to valorant.com [159.65.233.137]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms MyRouter.hsd1..........redacted.............. [192.168.1.1]
2 12 ms 11 ms 10 ms 96.120.104.105
3 11 ms 13 ms 9 ms 24.124.179.73
4 13 ms 12 ms 11 ms 68.87.128.173
5 13 ms 14 ms 15 ms ae-13-ar01............. redacted................comcast.net [68.87.168.61]
6 * * * Request timed out.
7 * 19 ms 20 ms ae-2-3602.ear4.Newark1.Level3.net [4.69.211.181]
8 20 ms 20 ms 20 ms 4.14.218.22
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 21 ms 20 ms 18 ms 159.65.233.137
Trace complete.
PS C:\Users\Username> ping valorant.com
Pinging valorant.com [159.65.233.137] with 32 bytes of data:
Reply from 159.65.233.137: bytes=32 time=20ms TTL=53
Reply from 159.65.233.137: bytes=32 time=18ms TTL=52
Reply from 159.65.233.137: bytes=32 time=17ms TTL=52
Reply from 159.65.233.137: bytes=32 time=16ms TTL=52
Ping statistics for 159.65.233.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 20ms, Average = 17ms
[Note: I ran the commands via Powershell but both commands will run via the Command Prompt.]
Recommend that you run each test several times. Vary the tests to include morning, afternoon, evening, etc. as circumstances permit.
C:\Users\pcs>tracert valorant.com
Tracing route to valorant.com [159.65.233.137]
over a maximum of 30 hops:
1 7 ms 30 ms 30 ms 192.168.254.254
2 71 ms 45 ms 62 ms 10.91.2.194
3 47 ms 62 ms 59 ms 10.205.252.178
4 59 ms 46 ms 46 ms 180.190.228.5
5 * * * Request timed out.
6 199 ms 187 ms 202 ms 120.28.0.82
7 * * * Request timed out.
8 * 310 ms 325 ms 0.ae1.BR1.LAX15.ALTER.NET [140.222.229.163]
9 313 ms * 295 ms 152.179.21.162
10 273 ms * 278 ms if-ae-55-2.tcore1.eql-losangeles.as6453.net [206.82.129.42]
11 283 ms * * if-ae-6-20.tcore2.lvw-losangeles.as6453.net [64.86.252.65]
12 265 ms * 265 ms if-ae-36-2.tcore2.aeq-ashburn.as6453.net [216.6.87.110]
13 263 ms 265 ms 265 ms if-ae-2-2.tcore1.aeq-ashburn.as6453.net [216.6.87.2]
14 * 265 ms 263 ms if-ae-30-2.tcore2.nto-newyork.as6453.net [63.243.216.20]
15 246 ms * * if-ae-12-2.tcore1.n75-newyork.as6453.net [66.110.96.5]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 260 ms 265 ms 283 ms 159.65.233.137
Trace complete.
C:\Users\pcs>ping valorant.com
Pinging valorant.com [159.65.233.137] with 32 bytes of data:
Reply from 159.65.233.137: bytes=32 time=244ms TTL=52
Reply from 159.65.233.137: bytes=32 time=277ms TTL=52
Reply from 159.65.233.137: bytes=32 time=250ms TTL=52
Reply from 159.65.233.137: bytes=32 time=278ms TTL=52
Ping statistics for 159.65.233.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 244ms, Maximum = 278ms, Average = 262ms
C:\Users\pcs>
Also tried pinging 1.1.1.1 and 8.8.8.8 (I use 1.1.1.1 btw) seems to have no problem
C:\WINDOWS\system32>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=75ms TTL=117
Reply from 8.8.8.8: bytes=32 time=49ms TTL=117
Reply from 8.8.8.8: bytes=32 time=47ms TTL=117
Reply from 8.8.8.8: bytes=32 time=63ms TTL=117
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 75ms, Average = 58ms
C:\WINDOWS\system32>ping 1.1.1.1
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=85ms TTL=57
Reply from 1.1.1.1: bytes=32 time=63ms TTL=57
Reply from 1.1.1.1: bytes=32 time=62ms TTL=57
Reply from 1.1.1.1: bytes=32 time=63ms TTL=57
Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 85ms, Average = 68ms
I tried searching for "valorant.com" it is actually a consulting services website. But anyway those are my results, I think its pretty bad lmao. I will also try to find the specific server IP for Valorant's SEA Server and maybe test it.