free-pow-8582
This node's own record over the last 30 days. Its place on the leaderboard comes from this figure alone.
What makes up the scoreReach is holding it back most
- Reach79% of typical for its age52.4
- Sync6.0 s behind the network98.2
- Track recordseen on 51 of the last 180 days71.1
- Block relay195 ms behind the first to announce67.8
6 other parts at full marksUptime, Stability, Software version, Clock, Responsiveness, Hosting diversity100
- Uptime100% of hours up100
- Stability0 unplanned restarts100
- Software version100
- Clock0.8 s from ours, 30-day median100
- Responsiveness0 ms of its own to answer100
- Hosting diversityprovider has 0.4% of public nodes100
How to gain up to 7.9 points
- +4.8Reachcomes 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.
- +1.6Block relay
It passes on new blocks 195 ms after the first node. A steady, low-latency connection and spare CPU help; so do more outbound peers (kaspad --outpeers=16).
- +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.1Sync
Its chain ran 6.0 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.1 | 100.0% | 3,257 |
| 18 Nov | 95.1 | 100.0% | 3,266 |
| 17 Nov | 95.1 | 100.0% | 3,253 |
| 16 Nov | 95.4 | 100.0% | 3,274 |
| 15 Nov | 94.6 | 100.0% | 3,263 |
| 14 Nov | 94.4 | 100.0% | 3,251 |
| 13 Nov | 94.2 | 100.0% | 3,264 |
| 12 Nov | 94.2 | 100.0% | 3,276 |
| 11 Nov | 94.2 | 100.0% | 3,282 |
| 10 Nov | 94.2 | 100.0% | 3,276 |
| 9 Nov | 94.3 | 100.0% | 3,292 |
| 8 Nov | 94.5 | 100.0% | 3,287 |
| 7 Nov | 94.0 | 100.0% | 2,231 |
| 6 Nov | 93.6 | 100.0% | 2,211 |
Connection checks, last 7 days100% answered
No outages. We check every node about every 5 minutes.
Details
- Operator
- Not claimed yet
- Location
- Tokyo, Japanapproximate, from its address
- Provider
- N963 PTE. LTD.AS963
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 596,283,524
- Running
- 50 dayssince its last restart
- Latest crawl
- 95.1 / 100
- Peer store
- 3,257 addresses
- Known to
- 55 public nodeshave its address in their peer store
- Distance
- Nuremberg 275 msNew York 150 msSingapore 68 msfastest connect from each of our sensors, last hour
- Responds in
- 271 mskaspad's reply to a ping from our crawler
- Clock
- 0.6 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.