alert-store-1654
This node's own record over the last 30 days. Its place on the leaderboard comes from this figure alone.
What makes up the scoreUptime is holding it back most
- Uptime46.81% of hours up26.0
- Reach82% of typical for its age54.8
- Track recordseen on 38 of the last 180 days65.8
- Block relay92 ms behind the first to announce90.7
5 other parts at full marksStability, Software version, Clock, Sync, Hosting diversity100
- Stability1 unplanned restart100
- Software version100
- Clock0.7 s from ours, 30-day median100
- Sync1.3 s behind the network100
- Hosting diversityprovider has 0.4% of public nodes100
How to gain up to 38.3 points
- +31.2Uptime
53.19% of hours went unanswered. Keep it running around the clock: restart it on failure (systemd Restart=always, or restart: unless-stopped in Docker), keep the machine on power it can ride out, and keep its port forwarded.
- +4.8Reachcomes with time
Fewer public nodes keep its address than typical for its age. Keep the same address and port: an address takes months to spread, and every change starts it again.
- +1.8Track recordcomes with time
Seen on 38 of the last 180 days. Nothing to change: this rises as it keeps answering, day after day.
- +0.5Block relay
It passes on new blocks 92 ms after the first node. A steady, low-latency connection and spare CPU help; so do more outbound peers (kaspad --outpeers=16).
Costliest first. The score covers the last 30 days, so a fix shows over the days that follow.
Show the last 14 days of crawls
| Crawl | Reading | Peer store |
|---|---|---|
| 19 Nov | Not seen that day | |
| 18 Nov | Not seen that day | |
| 17 Nov | Not seen that day | |
| 16 Nov | Not seen that day | |
| 15 Nov | Not seen that day | |
| 14 Nov | Not seen that day | |
| 13 Nov | Not seen that day | |
| 12 Nov | Not seen that day | |
| 11 Nov | Not seen that day | |
| 10 Nov | Not seen that day | |
| 9 Nov | Not seen that day | |
| 8 Nov | Not seen that day | |
| 7 Nov | Not seen that day | |
| 6 Nov | Not seen that day | |
Is this your node?
Claim it and your name goes on its row on the leaderboard. Add a one-time code to the node's name tag and keep it online; we check every 30 seconds and confirm automatically.