English
日本語English简体中文Español

Marvel Rivals

Marvel Rivals High Ping and Network Lag: Server Selection and PC Tests

For players who can enter matches but see delayed movement or actions. Record low FPS separately rather than assuming that all stuttering is a network problem.

Edited by Gemnao Editorial Team (Japanese)Last checked 2026-10-08
Saved articles (Japanese page) →
No account needed. Saved only in this browser.

The short answer

Compare the selected server and its displayed latency, then try a lower-latency candidate if appropriate. If delay continues, use CapturePro.exe’s Network Delay Test on familiar nodes or nearby regions and record when the symptom occurs.

Different symptom or still not fixed? Find the next check →
Open My Games →Keep this game’s fixes handy. No account. This browser only.

Key facts

Test to use
Network Delay Test
Scope
Windows PC / official tool in a legitimate installation

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
Separate network delay from low FPSThe word “lag” alone does not identify a network or rendering problem.Step 1
Compare the available match serversThe official guide allows a single server or a group of servers.Step 2
Capture delay with Network Delay TestTest familiar nodes or nearby regions using the official tool.Step 3
Compare the records and contact support if neededInclude the conditions under which each measurement was taken.Step 4

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1｜Separate network delay from low FPS

The word “lag” alone does not identify a network or rendering problem.

Time: About 2 min · Risk: low

  1. Describe whether actions arrive late or the whole picture loses smoothness.
  2. If available, record ping and FPS with the selected node and time. If no figures are shown, record the symptoms instead.
  3. Check official news for a relevant incident. If only FPS drops, continue to the general low-FPS guide.

General low-FPS guide (Japanese) — Use this when rendering, rather than network delay, is the problem.

Step 2｜Compare the available match servers

The official guide allows a single server or a group of servers.

Time: About 2 min · Risk: low

  1. Check the available servers and displayed latency in the game, and note your original selection.
  2. Compare a lower-latency candidate first. Do not assume a nearby city name guarantees a better route; check the display and actual play.
  3. Record nodes, times and symptoms before and after changing the selection so that you can restore the original choice if it does not help.

Node selection does not guarantee low ping or shorter queues. Use the options shown by your current client.

Step 3｜Capture delay with Network Delay Test

Test familiar nodes or nearby regions using the official tool.

Time: About 20 sec plus setup · Risk: low

  1. Open CapturePro.exe in the legitimate game installation and choose Network Delay Test. If it is missing, ask support rather than downloading an unofficial copy.
  2. Select nodes you normally use or nearby regions. For a short comparison, wait about 20 seconds, then press Stop yourself.
  3. The publisher also permits testing during play. To capture the symptom, press Stop when noticeable delay occurs and record the time, node and symptoms.

About 20 seconds is a measurement guideline, not an expected recovery time. Do not bypass security warnings to run the tool.

Step 4｜Compare the records and contact support if needed

Include the conditions under which each measurement was taken.

Time: About 3 min · Risk: low

  1. Compare the records before and after the node change and at the moment of lag. One result does not prove that your ISP or the game server is faulty.
  2. If it improves, keep the selected node and conditions in your notes. If it recurs, add the time, time zone and symptoms.
  3. If it persists, reach Marvel Rivals Support through the official FAQ. Confirm how to submit the generated tr_results_xxxxxxxx_xxxxxx.zip; do not post it publicly. Redact personal details in screenshots and ask before modifying diagnostic logs.

Avoid

  • Do not obtain CapturePro.exe from search ads, mirrors or unofficial download links.
  • Do not disable antivirus or the entire firewall to troubleshoot a connection.
  • Keep passwords, verification codes and tokens out of screenshots and support messages.

Important cautions

  • Diagnostic files may contain connection, device or network-environment information. Do not post them in public chat. Reach support through the official website and confirm the required data and secure submission method.
  • Based on public official documentation; not a claim of hands-on reproduction or a guaranteed fix.

FAQ

Is Tokyo always fastest when playing from Japan?

Tokyo appears in the official node list, but the best route depends on your connection. Compare your current client’s latency display with actual match behavior.

Does Network Delay Test improve FPS?

The publisher describes it as network diagnosis, not a frame-rate improvement feature. If ping is stable but FPS is low, investigate rendering load separately.

Should I select every server?

The official guide allows one server or a group, but does not say that selecting all is always best. Compare candidate latency and the symptoms before and after a change.

Sources

Based on public official documentation; not a claim of hands-on reproduction or a guaranteed fix.

Marvel Rivals: network analysis tool guideMarvel Rivals: server selectionMarvel Rivals: release FAQ and support contactMarvel Rivals: official newsSteam: Marvel Rivals requirements and languagesMarvel RivalsJapanese version of this page