good-chain-1604
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 scoreReach is holding it back most
- Uptime99.57% of hours up84.2
- Reach101% of typical for its age67.5
8 other parts at full marksStability, Software version, Clock, Responsiveness, Sync, Track record, Hosting diversity, Block relay100
- Stability0 unplanned restarts100
- Software version100
- Clock0.5 s from ours, 30-day median100
- Responsiveness0 ms of its own to answer100
- Sync3.3 s behind the network100
- Track recordseen on 127 of the last 180 days100
- Hosting diversityprovider has 1.9% of public nodes100
- Block relay30 ms behind the first to announce100
How to gain up to 9.5 points
- +6.3Uptime
0.43% 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.2Reachcomes 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.
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 | 97.2 | 100.0% | 3,342 |
| 18 Nov | 97.2 | 100.0% | 3,349 |
| 17 Nov | 96.7 | 100.0% | 3,345 |
| 16 Nov | 97.0 | 100.0% | 3,335 |
| 15 Nov | 96.6 | 100.0% | 3,331 |
| 14 Nov | 96.6 | 100.0% | 3,349 |
| 13 Nov | 96.8 | 100.0% | 3,346 |
| 12 Nov | 96.4 | 100.0% | 3,361 |
| 11 Nov | 96.5 | 100.0% | 3,367 |
| 10 Nov | 96.2 | 100.0% | 3,369 |
| 9 Nov | 96.5 | 100.0% | 3,356 |
| 8 Nov | 96.4 | 100.0% | 3,378 |
| 7 Nov | 96.2 | 100.0% | 2,564 |
| 6 Nov | 95.9 | 100.0% | 2,305 |
Connection checks, last 7 days100% answered
No outages. We check every node about every 5 minutes.
Details
- Operator
- Not claimed yet
- Location
- Houston, United Statesapproximate, from its address
- Provider
- Leaseweb USA, Inc.AS394380
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 596,283,508
- Running
- 20 dayssince its last restart
- Latest crawl
- 97.2 / 100
- Peer store
- 3,342 addresses
- Known to
- 112 public nodeshave its address in their peer store
- Distance
- Nuremberg 135 msNew York 38 msSingapore 202 msfastest connect from each of our sensors, last hour
- Responds in
- 131 mskaspad's reply to a ping from our crawler
- Clock
- 0.3 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.