RigSight

Building RigSight

Checking ping without asking anyone's server

The rebuilt Network page checks your ping every 5 seconds, and it doesn't ask any outside server to do it. How RigSight finds your provider's first router, the router that ignored empty pings, and the colour rule the page follows.

Ping checked every: 5 s, router and provider, no outside server

The short version

RigSight 1.4.0 checks ping every 5 seconds to your router and your provider's first router, found the way a traceroute does, so no outside server is ever asked. My router ignored empty pings, and usage is never shown as a warning.

Until November, RigSight's Network page only counted data. How much each app downloaded and uploaded, what moved while you were away, when the connection dropped. I had left ping out on purpose. On 4 November I rebuilt the page, and this time ping went in, because ping is what you actually feel in a game.

Whose server?

Measuring ping means sending something somewhere and timing the answer. Many tools ping a big public server, such as one run by Google or Cloudflare. My first plan did the same. Then I asked why RigSight should talk to anyone's server at all, when the internet you use already starts at your provider's own equipment.

So RigSight pings two places, and neither is a public server. The first is your router, the home side of the line. The second is your internet provider's first router after it, where your provider's side starts. Between the two, a spike tells you whether the trouble is in your home or past it.

Finding the provider's router takes a small trick. RigSight sends pings that may only travel a few hops before they expire, the way a traceroute does. Each one dies at a router along the way, and that router sends back a note saying so. The first note that comes from outside your home is your provider's router. The pings are aimed at an internet address only to pick the way out, and they never get there.

5 sHow often RigSight pings your router and your provider's first router. It looks for the provider's router again every half hour, in case it moved.

The router that ignored empty pings

The first build didn't work on my own router. The pings to it went unanswered every time, while Windows' own ping command got answers straight away. The difference turned out to be what was inside the ping. RigSight's were empty, filled with zeros, and Windows fills its pings with letters. My router simply ignored the empty ones. Now RigSight fills its pings the way Windows does.

There was one more catch on my PC. I use a VPN, Cloudflare WARP, which routes traffic through its own tunnel. Pings sent the normal way would go into the tunnel and measure the VPN instead of my line. RigSight sends its pings from the network card's own address, so a VPN can't hide the real line.

Usage is never a warning

In the first mock-up of the new page, a line said that OBS sent 4.1 GB in an hour, coloured amber. It was wrong. Using the internet isn't bad, and on RigSight amber already means stutters on the Games page. So the page has a rule. Usage is never shown in warning colours. Ping peaks are marked in the ping line's own blue. Amber is kept for drops and for data that got lost.

Two more things changed after trying the mock-ups. The live view went to the top of the page and stayed open, because hiding what's using your internet right now behind a click made it worse. And usage and ping became one graph with a switch, instead of two graphs stacked on top of each other.

The rebuilt page went out in version 1.4.0, along with alerts when the internet drops. The ping checks have already caught real spikes on my own line. There's more on reading them in ping spikes while gaming, and on drops in internet keeps disconnecting on PC.

Later: games and calls

One evening Discord showed lost packets and high ping while both checks stayed at 1 ms. The call was on a server in Singapore, about 97 ms away, and nothing RigSight checked was that far. So from version 1.14.0, while a game, a call or remote play is online, RigSight also checks the server that app is already talking to, every 5 seconds. It only asks servers your apps already use, it needs admin rights to see which one that is, and Settings has a switch for it. Your router and your provider are still checked the same way.