Uptime Leaderboard
Ranked by how much of the window each node was actually registered. Keep your node checking in every 60 seconds and you climb.
How the uptime ranking is calculated
The leaderboard measures heartbeat coverage, not self-reported availability. Every successful check-in a node makes covers the following one hundred and eighty seconds; the registrar adds that coverage up across the selected window and divides it by the time the node was eligible to be online. A node checking in every sixty seconds as intended therefore sits at one hundred percent, and every missed window costs it measurable ground.
Nodes are only measured from the moment they were allocated, so an operator who registered yesterday is not punished for the twenty-nine days before their node existed. The tracked window is capped at thirty days and only public nodes are ranked — a node marked private stays out of the table entirely.
Ties are broken by raw registration count, which rewards a node that checks in promptly over one that only just scrapes inside the heartbeat window. Switching between the seven, fourteen and thirty day views is a quick way to tell a genuinely solid installation from one that has simply had a good week.
If your node is lower than you expected, the outage timeline on its detail page shows exactly when it stopped registering. Most losses come from a keep-alive script that died quietly, an expired registration password, or a router dropping outbound UDP 4569 for the legacy IAX2 path.
How often does the ranking update?
It is computed on request from the registration log and the page refreshes every minute, so a recovered node climbs within a few minutes.
Does a suspended node still count?
A suspended node cannot register, so its coverage stops accruing and it falls down the table for as long as the suspension lasts.