Ping spikes: what causes them and how to find yours

Your ping sits at 30 ms, then jumps to 200 for a second and you rubber-band into a wall. That jump is a ping spike. It always starts in one of five places, and each has a different fix, so the first job is finding which one is yours.

The five places a spike can start

1. Your PC. A launcher starts a download, Windows fetches an update, a cloud-sync program uploads a folder. Anything that fills your connection makes the game wait its turn.
2. Your home network. Wi-Fi is the usual suspect: a neighbour's router on the same channel, a wall, a microwave. So is the rest of the household. One person uploading a video can stall everyone else's game.
3. Your provider's network. Lines get busy in the evening. If spikes arrive around the same hours every day and vanish at night, this is likely.
4. The route between your provider and the game. Your traffic crosses several networks on its way to the game's data centre. Providers pick those paths by cost and agreements, not by speed, and a busy or roundabout link along the way shows up as spikes in one game while everything else feels fine.
5. The game server. If everyone in the match stutters at the same moment, it isn't you.

Find yours in ten minutes

You need a Windows terminal (press Win, type cmd, Enter) and two commands. Run them while the spikes are happening, or you'll measure a healthy connection and learn nothing.

1. Find your router's address. Run ipconfig and note the "Default Gateway", often 192.168.1.1.
2. Ping the router. ping -n 50 192.168.1.1 (with your gateway's address). Over a cable, every reply should take about 1 ms. Over Wi-Fi a few milliseconds is normal. Replies of 50 or 200 ms here, or lost ones, mean the problem is inside your home: steps 1 and 2 above.
3. Ping something outside. ping -n 50 1.1.1.1. If the router was steady but this isn't, the problem is your line or your provider. Check that nothing in the house is downloading or uploading before you blame them.
4. Compare games. If both tests are clean and one game still spikes, it's the route to that game's servers, or the servers themselves. Ask a teammate on another provider whether they see it too.

What fixes each one

• Your PC: pause downloads and sync while you play. Launchers and cloud storage are the common ones.
• Wi-Fi: use a network cable if you possibly can. If not, see Wi-Fi or Ethernet for gaming for what helps.
• A busy household: many routers have a setting that keeps one device from starving the others, usually called QoS or SQM. It's worth switching on if your spikes follow someone else's uploads.
• Your provider: report it with your measurements and the times. A pattern is harder to dismiss than "the internet is slow".
• The route: you can't change the path your provider chose, but your game's traffic can take a different one. That's what game routing does.
• The game server: nothing on your side helps. Try another server or region.

Where NoSpike fits

NoSpike deals with the fourth cause, and only that one. It measures your direct route to the game server, measures the route through each of its own relays in Europe, and sends your game through a relay only when that's the better path. It checks again every minute while you play.

It can't fix Wi-Fi, a full line or a struggling game server, and it says so: when your own route is already the fastest, the app tells you and leaves your connection alone. Its network check runs the steps above for you and shows where along the way the delay appears.

Not sure what the numbers mean? Ping, jitter and packet loss explains each one.