sv_maxping FiveM Guide - Complete Server Network Configuration 2026

sv_maxping sets the maximum allowed ping (in milliseconds) for players on your FiveM server. Players whose ping exceeds this value are automatically kicked after a grace period. The default value varies by FiveM build but is typically around 150-200ms. How it works: FiveM checks each player's ping every few seconds. If ping exceeds sv_maxping for a sustained period (configurable via sv_maxping_grace), the player receives a warning. If ping remains high beyond the grace period, they're kicked with a 'Connection timed out' message. Important: sv_maxping measures round-trip time (RTT) from the player to your server - it's not just the player's internet speed but also their geographic distance to your server node.

Based on server type: Casual RP servers (32-64 slots): 250-300ms. This accommodates international players while filtering out truly problematic connections. Competitive/PvP servers: 150-200ms. Lower limit ensures fair gameplay, but may exclude players from distant regions. Racing servers: 100-150ms. Racing physics require low latency for fair times. Large communities (128+ slots): 300-350ms. With OneSync Infinity, you want to maximize player count - set higher and let server performance handle varying connections. Global communities (mixed regions): 300ms minimum. If your players are worldwide (Singapore, UK, Germany, Australia), set at least 300ms to not kick distant players. Never set below 100ms unless you're running a LAN-only event.

Complete your network configuration with these settings: sv_maxping_grace [seconds] - how long a player can exceed sv_maxping before being kicked. Default is 15 seconds, we recommend 30 seconds (players with temporary lag spikes won't be kicked). sv_maxclients [number] - max concurrent players, should match your plan's capacity. sv_endpoint_bandwidth_up/down [bytes] - bandwidth limits, set high (100000000 = 100 Mbps) for game server hosting. onesync_enabled 1 - enables OneSync which greatly improves player synchronization. onesync_distance [meters] - sync distance, 500 is standard for RP. sv_maxPingTrend [seconds] - average ping calculation window, 3-5 seconds is reasonable. sv_rconPassword - set a strong password for remote console access.

If your community has players from multiple continents: accept that ping will vary by region. A UK player on a Germany server gets 15ms. A Sri Lankan player on the same server gets 150-180ms. That's not the Sri Lankan player's fault - it's physics (speed of light across 8,000km of fiber). Solutions: set sv_maxping at 300ms to include all regions. Use a server location that's central to your player base (Frankfurt for Europe, Singapore for Asia). Consider running multiple servers in different regions connected via API (not possible for a single RP server, but for minigames). Alternatively, use a VPS to host multiple FiveM instances on one machine in different data center locations. CyberNex has nodes in 12+ global locations - choose the one closest to your majority player base.

High-ping players (200+ ms) experience: delayed vehicle response (press W, car moves 0.2 seconds later), desync with other players (appear to teleport), rubberbanding (movement corrections), and difficulty in combat (shots register late). Low-ping players (<30ms): near-instant response, smooth interactions, fair combat. The sv_maxping setting is a tradeoff: higher values = more players can join, but high-ping players may have a poor experience (and affect others). Lower values = better gameplay quality for everyone, but you may exclude legitimate international players. Our recommendation: set sv_maxping to 300ms for general RP servers. Add a Discord channel where kicked players can appeal if they had a temporary issue.

If many players complain about high ping: check your server location - are you hosting in Germany but 80% of players are in South America? Relocate to a more central node. Check server resource usage - CPU at 100% causes delayed packet processing, which manifests as high ping. Open txAdmin Performance Monitor and check TPS. Check DDoS status - an ongoing attack can saturate bandwidth, increasing latency for everyone. CyberNex control panel shows attack alerts. Check the player's own connection - some players blame the server for their ISP's routing issues. Ask them to run 'ping [serverIP]' in command prompt and share results. If a specific ISP is routing poorly, they can use a gaming VPN (like ExitLag) to get a better route.