As an Amazon Associate I earn from qualifying purchases. Some links on this page may earn RealIRacing a commission at no extra cost to you. Gear I personally race on is called out as such; other picks are researched recommendations.

You are side by side into a braking zone and the car next to you jumps half a length forward, then snaps back. You lift, the other driver lifts, and someone gets a 4x. Sim racers call this netcode, but a lot of what gets blamed on iRacing's servers starts in the home: a Wi-Fi link, a busy upload or a PC stutter that looks like a network fault. Here is how I work through it on my own MOZA R9 rig, cheapest and most likely fix first.

Lag and stutter look alike, so separate them first

The first question is whether your whole screen hitches or only other cars misbehave. They have different causes, and swapping a router will do nothing for a frame-rate problem.

iRacing has an on-screen performance readout that shows frame rate alongside connection information. Key bindings vary, so check the controls section in the sim options for how to toggle it on your install. Leave it on for a practice session. What you are watching for is the moment a problem happens: does the connection reading spike at the same second the cars jump? A number that sits steady and then jumps tells you more than any single value.

Plug in an Ethernet cable before anything else

If your sim PC is on Wi-Fi, this is the first change to make. Wi-Fi can look fast on a speed test and still deliver data in uneven bursts, especially when other devices share the airwaves or there is a wall or two in the way. Racing cares much more about steady delivery than about headline speed, since the sim only needs a small amount of data but needs it on time.

A long flat Ethernet cable run along a skirting board costs little and solves the problem for a lot of people. If you cannot run a cable, powerline adapters are worth trying, though results depend heavily on your home's wiring. As a last resort, keep the PC on the 5 GHz band with as clear a line to the router as you can manage, and test at the time of day you actually race.

Rig note

Test at race time. A connection that feels perfect at 10 am may behave very differently at 9 pm when the whole neighbourhood is streaming.

Check the upload, because that is what usually chokes

Home connections often have far less upload than download. A cloud photo backup, a game console pushing a clip, a video call or a stream running on the same line can fill the upload side, and once that happens every packet waits in line. You can have plenty of download speed left and still see cars warp.

Here is the test I would run. Pause cloud sync on every device, then do a practice session and see whether the problem disappears. If it does, turn things back on one at a time until it returns. Then you know what to schedule around race time.

If you stream your races, this matters twice as much, because your stream is itself a steady upload. Keep your stream bitrate well under what your line can sustain, and do a private test recording before going live. If your router has a QoS or traffic priority setting, try giving your sim PC priority. Its usefulness varies a lot by model, so judge it by testing.

Do a simple bufferbloat check

Bufferbloat is what happens when a router lets traffic pile up in a queue under load, and your delay rises as the line gets busy. Plain speed tests often hide it. Search for a bufferbloat test, run it from the sim PC, and compare the latency it reports when idle to the latency during the download and upload phases. If the delay climbs sharply under load, your line can be fine at rest and still fall apart as soon as someone in the house starts an upload.

Router settings such as Smart Queue Management, where available, are designed to help with this. On a basic ISP router you may not have that option, in which case the practical fix is to limit what else uses the connection while you race.

Rule out the PC while you are there

Network hunting can eat a whole evening when the real cause is on the rig. I go through this short list on my own machine before blaming the connection:

  1. Update the network adapter driver from your motherboard maker, as well as your GPU driver.
  2. Close overlay software you are not using, and see whether the problem changes.
  3. Check that your USB devices are not dropping. A wheelbase or pedal disconnect can feel like a sim fault. I wrote up that side of it in USB hubs and peripheral dropouts.
  4. Lower your graphics settings for one session and compare. If the hitching disappears, you had a frame-rate problem.

A stable frame rate matters for force feedback feel too, so this work pays off even if your network turns out to be fine. My wheel settings are in the MOZA R9 settings guide, and the ~9 N·m R9 is forgiving enough that a clean feed is more noticeable than any single number on the base.

Physical distance to the server

iRacing runs servers in different regions, and races are generally assigned according to the entrants. Your delay to that server depends on where you live and on how your provider routes traffic. If you race from South America like I do, you will often be further from the server than drivers in the US or Europe, and there is little you can do about that part.

Higher delay on its own does not have to mean a bad race as long as it stays steady. Variation hurts more. When your delay is high, leave a little more room when you race side by side, because the other car's position on your screen and on theirs can differ slightly. That habit also helps your safety rating, which I covered in the license climb guide.

When the problem is another driver

You cannot fix someone else's Wi-Fi. If a specific car warps through a session, give it extra room, avoid racing it hard into braking zones, and treat its position on your screen as approximate. Your incident count still matters more than who was right. If you think something needs review, save the replay; my process for that sits in the protest and sporting code guide.

What I would do tonight

Run Ethernet to the rig. Turn off cloud uploads on the other devices. Do a practice session with the performance readout on and note the moments anything jumps. That takes one evening, and it answers most of the question before you start thinking about buying a new router or changing provider. If the connection still looks uneven after that, run the same test with the laptop plugged straight into the router and take the results to your provider, since that rules out your own gear.

From the RealiRacing shop

Before you go live, free up your rig. NWM PitStop is the clean-up + stream-priority script set we run before every session — our own product, not a third-party pick. See NWM PitStop →

The gear in this guide
PickWhy it made the listTested?
MOZA R9 Direct Drive Wheelbase9 N·m direct drive — the base bolted to my rig right nowRaced on
MOZA CRP2 Load Cell Pedalsload-cell brake, managed in the same Pit House softwareResearched pick
NVIDIA GeForce RTX 5060 Ti (8 GB)renders iRacing and NVENC-encodes the stream on the same chipRaced on
1440p 120 Hz+ G-SYNC Compatible Gaming Monitormy single-screen setup — high refresh matters more than sizeRaced on

As an Amazon Associate I earn from qualifying purchases. Some links are affiliate links — I may earn a commission at no cost to you.

Watch it, don't just read about it

I stream and upload iRacing races on my MOZA R9 rig — real laps, real force feedback, real mistakes. See the gear from this guide working before you spend a cent.

▶ Subscribe on YouTube

Skip the trial and error

The force-feedback, pedal and baseline settings I actually race, written up as setup packs for MOZA, iRacing, ACC and Le Mans Ultimate. The opening section of each pack is free to read.

See the setup packs →

Free FFB tuning checklist

The order I tune force feedback in, from rig to wheelbase software to iRacing, plus the clipping check. Enter your email and the checklist opens right here. No spam, unsubscribe anytime.

See the privacy notice.

FAQ

Does iRacing need a very fast internet connection?

Generally no. The sim sends a small amount of data, so a steady connection matters more than a large headline speed. Uneven delivery and a saturated upload cause more trouble than a modest plan.

Is Wi-Fi good enough for iRacing?

It can work, but it is more likely to deliver data unevenly, especially at busy times or through walls. Ethernet is the first fix I recommend, with powerline or 5 GHz Wi-Fi as fallbacks when a cable is not possible.

Why do only some cars warp in my iRacing race?

If only one or two cars jump while the rest of the field looks smooth, the issue is often on their connection. If every car jumps at once, check your own network and upload first.

Can streaming cause lag in iRacing?

Yes, it can. A stream is a steady upload that shares your line with the sim, and a high bitrate can fill it. Keep the bitrate well below what your connection can sustain and test before going live.