Watch nodes, filter the leaderboard
Watch any node from its page, no account needed, and find it under Watching on the leaderboard. The board also filters by claimed or unclaimed, your own nodes and hosting provider.
What has changed on KasNodes, newest first. Something missing or wrong? Use Report a problem at the bottom of any page.
Watch any node from its page, no account needed, and find it under Watching on the leaderboard. The board also filters by claimed or unclaimed, your own nodes and hosting provider.
A node on an older kaspad than the newest release says by when to upgrade to keep full marks for software, with the steps and the release notes.
Your node's README badge is offered as soon as a claim is confirmed and beside each node on My nodes. Shared node links now show who runs it, how often it was online and its top-10 streak.
A node that is behind but still syncing is marked Catching up, apart from nodes stuck on an old chain.
Track record, hosting diversity and block relay are measured and shown on every node page, not scored yet. Nodes now have 14 days to upgrade after a new kaspad release.
Every public node is ranked on its own 30-day record. A node joins the board once it has been seen online on 10 separate days.
Reach now takes half again the typical reach for full marks, so being known more widely than typical counts.
How many addresses the network passes around, how many we try, and how few answer. Counts only, never addresses.
Network health shows how much of the network the three largest hosts carry over time, and charts mark each kaspad release and the Toccata hard fork.
See which platforms private nodes run on, such as Kaspa NG.
When a node is known to fewer public nodes than typical for its age, its page says what to check: a fixed forwarded port, or the address it advertises.
Five parts: uptime 50%, stability 15%, software 15%, reach 10% and clock 10%. Each node page shows what every part measured.
Nodes on the same score are marked with =, and placed by the longest time since a down hour, then by how widely the network knows them.
Six vital signs of the public network over a field with one dot per node, and how the count has moved over time.
A node that answers at several addresses keeps a single place on the leaderboard.
A week of connection checks and outages, time since its last restart, clock, platform, chain tip, distance from our sensors and how many public nodes know its address.
Every node has a live badge with its place and score. Copy the Markdown from its page.
How many private nodes run current software, and how that has changed.
Claiming shows steps for your setup, what our last check saw, and the code now lasts a day.
From the footer of any page, or already filled in from a node's page.
Every guide checked against today's releases and the machine a node needs.
A live globe of the Kaspa network, a feed of what is happening now, the leaderboard and network pages, rebuilt from the ground up.