Battle Royale · EA / Respawn
What is a good ping for Apex Legends?
A good ping for Apex Legends (Battle Royale) is under 40 ms, and under 20 ms is optimal. 70 ms is the highest still-playable ping; beyond about 100 ms Apex Legends becomes frustrating. The table below is the exact ping, jitter and packet-loss bands Apex Legends is graded against.
Good ping, jitter & packet loss for Apex Legends
| Metric | Optimal | Good | Playable max | No-go |
|---|---|---|---|---|
| Ping | ≤ 20 ms | ≤ 40 ms | ≤ 70 ms | > 100 ms |
| Jitter | ≤ 3 ms | ≤ 8 ms | ≤ 15 ms | > 30 ms |
| Packet loss | 0% | ≤ 0.2% | ≤ 0.8% | > 2.5% |
Dense end-game scenes want bandwidth headroom; twitch moments behave like Competitive FPS.
How FRAGRATE measures this
FRAGRATE measures ping and jitter as a TCP-handshake to a public endpoint in each game region, packet loss via UDP/WebRTC, and bufferbloat as the latency added while your line is saturated. Run it locally for true per-region game-server ping, or use the hosted browser test for ping, loss and bufferbloat.
FAQ
- What is a good ping for Apex Legends?
- Aim for under 40 ms; under 20 ms is optimal for Apex Legends. Up to 70 ms is the playable ceiling, and above about 100 ms Apex Legends feels laggy.
- Does jitter matter for Apex Legends?
- Yes — keep jitter under 8 ms for Apex Legends (Battle Royale). Above 30 ms you get inconsistent hit registration and rubber-banding even when average ping looks fine.
- How much packet loss can Apex Legends tolerate?
- Keep packet loss under 0.2%. Between 0.2% and 0.8% is borderline; above 2.5% Apex Legends is effectively unplayable.
- Why does Apex Legends lag when someone else is streaming?
- That's bufferbloat — latency that piles up when your connection is saturated. A fast line can still spike to hundreds of ms under load, so Apex Legends stutters mid-fight. FRAGRATE measures latency-under-load to catch it.