Starlink Jitter: How to Measure Ping Spikes and Reduce Them

Jitter is the variation between one latency result and the next. A Starlink connection can show a good average ping and still feel unreliable if the delay jumps sharply during a call, game, or live stream.

This guide helps you measure the pattern, identify where it starts, and make the smallest useful change.

What jitter looks like

Jitter is not the same as slow download speed:

• High average latency: every packet is delayed by roughly the same amount.
• Jitter: packet delay moves up and down from one result to the next.
• Packet loss: packets never arrive and must be retried.
• An outage: the connection drops entirely for a period of time.

These problems can overlap, but the remedy is different for each one. Do not replace equipment based on a single speed test.

Prepare a useful test

Before measuring:

1. Use one device and stay in the same room for every test.
2. Pause cloud backups, large uploads, game updates and video uploads.
3. Disconnect a VPN temporarily if your normal troubleshooting allows it.
4. Use Ethernet to the Starlink router or your own router when possible. If you must use Wi-Fi, test close to the router first.
5. Record the time, whether the network was idle or busy, and whether other devices were active.

Run tests at least three times. A single result cannot show whether the problem is steady, local or caused by a busy connection.

Measure jitter in layers

1. Check the Starlink app

Review the app's service status, outage history and obstruction information. Note whether the time of a noticeable interruption lines up with an outage or an obstruction event.

The app is useful for checking the dish and service path, but it does not prove that every delay is caused by the satellite link. A strong Starlink connection can still feel bad when a Wi-Fi link or a busy upload is the bottleneck.

2. Run a simple ping test

From a computer on the same network, send a series of pings to a stable public host.

On Windows PowerShell:

On macOS or Linux:

Run the command once while the network is quiet and once while a known upload or download is active. Look at the individual times, the average, and any timeouts. If the host does not answer, use another stable test host; a missing reply by itself is not proof of a Starlink fault.

You are looking for a pattern such as 35 ms, 42 ms, 38 ms, then 400 ms and 500 ms. That jump is more important than the average alone.

3. Compare wired and Wi-Fi results

Repeat the same test:

• On Ethernet near the router.
• On Wi-Fi in the room where the problem occurs.
• With the network idle.
• While the network is busy.

Use the comparison to narrow the cause:

• Ethernet stable, Wi-Fi spikes: suspect local Wi-Fi coverage or interference. Test closer to the router, improve placement or use wired backhaul.
• Idle stable, upload causes spikes: suspect queueing or bufferbloat. Limit uploads or enable SQM on the router managing your LAN.
• Ethernet and Wi-Fi both spike while idle: investigate the dish, service path, cable or power. Check the app's status and obstruction information, then document the times.
• Only one device or app is affected: suspect the device, VPN, security software or app path. Test another device and temporarily isolate that software.
• Delay is consistently high but steady: this is latency rather than jitter. Check distance, service conditions and the application's requirements.

Reduce jitter in the right order

1. Control busy uploads

A saturated upload queue is a common cause of ping spikes. Pause sync jobs and uploads, then test again.

If the spikes disappear only when uploads stop, set an upload limit below the maximum measured speed. Start around 80 to 90 percent of the real upload rate and adjust carefully. If you use your own router, enable Smart Queue Management (SQM) or an equivalent queue-control feature. Configure it on the router that actually routes your devices; a setting on an unused access point will not help.

Do not stack several competing QoS systems without testing. One correctly placed queue-control setting is easier to verify.

2. Improve the local Wi-Fi path

If Ethernet is clean but Wi-Fi is not:

• Test near the router before buying anything.
• Move the router into an open, central location instead of a closed cabinet.
• Keep the test device away from large metal objects and obvious sources of interference.
• Use Ethernet for a gaming console, work computer or streaming encoder when practical.
• If you use mesh, test the backhaul. A wireless mesh hop can add another busy link even when the Starlink connection is healthy.

Do not change Starlink dish settings to solve a problem that only appears on one Wi-Fi device.

3. Isolate VPNs and background software

A VPN, endpoint security tool, remote desktop session or cloud-sync client can add delay or create its own queue. Test with one change at a time so you know which change helped. Restore normal protection after the test.

4. Check the dish and service path

If wired devices on an otherwise idle network show the same spikes:

1. Check the Starlink app for service events and obstructions.
2. Inspect the visible cable and connectors for loose seating, sharp bends or damage.
3. Confirm that the router and dish have stable power.
4. Restart the system once if it has been running abnormally. Give it time to reconnect and retest.
5. Avoid a factory reset unless the evidence points to a configuration problem and you have a recovery plan.

Repeatedly rebooting can hide the pattern you need to diagnose.

Make calls and gaming more tolerant

For a video call, game or live stream:

• Prefer Ethernet or a strong nearby Wi-Fi connection.
• Pause large uploads and cloud synchronization during the session.
• Use SQM or a single, well-tested QoS policy when your router supports it.
• Keep a short log of the time, device, connection type, idle or busy state, and result.
• Reduce video quality only after checking the network path; lowering resolution will not fix a saturated queue.

A stable connection with moderate latency is usually more usable than a faster connection with repeated large spikes.

When to contact Starlink support

Contact support after you have documented a repeatable pattern, especially when:

• Multiple devices show the issue over Ethernet and Wi-Fi.
• The problem remains while the network is idle.
• The app shows outages or persistent obstruction events.
• Cable, power and local-network checks do not change the result.

Include the timestamps, test method, whether the network was busy, the affected devices, and screenshots from the app. That gives support something more useful than a single speed-test number.

Quick checklist

• Measure idle and busy conditions separately.
• Compare Ethernet with Wi-Fi.
• Treat jitter, packet loss and outages as different symptoms.
• Fix upload queueing before replacing hardware.
• Change one thing at a time and keep the test notes.
• Escalate with timestamps and evidence when wired devices still show persistent spikes.