The first time someone says you’re blinking, you don’t believe them. Your screen is smooth and your ping is fine, so as far as you’re concerned, it’s a problem on their end, not yours.
Then it happens the next race, and the one after. Different drivers, different farms, same message. It drives fine for you and looks broken to everyone else, and the fast broadband you’re paying for isn’t doing a thing about it.
Racing barely touches your bandwidth. It runs on a steady stream of tiny updates, and what breaks that stream is packet loss, congestion, a rough route to the race farm, or a PC dropping physics ticks. None of those care how fast your line is.
So start with the system meters. They’ll tell you whether the fault is in your network, your PC, or the route between them.
Image Source: iRacing
Check the system meters first
Before tweaking any settings, get the meters up and read them. They’re the only thing that tells you right away whether you’re chasing a network problem or a PC one.
While you’re in the sim, press Alt + K, open Widget Options, click System Meters, and set them to Graphical. That puts Q, L, C, S, and E on screen as bars. Run a busy practice or race where the issue normally shows up. A quiet session with two cars tells you very little.
Start with the Q meter. Its left side shows packets lost on the way from the server to your PC. Its right side shows packets your PC sent that never reached the server.
That right side is the one to watch when other drivers say you’re blinking. Their game gets fewer updates about where your car is, so it jumps, freezes, or vanishes on their screen.
Then read L, C, S, and E:
- L is latency. A steady 120ms connection races fine. A line that swings from 40ms to 250ms and back is the one that gives issues.
- C is CPU load, how hard the chip is working to keep iRacing’s physics running.
- S rises when the PC falls behind the 60Hz physics tick.
- E is congestion. When it flashes a red CE on the upload side, other drivers get your car’s position less often, and that’s the blinking they’re seeing.
The pattern matters more than a single red flash. Q going red while C and S stay green points to your network or route. C turning red before Q or L points to the PC. And if S keeps climbing, your system is missing physics updates and needs sorting before you go near any router settings.
One blinking car with a quiet meter box is usually somebody else’s problem. Several cars breaking up at once while your Q or E meter lights up puts it back on you.
Image Source: iRacing
Fix packet loss on your own network
Most blinking starts on your own home network, and the cause is usually something not so taxing. The plain fixes clear it more often than any config tweak, so start with a wired baseline.
Connect the PC straight to the main router with a cable you trust, then take Wi-Fi, mesh nodes, powerline adapters, and USB Ethernet dongles out of the test.
Pause anything that uploads or downloads in the background: cloud backups like OneDrive or Google Drive, Steam updates, Twitch streams, Windows updates, CCTV uploads, and anybody else in the house hammering the connection.
Restart the modem and router, then run the same session again with the meters visible. iRacing puts background traffic and a modem restart at the top of its own checklist for this.
A speed test can look excellent while your race connection is rough, because it only samples a brief moment. iRacing itself says a couple of quick tests won’t catch how much your connection wobbles mid-race, which is how a fast broadband package still leaves you blinking.
Check your Connection Type setting too, under Helmet Icon > Account > Options > Network. It controls how much car data the server sends you. Higher settings allow larger packets and more detailed updates from more cars, which matters most in big fields, and the change only takes effect once you leave the sim and rejoin.
Set it to match the download speed you get day to day, not the number on the box, then watch the Q, E, and C meters to see how stable it is.
Upload congestion that turns up at the same time every evening is the one time it’s worth poking at your router’s QoS. Change one thing, run the same test, and keep it only if the meters improve. QoS only orders the traffic leaving your house, so it helps when your own uploads are the jam and does nothing when the congestion is further up your ISP’s line. Router settings turn into a rabbit hole fast.
Image Source: iRacing
Check whether your PC is falling behind
A red C meter points at the PC rather than the network. iRacing’s physics thread has to run 60 times every second. When your PC can’t keep up, the S meter starts to rise. iRacing also warns that a red C meter can push your Q and L readings higher, which is how an overloaded CPU ends up looking like packet loss.
Use the same car, track, weather, and field size for every test. Then change one thing at a time:
- Cap your FPS at your monitor’s refresh rate, or two to five frames below it.
- Reduce max cars, visible cars, mirror detail, and cars in the pits.
- Close overlays, RGB utilities, motherboard control apps, browser tabs, telemetry tools, and anything else running in the background.
- Plug your wheel, pedals, and other race hardware straight into motherboard USB ports while testing.
Large grids lean on the PC far harder than a solo lap. iRacing says the number of cars received and rendered drives processing load directly, so deal with that before you start tearing through graphics settings at random.
USB gear can cause trouble too. iRacing calls out Simagic Alpha wheelbases running at 360Hz and the Haptic Pedal Reactor, where high polling rates flood the USB bus. For a Simagic Alpha, set loadSimagicAPI=0 in Documents/iRacing/app.ini to drop it out of 360Hz mode, and switch off the Haptic Pedal Reactor by unchecking vibrate pedals in the options.
AMD B550 and B650 board owners should also check for BIOS updates and pull out any unnecessary USB hubs. iRacing flags those boards as especially prone to shared USB and PCI bandwidth issues, worst with a high-power GPU and NVMe drives in the mix.
Image Source: iRacing
Test the route to your race farm
If your network checks out and your PC’s keeping pace, the fault is somewhere on the route between you and iRacing’s servers. Blinking that only turns up in one series, one region, or at certain times of day usually points this way.
Join a session where it happens, open the RULES tab, and note the race farm and test target shown there. Then run iRacingPing.exe from your iRacing install folder. It checks IPv4 and IPv6, plus unicast and Anycast, so you can compare all four paths instead of guessing from a single speed test.
Look at packet loss, average ping, and how much each result moves around. A route that saves 3ms but drops packets is no use to you in a close race.
Keep Prefer Anycast switched on while you test. Anycast is iRacing’s default route because it gets your traffic onto iRacing’s backbone early, where there are fewer public-internet hops in the way. The UI shows average unicast and Anycast ping for each farm when you hover over the connection graphs.
IPv6 needs the same treatment. Turn it on in iRacing’s Network settings, compare the results, and keep whichever route behaves better for the farm you use. Some ISPs route IPv6 poorly. Others route it far better than IPv4, especially where carrier-grade NAT shifts your IPv4 address mid-race.
One farm behaving badly doesn’t mean you change every connection. iRacing lets you exclude a single farm in Documents\iRacing\app.ini:
[Misc]
excludeIPv6OnFarms=use2
excludeAnycastOnFarms=use2
Use the farm code you tested, save the file while iRacing is closed, then run the same test session again. For reference:
- Frankfurt is euc1
- US East is use2
- US West is usw1
- São Paulo is sae1
- Tokyo is apne1
- Sydney is apse2
Image Source: iRacing
Avoid random network tweaks
Plenty of the blinking advice floating around forums either does nothing or quietly makes things worse.
Leave Windows-level IPv6 changes alone. iRacing has its own IPv6 control, and switching the protocol off across your whole PC can take away the better route for a different race farm.
Skip the old net_max_payload=1024 advice too. iRacing’s current path runs on the system meters, the Connection settings, the Network switches, and iRacingPing.exe. Stick with those until the evidence points somewhere specific.
Plain ping and traceroute tell you less now that Anycast is on. They can look like they’ve finished once traffic reaches iRacing’s network, even though the race server is much further out. Run iRacingPing.exe first, and bring in PingPlotter only when you want a longer trace using the hostnames the tool hands you.
Image Source: SimStaff
When to call your ISP or iRacing
Work through the local checks first, then gather your proof before you contact anyone. Support on every side moves quicker when you turn up with evidence.
Take a screenshot of your system meters while the issue is happening. Save the iRacingPing.exe results for the affected farm. If you run PingPlotter, export the .pp2 file and grab a screenshot of the final hop. iRacing asks for both when you raise a connection issue.
Give your ISP the date, time, race farm, and your evidence of loss or spikes at the final target. An ugly hop in the middle can look alarming while the destination remains fine, and the final hop is the one affecting your race.
Send the same evidence to iRacing when the problem only shows on its servers or on one specific farm. Keep the report short: which session you joined, when the blinking started, what Q, E, C, and S did, and what the route test showed.
When the same fault keeps coming back after all of that, it’s worth getting a second pair of eyes on it. SimRigSupport runs remote sessions where someone reads your meters and route traces with you, then pins down the hop that keeps costing you races.
Finally, an important thing to note is that iRacing has started backing this up with a rule. In specified official series, a Connection Black Flag pulls a driver to the pits when their connection keeps swinging around. A high ping on its own won’t trigger it, as long as that ping holds steady. Get the connection stable, and the blinking goes with it.
