strong-anchor-9975
This node's own record over the last 30 days. Its place on the leaderboard comes from this figure alone.
What makes up the scoreBlock relay is holding it back most
- Reach105% of typical for its age69.8
- Sync6.1 s behind the network98
- Track recordseen on 51 of the last 180 days71.1
- Block relay187 ms behind the first to announce69.6
6 other parts at full marksUptime, Stability, Software version, Clock, Responsiveness, Hosting diversity100
- Uptime100% of hours up100
- Stability1 unplanned restart100
- 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 6.0 points
- +3.0Reachcomes 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.5Block relay
It passes on new blocks 187 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.1 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.8 | 100.0% | 3,508 |
| 18 Nov | 95.9 | 100.0% | 3,510 |
| 17 Nov | 96.8 | 100.0% | 3,501 |
| 16 Nov | 96.4 | 100.0% | 3,520 |
| 15 Nov | 96.2 | 100.0% | 3,475 |
| 14 Nov | 96.8 | 100.0% | 3,477 |
| 13 Nov | 96.5 | 100.0% | 3,465 |
| 12 Nov | 96.8 | 100.0% | 3,484 |
| 11 Nov | 96.1 | 100.0% | 3,471 |
| 10 Nov | 96.6 | 100.0% | 3,482 |
| 9 Nov | 96.6 | 100.0% | 3,471 |
| 8 Nov | 96.0 | 100.0% | 3,482 |
| 7 Nov | 91.1 | 100.0% | 1,495 |
| 6 Nov | 96.8 | 100.0% | 2,361 |
Connection checks, last 7 days100% answered
No outages. We check every node about every 5 minutes.
Details
- Operator
- Not claimed yet
- Location
- Hoi Fu Court, Hong Kongapproximate, from its address
- Provider
- Netsec LimitedAS45753
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 596,283,605
- Running
- 2 dayssince its last restart
- Latest crawl
- 95.8 / 100
- Peer store
- 3,508 addresses
- Known to
- 58 public nodeshave its address in their peer store
- Distance
- Nuremberg 156 msNew York 199 msSingapore 32 msfastest connect from each of our sensors, last hour
- Responds in
- 172 mskaspad's reply to a ping from our crawler
- Clock
- 0.4 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.