Download—Mbps
Cloudflare edge testPerformance, not guesswork
Apex Legends connection check.
Test your connection, then follow the game-specific fixes and settings below.
Jump to fixes, settings & platform help ↓DownloadUploadPingJitterLoss
Upload—Mbps
Ping—ms
Jitter—ms
Packet loss—%
Apex Legends: fix lag, high ping and packet loss
Compare Apex data centres, check actual in-match packet loss and separate connection warnings from low frame rate.
Find out what is actually lagging
Start with the match's performance display rather than the headline broadband speed. Note whether latency, packet loss or FPS changes as movement becomes uneven. The launch-screen estimate is useful for choosing a data centre, but the actual match remains the better comparison.
High ping or jitter
Actions arrive late, or delay fluctuates. Compare the in-game latency reading with your usual baseline.
Packet loss
Updates may be missing and movement can snap back. Look for a loss reading, not just a low average ping.
Low FPS or input delay
A choppy image or delayed controls can come from the device or display. Check an offline/local mode when available.
Settings worth checking in Apex Legends
Menu names can change with patches, editions and platform. Use the controls available in your build; do not apply PC-only instructions to a console.
Performance Display
Settings → Gameplay → Performance Display: turn it On.
What it does: Displays frame rate, latency and packet loss so you can compare network and rendering problems.
Data Center
At the launch screen, before selecting Continue, open Data Center and compare nearby locations.
What it does: EA recommends a nearby centre. Check both loss and latency rather than choosing distance alone.
Video settings
If FPS drops while connection values remain steady, compare lower video settings or an available performance mode.
What it does: Improves local rendering where supported. It cannot repair loss on the route to an Apex server.
PC troubleshooting, step by step
- Pause downloads in Steam, the EA app and other clients. Compare the same nearby data centre over several sessions with background uploads stopped.
- If Performance Display points to FPS rather than network trouble, compare a sustainable frame-rate cap and lower video settings. Change one variable and use a similar scene or mode.
- Save the time, data centre and display readings from a bad match. Avoid presenting a prediction-error icon alone as proof of ISP packet loss; record the accompanying measurements.
Console support and fixes
- Enable Performance Display and use the Data Center selection available in the current build. Record the console model and game version in any support report.
- Pause downloads, use Ethernet where supported and run the platform's connection check. Then compare a match; platform diagnostics do not test the exact route to that Apex server.
- Use only performance options supported by your console and display. A smoother frame rate can feel better while network ping stays unchanged.
Check the console connection itself
PS5: Settings → Network → Connection Status → Test Internet Connection. Xbox: Settings → General → Network settings → Test network speed & statistics. Other models can use different labels. These tests assess platform connectivity, not your game's exact match server.
Record errors and NAT warnings if joining or party chat fails. NAT changes are not a general cure for high ping. Avoid DMZ mode or opening ports without a diagnosed need and the platform's own guidance.
A controlled checklist for ping spikes and loss
- Record a baseline. Note your game mode, platform, time, connection type and the in-game reading. Run RaceMyNet outside a match. Keep two or three results rather than relying on one unusually good test.
- Remove local wireless uncertainty. Compare Ethernet directly to the main router where possible. A cable into a wireless mesh satellite may still use a wireless backhaul. If Ethernet is unavailable, compare close to the main router.
- Pause heavy traffic. Stop downloads, cloud backups and livestream uploads across the household for one comparison. If lag disappears only when traffic stops, investigate congestion and your router's supported queue-management options.
- Check the simple physical causes. Reseat Ethernet plugs, try a known-good cable or another router port, and restart network equipment once using its manufacturer's instructions. Do not factory-reset it as the first step.
- Change one thing and retest. Compare similar matches at your normal playing time. Keep improvements that repeat. A faster DNS service, a VPN or more Mbps is not a guaranteed reduction in game-server ping.
Prefer the game's own loss display for game traffic. If RaceMyNet reports an HTTPS fallback, request failures are not a direct measurement of the game's UDP packet loss.
If Apex Legends still has connection problems
- If multiple nearby centres show trouble, check EA's service information before assuming every route from your home is faulty.
- If only one centre repeatedly performs badly, compare another nearby one and report the times and results. A successful comparison is evidence about the route/server combination, not proof of which organisation caused it.
If several games and devices struggle on a wired connection, give your ISP the times, results and affected services. If only this game or mode is affected, start with the publisher's support and service information below. Include the platform, region, timestamps and a short clip of the indicators. Share diagnostic logs privately through official support.
Should I choose the centre with the lowest ping even if it shows loss?
Not automatically. Compare nearby centres that show stable delivery, then verify in a match. A slightly higher stable latency may feel more consistent than the lowest number with repeated lost updates.
Official guidance and further help
Menu instructions were checked against the publisher guidance below. General comparison steps are troubleshooting suggestions, not a promise of a particular ping or a guaranteed fix.
GAMING CONNECTION GUIDE
Use the test as a baseline. Verify the result in your game.
A browser test and a game match use different servers. Compare repeat measurements, in-game indicators and the same playing conditions before deciding whether a change helped.