ready-dag-0510
This node's own record over the last 30 days. Its place on the leaderboard comes from this figure alone.
- Through the forkOnline before and after the Toccata hard fork, 30 Jun 2026
- 100 days seenAnswered our crawls on that many days ยท earned 4 Nov 2026
What makes up the scoreStability is holding it back most
- Uptime74.40% of hours up41.3
- Stability10 unplanned restarts20
- Reach74% of typical for its age49.2
- Track recordseen on 98 of the last 180 days90.6
- Block relay56 ms behind the first to announce98.6
5 other parts at full marksSoftware version, Clock, Responsiveness, Sync, Hosting diversity100
- Software version100
- Clock0.5 s from ours, 30-day median100
- Responsiveness3 ms of its own to answer100
- Sync1.7 s behind the network100
- Hosting diversityprovider has 0.8% of public nodes100
How to gain up to 37.2 points
- +23.5Uptime
25.60% 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.
- +8.0Stability
10 unplanned restarts in 30 days, and two are free. Look for crashes in its log, give it the memory and disk it needs, and restart it only to upgrade: a restart that brings a new version costs nothing.
- +5.1Reach
Less known than typical for its age. Check that it advertises an address other nodes can reach (kaspad --externalip).
- +0.5Track recordcomes with time
Seen on 98 of the last 180 days. Nothing to change: this rises as it keeps answering, day after day.
- +0.1Block relay
It passes on new blocks 56 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 | Uptime, 24 h | Peer store |
|---|---|---|---|
| 19 Nov | 93.8 | 100.0% | 3,547 |
| 18 Nov | 93.5 | 100.0% | 3,543 |
| 17 Nov | 94.1 | 100.0% | 3,534 |
| 16 Nov | 68.4 | 83.3% | 3,542 |
| 15 Nov | 93.8 | 100.0% | 3,495 |
| 14 Nov | 68.6 | 83.3% | 3,419 |
| 13 Nov | 93.8 | 100.0% | 3,477 |
| 12 Nov | 93.7 | 100.0% | 3,474 |
| 11 Nov | 93.8 | 100.0% | 3,474 |
| 10 Nov | 61.1 | 54.2% | 3,598 |
| 9 Nov | โ | ||
| 8 Nov | 93.5 | 100.0% | 3,467 |
| 7 Nov | 88.1 | 100.0% | 2,981 |
| 6 Nov | 91.4 | 100.0% | 3,209 |
Connection checks, last 7 days97.3% answered
- 16 Nov 06:52โ08:22 UTC1.5 h
- 16 Nov 04:32โ06:32 UTC2 h
- 16 Nov 04:12โ04:22 UTC10 min
- 16 Nov 03:42โ03:52 UTC10 min
- 16 Nov 03:22โ03:32 UTC11 min
Details
- Operator
- Not claimed yet
- Location
- Lyon, Franceapproximate, from its address
- Provider
- Free SASAS12322
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 596,283,615
- Running
- 2 dayssince its last restart
- Latest crawl
- 93.8 / 100
- Peer store
- 3,547 addresses
- Known to
- 82 public nodeshave its address in their peer storeLess known than typical for its age. Check that it advertises an address other nodes can reach (kaspad --externalip).
- Distance
- Nuremberg 25 msNew York 88 msSingapore 172 msfastest connect from each of our sensors, last hour
- Responds in
- 35 mskaspad's reply to a ping from our crawler
- Clock
- 0.5 s behindat its latest handshake
- Seen on
- 22 of the last 30 days
- Penalties
- None in the last 30 days
- Badge
- Card
- See it
Something wrong here? Report it
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.