NIFFELENNETWORK FIELDWORK
Home/Field notes/001
Field note 001 · Fundamentals

Why a great ping
can still feel bad.

Three measurements describe different parts of a connection: latency, jitter, and packet loss. Understanding all three is more useful than chasing the lowest number.

Network basics · Approximately 5 minutes

Latency is the delay.

Latency is how long information takes to travel from your device to a destination and back. A low, consistent round-trip time (RTT) usually helps online games feel responsive. But your game's displayed ping can differ from browser-based measurements because they contact different servers using different protocols.

Distance matters, but so do routing, congestion, local Wi-Fi conditions, and the game server itself.

Jitter is the inconsistency.

Imagine a connection responding in 25, 26, 24, 91, and 28 milliseconds. Its typical response is low, yet that one spike can be noticeable. Jitter describes variation in timing, and different tools calculate it in different ways.

A stable 45 ms connection may feel smoother than one bouncing unpredictably between 15 and 110 ms.

In multiplayer games, irregular delivery can contribute to uneven movement, late state updates, or intermittent stutter. Games use prediction and buffering to mitigate these effects, so the experience also depends on the game's netcode.

Packet loss means missing information.

Packets can disappear because of interference, congestion, routing issues, or equipment problems. Some transports retransmit lost information; real-time game traffic may instead continue with the next update. Either way, the application may notice gaps.

A few isolated drops aren't enough to diagnose their cause. Repeated loss correlated with in-game problems is more informative.

How to investigate

  1. Check close to home: compare a wired connection against Wi-Fi when possible.
  2. Measure over time: run tests during the hours you normally play, not just once.
  3. Compare destinations: a browser test, your router, and a game server may behave differently.
  4. Change one variable: pause heavy uploads, then retest before changing any other setting.
  5. Keep a record: note time of day, server region, connection type, and the symptoms.

What the Niffelen check tells you

Our browser check times HTTPS requests to this site's edge. It can reveal major changes in that path, but it does not measure in-game UDP traffic, actual game-server RTT, or true network-level packet loss.

Think of it as a quick signal, not a verdict.

← Back to field notes