Summary
- While connected to a published Creative island, the game client was exchanging
constant traffic with 74.231.95.34 (74.231.95.34.bc.googleusercontent.com,
Google Cloud). The server does not respond to ICMP ping. - A traceroute to 74.231.95.34 shows the route leaving my ISP through
Miami, USA (ae2.3609.edge6.Miami1.net.lumen.tech) and continuing on the AT&T
network in Florida (fldfl401me3.ip.att.net). The trace did not reach the
destination. - In comparison, traceroute to the AWS São Paulo server (15.228.25.140) reaches
sa-east-1 directly in 87 ms. - This indicates the Creative session is hosted in the United States instead of
the Brazil region, despite Matchmaking Region being set to Brazil. - Note: the last visible hop (Florida) is at ~86 ms, while in-game ping is ~200 ms,
so part of the extra latency may come from the remaining path to the server
or from the server itself.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Assets
Steps to Reproduce
- Launch Fortnite on PC (Windows) with Matchmaking Region manually set to “Brazil”.
- Check network stats in Battle Royale or Reload to confirm normal latency (~80ms).
- Go to the Discovery menu and select any public Creative island or UEFN map.
- Load into the map and open the Network Debug Stats.
- Observe the ping spikes to ~200ms while in the Creative map.
Expected Result
The Creative mode should assign me to the closest server (Brazil), resulting in the same stable ping of ~80ms that I get in Battle Royale, with no packet loss.
Observed Result
The game assigns me to a distant server (likely NA-East or NA-Central), causing my ping to spike to ~200ms.
I ran a manual ping test via CMD to the Brazil AWS server (15.228.25.140) and got 86ms with 0% packet loss, confirming my local network and routing to Brazil are perfect. The issue is strictly the matchmaking server assignment for Creative modes.
Platform(s)
PC
Video
Additional Notes
Network Diagnostic Evidence:
To prove this is a server-side routing/matchmaking issue and not a problem with my local internet, I ran a ping test via Windows CMD to the official AWS Brazil server IP (15.228.25.140).
Command used: ping 15.228.25.140 -n 50
Results:
- Packets: Sent = 50, Received = 50, Lost = 0 (0% loss)
- Approximate round trip times in milli-seconds:
- Minimum = 86ms, Maximum = 87ms, Average = 86ms
This confirms a perfect, stable 86ms connection to the Brazil region. The 200ms ping in Creative is caused by the game incorrectly routing me to a different region. I have also attached screenshots of this ping test and the in-game network debug stats.