happy-pulse-3608
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
- Uptime99.72% of hours up88.7
- Stability3 unplanned restarts90
- Reach83% of typical for its age55.3
- Track recordseen on 51 of the last 180 days71.1
- Block relay58 ms behind the first to announce98.1
5 other parts at full marksSoftware version, Clock, Responsiveness, Sync, Hosting diversity100
- Software version100
- Clock0.1 s from ours, 30-day median100
- Responsiveness0 ms of its own to answer100
- Sync0.1 s behind the network100
- Hosting diversityprovider has 0.4% of public nodes100
How to gain up to 11.5 points
- +4.5Reachcomes 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.
- +4.5Uptime
0.28% 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.
- +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.
- +1.0Stability
3 unplanned restarts in 30 days, and two are free. Look for crashes in its log, give it the memory and disk it needs, and restart it only to upgrade: a restart that brings a new version costs nothing.
- +0.1Block relay
It passes on new blocks 58 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.7 | 100.0% | 3,326 |
| 18 Nov | 93.5 | 100.0% | 3,369 |
| 17 Nov | 93.0 | 100.0% | 3,368 |
| 16 Nov | 92.7 | 100.0% | 3,424 |
| 15 Nov | 93.2 | 100.0% | 3,287 |
| 14 Nov | 93.2 | 100.0% | 3,429 |
| 13 Nov | 93.5 | 100.0% | 3,572 |
| 12 Nov | 93.5 | 100.0% | 3,582 |
| 11 Nov | 93.8 | 100.0% | 3,577 |
| 10 Nov | 93.6 | 100.0% | 3,570 |
| 9 Nov | 93.9 | 100.0% | 3,589 |
| 8 Nov | 93.8 | 100.0% | 3,574 |
| 7 Nov | 93.4 | 100.0% | 3,315 |
| 6 Nov | 94.1 | 100.0% | 3,233 |
Connection checks, last 7 days99.7% answered
- 14 Nov 14:13–14:28 UTC15 min
Details
- Operator
- Not claimed yet
- Location
- Düsseldorf, Germanyapproximate, from its address
- Provider
- WIIT AGAS24961
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 596,480,632
- Running
- 4 dayssince its last restart
- Latest crawl
- 93.7 / 100
- Peer store
- 3,326 addresses
- Known to
- 39 public nodeshave its address in their peer store
- Distance
- Nuremberg 18 msNew York 90 msSingapore 167 msfastest connect from each of our sensors, last hour
- Responds in
- 19 mskaspad's reply to a ping from our crawler
- Clock
- In syncat 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.