ElevateBoost
Marvel RivalsA 180 ms match in Marvel Rivals is not just annoying — it costs you fights. Dive characters eat your Strange shield before the server registers your W. Luna Snow's heal lands on a teammate who was alive 300 ms ago. Ranked climbing stalls because every duel is decided by whoever has the better connection, not the better aim.
The good news: the fixes are concrete, free, and finished in under an hour. Below is the exact order to work through them, from the one-click wins to the deeper network changes that actually solve stuttering ping. Target numbers are from the official NetEase server regions and the hitreg thresholds competitive players use.
What counts as high ping in Marvel Rivals
Marvel Rivals shows your ping on the top-right of the HUD once you enable it in Settings → Interface → Display Network Statistics. The game runs 60 Hz tick-rate and streams positional updates roughly every 16 ms. Here is the realistic ladder:
- Under 40 ms — competitive tier. Hitboxes are honest, melee heroes trade fairly, and ultimates land where you aimed.
- 40 to 80 ms — playable in ranked up to Diamond. You will lose a few peeks against lower-ping duelists but can still carry.
- 80 to 120 ms — projectile heroes feel bad. Hela, Hawkeye and Iron Fist suffer most. Expect a visible delay on every ability cast.
- Over 120 ms — this is the zone the game flags as unstable. You will see rubber-banding, phantom hits, and ability refunds.
- Over 200 ms — fights are no longer winnable against a 40 ms opponent. Fix the route before queueing again.
Spikes are worse than steady high ping. A match that sits at 65 ms with 150 ms spikes every 30 seconds reads as 65 average in the overlay, but the spikes are what cost you rounds. The target is a flat line, not just a low average.
Step 1 — Pick the correct server region
Marvel Rivals auto-picks the lowest-latency NetEase server, but the auto-pick is sometimes wrong on first launch after a title update or if you queued with a party. Open the main menu, click your profile icon, choose Settings → Match → Server, and compare the ping readings. The official regions are:
- North America East — hosted in Virginia, roughly 10 ms from the US East Coast.
- North America West — Oregon, 20 ms from the US West Coast.
- Europe — Frankfurt, 20 to 40 ms from Western Europe.
- Asia — Tokyo and Singapore, swap based on queue health.
- Oceania — Sydney, 20 ms within AU/NZ.
Pick the lowest number, not the one closest on the map. If you live in Lisbon and the US East ping is lower than Europe, that is because the Atlantic submarine cable to Virginia is better than the terrestrial route to Frankfurt from your ISP. Queue there.
Step 2 — Switch to Ethernet, every time
Wi-Fi is the single biggest cause of ping spikes in Marvel Rivals. A 5 GHz connection reads as 10 ms in the Windows speed test, but the radio renegotiates every few seconds, and each renegotiation is a 40 to 120 ms spike while packets reorder. Even a signal reading of -55 dBm on the taskbar is enough for this.
Run a cable. A 15-meter flat Cat6 cable costs under 20 euros and routes under a door. The ping overlay will go from an average of 65 ms with 150 ms spikes to a flat 55 ms line within one match. There is no software fix that matches this — if the gaming PC and the router are not on the same floor, the cable is the whole solution.
If a cable is impossible, go wired by MoCA (Multimedia over Coax) if your home has coaxial outlets, or by Powerline G.hn adapters. Both are five to ten times more stable than Wi-Fi. Avoid old Powerline AV2 units — they share bandwidth with microwaves and refrigerators on the same circuit.
Step 3 — Kill the background upload
Any program uploading in the background turns your ping into a sawtooth. Game packets wait in line behind the uploader because home routers do not prioritize them by default. Check for and pause:
- Cloud sync — OneDrive, Dropbox, Google Drive and iCloud all upload the moment you edit a file.
- Steam, Epic and the Riot client — background game updates saturate the upload link if a 90 GB patch is downloading.
- Discord screen share and streaming — a single 720p screenshare pushes 4 to 6 Mbit/s upload.
- Browser video uploads — a Zoom or Google Meet call shares the same route as the game.
- Smart home backups — security cameras uploading to the cloud. Check your router's traffic graph.
The fastest check: open Task Manager → Performance → Ethernet. If upload is above 1 Mbit/s and you are not streaming on purpose, something is wrong. Right-click the offender in the Processes tab and set its priority to Low, or just quit it.
Step 4 — Set Marvel Rivals to High priority
Windows defaults every program to Normal priority. The game is competing with Discord, Chrome, and your anti-virus for CPU slots, which creates frame hitches that look like ping spikes but are not. Fix it:
- Open Task Manager with Ctrl + Shift + Esc while the game is running.
- Go to Details, right-click MarvelRivals-Win64-Shipping.exe.
- Choose Set Priority → High. Do not choose Realtime — it starves the audio driver.
- Then right-click again → Set Affinity, and uncheck CPU 0 if you have 8 or more cores. CPU 0 handles Windows interrupts and causes microstutter.
The change resets when you quit. To make it permanent, create a shortcut that launches the game with the Windows command start /HIGH MarvelRivals-Win64-Shipping.exe or use Process Lasso.
Step 5 — Flush DNS and lock to a fast resolver
Your ISP's default DNS server is often the slowest hop in your route. Marvel Rivals contacts dozens of hosts at launch — login, matchmaking, telemetry, chat — and each one does a DNS lookup. A slow resolver adds 50 to 200 ms to the first ability of every match while connections resolve.
Open Command Prompt as administrator and run ipconfig /flushdns to clear a corrupted cache. Then set your DNS manually to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). On Windows 11: Settings → Network & Internet → Ethernet or Wi-Fi → DNS server assignment → Manual → IPv4 → On. Preferred DNS 1.1.1.1, Alternate 1.0.0.1.
Step 6 — Check for packet loss, not just ping
Low ping with 2% packet loss plays worse than 100 ms ping with 0% loss. Every lost packet is a rollback that looks like your character teleporting or an ability refunding. Run this test for 60 seconds while the game is running:
Open PowerShell and run ping -t -n 60 playvalorant.com — any public gaming host works, Riot's edge is close to NetEase's. Watch the output. If more than one packet in 100 says Request timed out, you have packet loss. Then run tracert gameserver.marvelrivals.com to find the hop that is losing packets. If the bad hop is on your ISP, you need to call them. If it is on your router, reboot the router.
Step 7 — Turn off the two overlays that spike ping
Nvidia Experience / GeForce overlay and Xbox Game Bar both inject hooks into the game, and both have been seen to add 15 to 40 ms of ping on networked games. Turn them off:
- Nvidia — open Nvidia App → Settings → In-Game Overlay → Off. The old GeForce Experience is being retired for the Nvidia App in 2026, both have the toggle.
- Windows Game Bar — Settings → Gaming → Game Bar → Off.
- Discord overlay — settings → Game Overlay → Enable In-Game Overlay off. Keep the voice connection, drop the overlay.
- MSI Afterburner / RTSS — these are safer, keep them if you use them for FPS monitoring.
Step 8 — The router reboot that actually works
A router that has been running for more than 30 days accumulates stuck NAT table entries. The symptom is ping that is fine for the first 10 minutes of a session, then climbs steadily. The fix is a full power cycle, not just a restart from the admin panel:
- Unplug the router from the wall for 60 seconds. Not 10 — 60. The capacitors need time to drain.
- Unplug the modem too if they are separate boxes.
- Plug the modem back in first, wait until all its lights are green.
- Then plug the router back in.
This clears the NAT table, the DHCP leases and the DNS cache in one pass. Combined with the DNS switch in step 5, it fixes the slow-climbing ping that nobody can explain.
When your ping is fine but matches still feel laggy
If your overlay reads 45 ms, your packet loss is 0, and the game still rubber-bands, the problem is on the server side — a specific NetEase region having a bad night. Switch regions for the session. Marvel Rivals lets you queue in any region at the cost of higher ping, and a 90 ms stable match is better than a 45 ms match that drops packets.
You can also check Downdetector and the official @MarvelRivals account on X for outage reports. If dozens of players in your region are reporting the same thing, close the client for an hour and come back.
Climb ranks without the lag
A stable 50 ms connection is the floor for competitive play. If the fixes above shaved your ping from 180 to 50 and you still cannot climb, the ping was not the only problem — your rank is where your mechanics are. Our boosters play on wired fiber lines in Oregon, Virginia and Frankfurt with sub-30 ms stable connections, and run Marvel Rivals rank boost orders at One Above All level. Use it as a shortcut or just to see where the ceiling of the current meta actually sits.