To fix packet loss in Valorant, check Riot’s service status first. Then play one test match over Ethernet with downloads, uploads, cloud sync, and streaming paused. If the loss disappears, focus on WiFi or traffic inside your home. If it remains over Ethernet, restart the PC and router, compare another time, and collect evidence for your ISP. Do not start with DNS changes or random port forwarding.
Use the symptom to choose the first test
| What you observe | First test | Likely area |
|---|---|---|
| Everyone in the match has problems | Check Riot service status | Game service or regional route |
| Valorant loses packets only on WiFi | Play one match over Ethernet | Signal, interference, or WiFi adapter |
| Loss starts when someone uploads or streams | Pause that traffic and repeat | Home connection congestion |
| Ethernet and WiFi fail at the same time | Compare the router with a public ping target | Router, modem, ISP, or outside route |
| Only this PC has the problem | Restart, update, and disable its VPN for a test | PC, driver, software, or network profile |
| The issue appears on one evening and then stops | Record another session before changing settings | Temporary service, route, or household traffic |
Packet loss means some data does not reach its destination. In a match, that can appear as delayed movement, rubber-banding, missed actions, or a disconnect. Those symptoms can also have other causes, so use Valorant’s network statistics if they are available in your current client and compare them with the tests below. Riot’s guide to game and network instability explains how its performance graphs can help separate network trouble from frame-rate problems.
1. Check Riot service status
Open Riot Games Service Status and choose Valorant and your region. Look for an active incident that matches the time and location of your problem. If Riot reports an outage or degraded service, changing the router will not repair it. Wait for the incident to clear, then test again.
A clean status page does not prove that every route to the game is healthy. It only tells you that Riot has not posted a matching incident. Continue with a local comparison before blaming the PC or ISP.
2. Make the problem repeatable
Write down the time, region, connection type, and what was happening at home. Note whether the problem affects every match or only one server session. One bad match is too little evidence for a factory reset or new router.
- Use the same PC and game region for the first comparisons.
- Record whether the network warning appears throughout the match or in short bursts.
- Ask whether other people in the home lost internet at the same time.
- Repeat the test at another time if the issue appears mainly in the evening.
If Valorant shows several network measurements, do not treat ping and packet loss as the same thing. Ping measures delay, jitter describes how much that delay changes, and packet loss reports missing data. Our guide to packet loss vs ping vs jitter explains the difference.
3. Run one Ethernet control test
Connect the gaming PC directly to a LAN port on the main router or gateway. Turn off WiFi on the PC so Windows cannot keep using it. Play the same mode in the same region for a short test.
If packet loss stops over Ethernet, the internet service may be fine. Focus on WiFi signal, interference, placement, and the PC’s wireless adapter. The article on packet loss on WiFi but not Ethernet follows that branch in more detail.
If the loss continues over Ethernet, you have removed the wireless link from the test. The cause may still be the PC, router, modem, household traffic, ISP, outside route, or game service. Keep testing in that order instead of buying a stronger WiFi router.
4. Pause uploads and background traffic
A speed test can look acceptable while a busy upload queue makes real-time traffic inconsistent. Cloud backups, photo sync, livestreaming, file sharing, game downloads, and operating-system updates all use the same home connection.
- Pause game and launcher downloads on every PC and console.
- Pause cloud backup and photo sync for one match.
- Stop livestreaming and large file uploads.
- Check the router app for another device moving a large amount of data.
Repeat the Ethernet test after pausing that traffic. If the loss stops, reschedule large transfers or review the router’s traffic-management controls. Do not copy a QoS percentage from a forum without measuring your own upload and download capacity. A limit that works on one connection can be wrong on another.
5. Fix the WiFi branch
If Ethernet is stable, test WiFi from the same room as the router. A strong 5 GHz connection is often the sensible first choice at short range. If the PC is farther away or behind several walls, compare 2.4 GHz and 5 GHz from the gaming desk. Keep the band that produces the steadier match, even if its download result is lower.
- Move the router into the open and above floor level.
- Keep the PC away from large metal objects and enclosed furniture.
- Forget the saved WiFi network and reconnect.
- Install the WiFi adapter update offered by Windows Update or the PC or adapter manufacturer.
- Restart the PC and router, then repeat the same match test.
Do not change channel, channel width, wireless mode, and security settings all at once. Make one change, test it, and keep a record. If the WiFi connection itself drops every few minutes, use the separate WiFi disconnecting troubleshooting guide.
6. Check the Windows PC
Restart Windows before using repair commands. Install pending Windows updates and the network-adapter driver supplied for your hardware. For one test, disconnect a VPN or proxy that changes the route to the game. Turn it back on afterward if you need it for other work.
Microsoft’s WiFi troubleshooting steps include forgetting and reconnecting to the network, checking the adapter, and using Network reset only after simpler steps fail. Network reset removes and reinstalls network adapters and returns their settings to defaults. Record any VPN, virtual adapter, or custom network setup before using it.
Flushing DNS is not a general packet-loss repair. DNS helps the PC find an address. Once the match is exchanging traffic, missing packets usually require a connection or route investigation. Changing to a different DNS provider may alter name resolution, but it does not increase WiFi signal or repair an overloaded upload.
7. Compare the router with a public target
A short Windows ping comparison can show whether loss begins before traffic leaves your home. First open Command Prompt and run ipconfig. Find the Default Gateway for the Ethernet or WiFi adapter you are using. Then replace the example router address below with that gateway:
ping -n 50 192.168.1.1
ping -n 50 8.8.8.8The first command checks the local router. The second uses a public Google DNS address as a comparison. Microsoft documents the ping command and its count option. Google documents 8.8.8.8 as one of its Public DNS addresses.
| Ping comparison | What it suggests | Next step |
|---|---|---|
| The router test loses packets | The problem starts on the PC, cable, WiFi, or local router | Repeat over Ethernet and another device |
| The router is clean, but the public test loses packets | The problem may begin after the router | Restart the gateway and collect ISP evidence |
| Both tests are clean, but Valorant still loses packets | The public ping does not follow the same route as the game | Compare another time and check Riot support |
| Only one PC shows loss to the router | The PC or its local connection needs attention | Update the adapter and compare another cable or device |
Some networks give low priority to ping traffic, so a public ping result is a clue rather than proof. Do not claim that a specific company is dropping game packets from this test alone.
8. Avoid fixes that add new problems
- Do not disable the Windows firewall or security software permanently.
- Do not forward a long list of ports unless current Riot support instructions require it for a specific problem.
- Do not use a factory reset before saving the router and ISP settings.
- Do not buy a new router until Ethernet proves that WiFi is the failing part.
- Do not assume a gaming VPN will help. It changes the route and can improve or worsen the result.
A phone hotspot is useful as a brief comparison because it uses a different access network. It is not a permanent diagnosis. Mobile signal, data limits, carrier routing, and added latency make it a different connection. If Valorant works on the hotspot but not home Ethernet, keep investigating the home gateway, ISP, and route.
9. Send useful evidence to the ISP or Riot
Contact the ISP when the problem repeats over Ethernet with household traffic paused. Provide dates and times, the game region, whether other devices were affected, and the router-versus-public ping comparison. Ask the ISP to check the line, gateway history, and route around the reported times.
If local and public tests remain clean while Valorant reports loss, use Riot player support. Include the region, timestamps, connection type, and steps already tried. Do not post account credentials, private support logs, or your public IP address in a public forum.
Use this order when you test again
Check Riot status, reproduce the issue, test Ethernet, pause background traffic, and compare the router with a public target. Fix WiFi only when the Ethernet control is stable. Escalate with timestamps and repeatable results when loss continues beyond the router. This order avoids wiping settings or buying hardware before the failing part is known.
