Start by separating network lag from local performance problems. High ping, rubberbanding, packet loss and disconnects point to your connection, the route to a server, or the server itself. Low or stuttering FPS, freezes and crashes point to your PC and game files. For network symptoms, check NAT, firewall and DNS-blocking software, synchronize your system clock, compare regions and servers, and test a wired Ethernet connection. For FPS problems, lower settings, verify Steam files and only then consider reinstalling. Server administrators should direct-connect, check sv_lan, browser filters, map and mode entries, plugins and update parity. Saber Interactive also acknowledges connection and packet-loss incidents affecting multiple server regions, so some cases require escalation rather than a client-side tweak.
Is Insurgency lag caused by the network or by low FPS?
The symptom tells you which troubleshooting path to use. Changing graphics options cannot repair packet loss, while replacing an Ethernet cable will not raise a low rendering frame rate.
| What you notice | Most likely class | First checks |
|---|---|---|
| High ping shown in the scoreboard, delayed hit registration, rubberbanding, packet loss or disconnects | Network, route or server | Check NAT, firewall and DNS blockers; compare regions and servers; test Ethernet |
| Low FPS, regular stutter, freezing or crashes while ping remains normal | Local performance or files | Check system requirements, lower video settings, verify Steam files |
| Many players in different regions lose packets at the same time | Server-side or provider incident | Confirm the scope, record times and affected regions, then monitor official support |
Keep a short record before changing anything: matchmaking region, server name or address, your location, the exact symptom, whether other players are affected, and the date and time. Those details are specifically requested in pinned Insurgency support guidance and make it possible to distinguish a single bad route from a wider outage.
What should I check before changing settings?
Confirm whether other services are affected
Play another online game or use another real-time service on the same connection. If everything else is unstable, investigate your home network or internet service first. If only one Insurgency server or region is problematic, do not assume your graphics settings or computer hardware are responsible.
Identify the scope
- One player: prioritize your NAT, firewall, DNS-blocker, Wi-Fi and clock checks.
- Everyone on one server: the host should inspect its configuration, map rotation, plugins and update state.
- Players across several regions: treat it as a possible provider or game-service incident and collect evidence for escalation.
Make one change at a time
Run a short match or reconnect after each change. If you alter several settings simultaneously, you will not know which one helped and may hide the original cause.
How do I fix high ping, rubberbanding and packet loss as a player?
1. Check firewall and DNS-blocking software
Temporarily review your operating-system firewall and any security, parental-control or DNS-filtering service. Make sure Steam and Insurgency Sandstorm are allowed to communicate, and that the filter is not blocking matchmaking or server traffic. Use a temporary, controlled test rather than leaving protection disabled; restore the normal rules immediately after testing.
2. Check your NAT status
Saber Interactive’s support guidance says, “Your NAT Type should be set to Type 1 (Open).” NAT determines how readily your device can establish and maintain peer and server connections. Check the NAT information in your router or platform network settings, then correct the router configuration according to its manufacturer’s instructions. If your network is managed by a university, workplace or carrier-grade NAT, you may not have permission to change it; record that limitation for your internet provider or support ticket.
3. Synchronize the Windows clock
An incorrect system clock can interfere with authentication and online services. On Windows:
- Press Windows + R.
- Enter
ms-settings:dateandtimeand press Enter. - In the Date & time settings page, select Sync Now.
- Restart Steam and test the same server again.
4. Compare regions and individual servers
Try the same mode in another matchmaking region, then compare two or more servers in the original region. If one server is consistently bad while others are stable, note its name, address if visible, and timestamps. A region change is a diagnostic comparison, not proof that the original region is permanently faulty; internet routes and server load can change during the day.
5. Isolate Wi-Fi variability with Ethernet
Connect the PC directly to the router or modem with a Cat6 Ethernet cable and repeat the test from the same location and at the same time. A wired result that is stable while Wi-Fi is not points to wireless interference, signal strength or local congestion. It does not prove that the game server is healthy, and it cannot fix packet loss occurring beyond your home network.
6. Check for local congestion
Pause large downloads, cloud backups, streaming uploads and other traffic while testing. If lag appears only when another household device is active, the bottleneck is likely local bandwidth or queueing. Router quality-of-service controls may help, but document the before-and-after result instead of assuming a setting worked.
Why is Insurgency stuttering or running at low FPS?
Low frame rate, stutter, freezing and crashes are local-performance symptoms even when they feel like “lag.” Saber’s performance guidance recommends checking all system requirements, adjusting video settings, verifying Steam files and using reinstall only as a last resort.
Check the hardware baseline
Confirm that your operating system, processor, graphics card, memory and available storage meet the game’s published minimum or recommended builds. Saber says those builds are benchmarked to achieve “60 FPS or above >95% of the time” under its stated low and medium-high settings. The page does not state a publication year, so treat this as an undated vendor benchmark claim, not a current guarantee for every map, patch or driver.
Lower settings in the correct menu
- Open Insurgency Sandstorm.
- Go to Settings > Video.
- Lower the most demanding options first, then apply the changes.
- Play the same map or mode long enough to reproduce the stutter.
Change only a few options per test and note the result. If FPS improves but ping remains high, you have two separate problems; continue network troubleshooting rather than lowering settings indefinitely.
Verify Steam files
- Exit the game.
- Open Steam and find Insurgency Sandstorm in your library.
- Right-click it and choose Properties.
- Open Local Files and select Verify Integrity of Game Files.
- Launch the game after Steam completes the check.
Saber recommends running Steam as administrator for this check if file access is failing. Verification can replace damaged or missing files without deleting the whole installation.
Reinstall only after the checks above
A reinstall is slower, consumes bandwidth and may not solve a server or routing problem. Use it only after requirements, video settings and file verification have been addressed. If crashes continue, attach a DxDiag report to your support request so the hardware, drivers and operating-system details can be reviewed.
Is the lag a server-wide incident?
When players in different locations and regions report packet loss or instability at the same time, local changes are unlikely to repair it. Saber’s known-issues notice states: “Thanks to your feedback, we are aware of some connection/packet loss issues affecting players across all server regions. We are actively working with our server provider to resolve this.”
Use the scope test before spending an hour changing router settings: ask teammates in another region to try the same period, test a different server, and compare timestamps. If the problem follows the service rather than your connection, preserve your notes and wait for a provider-side fix or escalate through official support. A wired connection and open NAT are still useful baseline checks, but neither can correct a faulty upstream route or overloaded server.
How can a dedicated-server administrator fix connection and browser problems?
Work through these checks in order. They distinguish a healthy server that is merely undiscoverable from a server that cannot load its map or accept internet clients.
1. Try a direct connection
Open the game console and use:
connect IP:PortIf direct connection succeeds, the process is reachable and attention should shift to server-browser advertising, filters or listing data. If it fails, inspect the server console, firewall and provider network before changing browser settings.
2. Ensure the server is not in LAN mode
Open insurgency/cfg/server.cfg, set:
sv_lan 0Save the file and restart the server. A value of sv_lan 1 prevents advertising and rejects internet connections, so a server can appear to be missing even though its process is running.
3. Remove browser filters that hide the server
Clear filters for empty, full and password-protected servers. Search part of the hostname instead of relying only on the complete name, then add the server to Steam favourites once it appears. Filters affect visibility; they do not reduce ping on a server that is already reachable.
4. Fix map-load hangs
Verify that the selected map supports the selected game mode. Then inspect mapcycle.txt for spelling, capitalization and obsolete entries. A single invalid map name can stall rotation or make a server appear to hang during loading even when the network is fine.
5. Roll back a newly added plugin
If crashes or failed connections began immediately after a plugin change, remove that plugin temporarily and restart. Confirm that every plugin matches the installed SourceMod version before adding it back. Test the unmodified server first; otherwise a plugin can mask a configuration or update problem.
6. Restore update parity
After a game update, restart the server so it receives the same build as clients, then watch the console for download, authentication and map errors. Clients on a newer build may fail to join an older server, and a server that was not restarted can continue advertising stale state.
How do I repair mod-menu or authentication problems?
For many Insurgency Sandstorm mod issues, mod.io recommends resetting the local user-settings file and signing in again:
- Close the game completely.
- Open
%localappdata%InsurgencySavedConfigWindowsClient. - Rename
GameUserSettings.initoGameUserSettings.ini.backup. Renaming preserves a copy you can restore. - Restart the game.
- Sign back into the mod menu and test the affected content.
This reset can remove a corrupted or incompatible local setting, but it does not repair a server-side plugin, an unavailable mod dependency or a game-wide outage. If the issue returns only on one server, give its administrator the mod name, version and console error.
Which remedy fits the symptom, scope and risk?
| Situation | Who can act | Best first action | Reversibility |
|---|---|---|---|
| High ping or packet loss on one PC | Player | NAT, firewall/DNS, clock, region comparison and Ethernet test | Temporary tests; restore security settings afterward |
| Low FPS or crashes with normal ping | Player | Video settings, file verification, then DxDiag-supported escalation | Settings changes are reversible; reinstall is disruptive |
| Server absent from browser but direct connect works | Server administrator | sv_lan 0, clear filters, search hostname and favourite it |
Configuration change requires restart |
| Map-load hang | Server administrator | Validate map/mode pair and mapcycle.txt |
Reversible file edit |
| Crash after plugin installation | Server administrator | Remove the new plugin and match its SourceMod version | Temporary rollback |
| Instability across regions | Game or hosting provider | Record scope and timestamps, monitor support notices and escalate | Not fixed by local settings |
What should I include in a support ticket?
Give support enough information to reproduce or correlate the incident:
- Matchmaking region and your physical location or country.
- Server name, address or port when available.
- Date and exact time, including time zone.
- Whether the symptom is high ping, rubberbanding, packet loss, disconnect, low FPS, freeze or crash.
- Whether another game, another region or another server works.
- Whether teammates or players in other regions see the same problem.
- Your NAT type, firewall/DNS-blocker test result and whether Ethernet changed the outcome.
- For crashes or performance issues, a DxDiag report and the result of Steam file verification.
- For hosted servers, relevant console output, the map and mode, recent plugin changes, and whether the server was restarted after the latest game update.
Do not describe every symptom as “lag.” Precise terms let support route a network incident to the server provider and a rendering issue to the performance team.
What common fixes waste time?
- Lowering graphics to fix ping: video settings change rendering load, not the network route.
- Reinstalling before verifying files: verification is faster and less disruptive for damaged local files.
- Blaming Wi-Fi without testing: Ethernet is an isolation test; a wired connection cannot repair an upstream outage.
- Changing regions randomly: compare specific servers and record times so a temporary route change is not mistaken for a permanent fix.
- Editing a hosted server without a rollback: back up configuration files and remove one plugin or map entry at a time.
- Ignoring update parity: a server that was not restarted after a game update can reject clients or advertise stale information.
When should I stop troubleshooting locally?
Stop making client changes when the same packet-loss pattern appears on multiple devices, in multiple regions or for many unrelated players. At that point, preserve your timestamps and server details and escalate. Likewise, if FPS remains low after settings changes and file verification, provide DxDiag rather than repeatedly reinstalling. The objective is not to find a universal “lag setting”; it is to identify whether the fault belongs to your device, your home network, the route, the server configuration or the provider.
Frequently Asked Questions
Can a normal internet speed test rule out an Insurgency connection problem?
No. A speed test may use a nearby test server and a different route from the one used by Insurgency. A clean result does not exclude peering, routing or packet-loss trouble on the game-server path, so compare actual servers and record timestamps.
Do server-browser filters change my ping?
No. Filters only decide which servers are displayed, such as empty, full or password-protected servers. They can hide a reachable server, but removing a filter does not improve latency after you connect.
Should I keep using a server that works only through direct connect?
Use direct connect as a diagnostic and temporary access method, then fix discovery. Check sv_lan 0, browser filters and hostname search so players can find the server normally and receive current listing information.
What happens if my NAT cannot be changed to Open?
Some managed networks and carrier-grade NAT arrangements do not expose the router controls needed for an Open NAT. Tell support or your internet provider that limitation, include your region and timestamps, and rely on a different network only as a controlled comparison rather than assuming the game server is at fault.