steady-halving-8198
This node's own record over the last 30 days. Its place on the leaderboard comes from this figure alone.
What makes up the scoreClock is holding it back most
- Reach141% of typical for its age94.1
- Clock9.6 s from ours, 30-day median50
- Track recordseen on 51 of the last 180 days71.1
- Block relay92 ms behind the first to announce90.6
6 other parts at full marksUptime, Stability, Software version, Responsiveness, Sync, Hosting diversity100
- Uptime100% of hours up100
- Stability1 unplanned restart100
- Software version100
- Responsiveness0 ms of its own to answer100
- Sync4.1 s behind the network100
- Hosting diversityprovider has 0.4% of public nodes100
How to gain up to 5.0 points
- +2.5Clock
Its clock is 9.6 s off. Turn on time sync: timedatectl set-ntp true on most Linux systems, or install chrony.
- +1.4Track recordcomes with time
Seen on 51 of the last 180 days. Nothing to change: this rises as it keeps answering, day after day.
- +0.6Reachcomes 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.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 | Uptime, 24 h | Peer store |
|---|---|---|---|
| 19 Nov | 93.3 | 100.0% | 3,509 |
| 18 Nov | 93.3 | 100.0% | 3,502 |
| 17 Nov | 93.3 | 100.0% | 3,511 |
| 16 Nov | 93.7 | 100.0% | 3,557 |
| 15 Nov | 93.8 | 100.0% | 3,551 |
| 14 Nov | 93.3 | 100.0% | 3,560 |
| 13 Nov | 93.8 | 100.0% | 3,551 |
| 12 Nov | 93.5 | 100.0% | 3,563 |
| 11 Nov | 93.1 | 100.0% | 3,546 |
| 10 Nov | 93.0 | 100.0% | 3,564 |
| 9 Nov | 93.1 | 100.0% | 3,564 |
| 8 Nov | 93.4 | 100.0% | 3,564 |
| 7 Nov | 93.0 | 100.0% | 1,542 |
| 6 Nov | 92.7 | 100.0% | 1,544 |
Connection checks, last 7 days100% answered
No outages. We check every node about every 5 minutes.
Details
- Operator
- Not claimed yet
- Location
- Dandridge, United Statesapproximate, from its address
- Provider
- Twin Lakes Telephone Cooperative CorporationAS19331
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 596,283,605
- Running
- 14 dayssince its last restart
- Latest crawl
- 93.3 / 100
- Peer store
- 3,509 addresses
- Known to
- 81 public nodeshave its address in their peer store
- Distance
- Nuremberg 127 msNew York 38 msSingapore 234 msfastest connect from each of our sensors, last hour
- Responds in
- 133 mskaspad's reply to a ping from our crawler
- Clock
- 29 s behindat its latest handshake; check its time sync (NTP)
- 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.