iRacing is rolling out AWS Global Accelerator with the Season 3 June build, and for a significant portion of the community the improvement will be immediate. The change affects how your connection reaches iRacing race servers, shifting traffic from the unpredictable public internet to Amazon’s private global network. For most drivers, the benefit is reduced jitter. For international drivers, particularly those in South America and Australia, it also means lower raw latency.
Also See
➡️ iRacing Season 3 2026: Every Car, Track, and Feature Announced
🎮 iRacing Staff Post: AWS Global Accelerator Announcement
iRacing staff member Nicholas Bailey confirmed the rollout in a forum thread about connection quality. He noted the service has been in testing and that the full deployment across all race farms is tied to Season 3. A new iRacingPing.exe utility is already available for drivers who want to measure their current connection quality ahead of the update.
What the Upgrade Actually Does
Your current connection to an iRacing race server travels across the public internet. That route is not fixed. It changes based on network conditions, the time of day, and the decisions made by various routers along the way. The variability is the problem. When your data takes a different number of hops from session to session, or even within a session, the delay between your inputs and the server fluctuates. That fluctuation is jitter, and it causes the kinds of disconnects and input lag spikes that feel like something went wrong even when your average ping looks fine.
AWS Global Accelerator changes the entry point. Instead of your data traveling the full distance to iRacing’s servers on the public internet, it enters Amazon’s private network at the nearest AWS edge location to your region. From there it travels on Amazon’s own backbone infrastructure, which is heavily redundant, predictable, and monitored. The result is a much more consistent delay between you and the server, because the data is no longer competing with regular internet traffic or subject to the whims of public routing.
Who Benefits Most
For drivers in North America who are already close to iRacing’s primary infrastructure, the main gain is stability. Sessions that occasionally show spikes or feel inconsistent should improve. However, the raw latency number may not change much because the public internet path was already relatively short.
The bigger gains land in South America and Australia. Both regions have historically relied on long, variable routes to reach iRacing’s servers, and that has been a consistent source of frustration. With anycast routing, the connection enters Amazon’s network close to home and then rides a controlled path to the destination. Bailey’s post specifically highlights these regions as seeing measurable latency reductions, not just jitter improvements.
Testing Your Connection Now
iRacing has made iRacingPing.exe available ahead of the build. The utility lets you check current connection quality to iRacing’s server infrastructure. It is a useful baseline to run before Season 3 so you have something to compare against after the update goes live.
One thing to note: the UI option for enabling or configuring the anycast connection exists in the current iRacing client but does not function yet. Bailey clarified this directly in the forum thread. The toggle will become active with the June build. If you see the option and it does not respond, that is expected.
This is the kind of backend change that rarely gets its own headline but affects the experience every time you race. Consistent connections do not make you faster, but they eliminate one of the more unpredictable variables in online racing. For anyone who has had a strong weekend follow an inconsistent one without a clear reason why, Season 3 gives you one fewer factor to guess about.
