lively-anchor-9492
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 20 Oct 2026
What makes up the scoreStability is holding it back most
- Uptime99.71% of hours up88.6
- Stability25 unplanned restarts0
- Reach100% of typical for its age66.7
- Sync7.5 s behind the network95.5
- Block relay314 ms behind the first to announce41.2
5 other parts at full marksSoftware version, Clock, Responsiveness, Track record, Hosting diversity100
- Software version100
- Clock1.0 s from ours, 30-day median100
- Responsiveness0 ms of its own to answer100
- Track recordseen on 127 of the last 180 days100
- Hosting diversityprovider has 0.4% of public nodes100
How to gain up to 21.0 points
- +10.0Stability
25 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.
- +4.6Uptime
0.29% 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.
- +3.3Reachcomes 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.
- +2.9Block relay
It passes on new blocks 314 ms after the first node. A steady, low-latency connection and spare CPU help; so do more outbound peers (kaspad --outpeers=16).
- +0.2Sync
Its chain ran 7.5 s behind the network. Usually a slow disk or a busy CPU; check it meets the requirements and keeps 8 or more peers.
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 | 95.2 | 100.0% | 3,544 |
| 18 Nov | 95.3 | 100.0% | 3,543 |
| 17 Nov | 95.5 | 100.0% | 3,503 |
| 16 Nov | 95.2 | 100.0% | 3,525 |
| 15 Nov | 95.1 | 100.0% | 3,501 |
| 14 Nov | 95.1 | 100.0% | 3,488 |
| 13 Nov | 95.1 | 100.0% | 3,547 |
| 12 Nov | 95.5 | 100.0% | 3,548 |
| 11 Nov | 95.4 | 100.0% | 3,540 |
| 10 Nov | 95.6 | 100.0% | 3,521 |
| 9 Nov | — | ||
| 8 Nov | 96.0 | 100.0% | 3,495 |
| 7 Nov | 95.6 | 100.0% | 1,520 |
| 6 Nov | 96.1 | 100.0% | 2,023 |
Connection checks, last 7 days99.2% answered
- 18 Nov 02:16–03:37 UTC81 min
- 15 Nov 00:22–00:32 UTC10 min
- 14 Nov 03:05–03:55 UTC50 min
Details
- Operator
- Not claimed yet
- Location
- Chajarí, Argentinaapproximate, from its address
- Provider
- ItelsaAS263236
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 596,283,605
- Running
- 24 hourssince its last restart
- Latest crawl
- 95.2 / 100
- Peer store
- 3,544 addresses
- Known to
- 95 public nodeshave its address in their peer store
- Distance
- Nuremberg 253 msNew York 174 msSingapore 384 msfastest connect from each of our sensors, last hour
- Responds in
- 262 mskaspad's reply to a ping from our crawler
- Clock
- 0.8 s behindat its latest handshake
- Seen on
- 30 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.