Fortnite Ping Test — Understand Your Regional Baseline
To check your actual Fortnite ping, turn on Net Debug Stats in the game and read it during a match. The browser test above measures HTTP response timing to AWS reference regions. Use it as a separate regional comparison; it cannot measure the ping or packet loss of your Fortnite match.
Show ping and packet loss in Fortnite · Check high ping or lag · Read our test method
This test compares the time your browser takes to complete HTTP requests to public AWS DynamoDB endpoints in different regions. It makes four attempts per region, with up to three requests active at once, then stops. No test traffic starts until you select Start Regional Test. The median uses successful requests only; the sample count shows valid results out of attempts made.
These AWS locations are not a list of Fortnite matchmaking servers. Browser timing can include DNS lookup, connection setup, TLS negotiation and the HTTP response. Fortnite uses its own game traffic, endpoints and routing, so this number can differ from the ping shown in a match. This tool does not measure Fortnite packet loss, UDP latency or server health. For bandwidth, run the internet speed test separately.
Check Your Actual Ping and Packet Loss in Fortnite
In Fortnite, open Settings → Game UI and turn on Net Debug Stats. Join an actual match to see the connection readout. Epic explains the setting in its official ping and packet-loss instructions. Menu names and availability can vary by game version or mode.
Also review Settings → Game → Language and Region → Matchmaking Region. Epic recommends Auto, which selects its best-ping region. Compare the estimates there with your actual match. A region can contain several subregions, and the match destination can vary. A low AWS result here does not identify a Fortnite server or guarantee a better match if you change regions.
Which Result Should You Use?
| Check | What It Shows | How to Use It |
|---|---|---|
| This regional test | Browser HTTP timing to AWS endpoints | Compare a regional baseline under the same conditions |
| Fortnite Matchmaking Region | Fortnite's estimated ping for its available regions | Review Auto and the regions offered by the game |
| Net Debug Stats in a match | The game's connection readout, including ping and packet loss | Check what happens during the lag you actually experience |
| Internet speed test | Bandwidth and supported latency measurements to its own test endpoints | Look for broader connection or congestion problems |
Run a Fair Comparison Before Changing Your Setup
Pause downloads, cloud backups and other heavy traffic before a baseline run. Keep the device, location and connection the same when comparing regions. To investigate Wi-Fi, repeat the check over Ethernet where available, then verify the difference inside a Fortnite match. Run a separate comparison while the connection is busy if you suspect congestion; do not mix those results with your idle baseline.
A single fast request does not show that your connection stays stable. The median reduces the influence of one unusually slow sample, but four requests are a short snapshot. Read our Fortnite ping guide for the difference between regional distance, routing and changing network conditions.
What to Check When Fortnite Ping Is High
- Check the service first. Review Epic Games Server Status for a reported incident.
- Record the affected match. With Net Debug Stats on, note ping and packet loss during the problem, plus the time, matchmaking region and experience or mode. A browser timeout here is not an in-game packet-loss percentage.
- Compare one condition. Pause your own large transfers, or compare Ethernet with Wi-Fi where practical. Repeat inside Fortnite as well as in the browser. Keep idle and busy-connection results separate.
- Use the right evidence for support. Epic's latency troubleshooting guide includes its own datacenter ping endpoints. Those manual checks use ICMP, while gameplay uses UDP; neither an ICMP result nor this HTTP test rules out a problem on the game's route. Share the affected match observations with your ISP or Epic support.
How This Test Handles Failed Requests
Each request has a four-second time limit. Network errors and timeouts show Unavailable and are excluded from the median. If a region has no valid samples, it has no latency result. A browser, firewall or endpoint policy can block a request, so Unavailable does not establish that Fortnite is offline or that your game packets are being lost.
The browser uses no-cors requests, so it cannot inspect the endpoint's HTTP status or response body. A completed response provides a timing sample even if the service returns an HTTP error. Stopping the test or hiding the tab cancels active requests and prevents old results from updating a later run. A complete run makes at most 116 attempts across 29 AWS regions, with only three requests active at once. If every request times out, it can take about three minutes. You can stop the run at any time.
Compare a room or a busy connection
If the problem follows location, use the Wi-Fi room comparison on the same device. If lag appears mainly during transfers, compare the idle and loaded HTTP timing test, then confirm the difference in Fortnite. These checks organise browser evidence; they cannot read game traffic or identify the exact cause. The measurement method explains the scope.
Related Guides
- Gamer Hub — All Game Ping Tests
- General Server Ping Test
- Fortnite Ping Explained
- What Is a Good Ping for Gaming?
- Jitter vs Ping for Gaming
- How to Improve Ping for Online Gaming
Frequently Asked Questions
Is this my exact Fortnite ping?
No. It is HTTP timing to AWS reference endpoints. Use Fortnite's Net Debug Stats in a match for the game's own connection readout. The network route, protocol and destination can all differ.
What region should I pick in Fortnite?
Start with Auto, which selects the best ping according to Fortnite. Review the estimates next to the game's available matchmaking regions and verify your actual match experience before changing the setting. The AWS list above does not replace Fortnite's region list.
Why does the median show fewer than four samples?
The count shows valid requests out of attempts made, such as 3/4. A failed or timed-out request is not included in the median. If you stop a test early, the results are a partial run; select Run Again for a fresh comparison.