open-testnet-1715
kaspad 2.1.0 has been out since 22 Sep 2026. This node runs kaspad 2.0.1. Its software part no longer scores full marks until it runs 2.1.0. How to upgrade ยท Release notes
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 scoreBlock relay is holding it back most
- Uptime85.26% of hours up47.4
- Software version75
- Reach116% of typical for its age77.3
- Sync5.6 s behind the network98.9
- Block relay295 ms behind the first to announce45.6
5 other parts at full marksStability, Clock, Responsiveness, Track record, Hosting diversity100
- Stability1 unplanned restart100
- Clock1.4 s from ours, 30-day median100
- Responsiveness0 ms of its own to answer100
- Track recordseen on 123 of the last 180 days100
- Hosting diversityprovider has 0.4% of public nodes100
How to gain up to 28.7 points
- +21.1Uptime
14.74% 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.
- +2.7Block relay
It passes on new blocks 295 ms after the first node. A steady, low-latency connection and spare CPU help; so do more outbound peers (kaspad --outpeers=16).
- +2.5Software version
Upgrade to kaspad 2.1.0, the newest release.
- +2.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.
- +0.1Sync
Its chain ran 5.6 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 | 93.4 | 100.0% | 3,532 |
| 18 Nov | 93.3 | 100.0% | 3,527 |
| 17 Nov | 93.2 | 100.0% | 3,531 |
| 16 Nov | 93.2 | 100.0% | 3,542 |
| 15 Nov | 93.2 | 100.0% | 3,547 |
| 14 Nov | 93.1 | 100.0% | 3,548 |
| 13 Nov | 93.0 | 100.0% | 3,550 |
| 12 Nov | 90.3 | 100.0% | 3,551 |
| 11 Nov | 33.0 | 6.7% | 3,551 |
| 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 | โ | ||
Connection checks, last 7 days100% answered
No outages. We check every node about every 5 minutes.
Details
- Operator
- Not claimed yet
- Location
- Brisbane, Australiaapproximate, from its address
- Provider
- LeaptelAS134090
- Software
- kaspad 2.0.1
- Chain tip
- In syncblock 596,283,396
- Runs on
- Kaspa NG
- Running
- 7 dayssince its last restart
- Latest crawl
- 93.4 / 100
- Peer store
- 3,532 addresses
- Known to
- 108 public nodeshave its address in their peer store
- Distance
- Nuremberg 257 msNew York 204 msSingapore 107 msfastest connect from each of our sensors, last hour
- Responds in
- 261 mskaspad's reply to a ping from our crawler
- Clock
- 1.4 s behindat its latest handshake
- Seen on
- 26 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.