agile-script-8150
This node's own record over the last 30 days. Its place on the leaderboard comes from this figure alone.
What makes up the scoreUptime is holding it back most
- Uptime69.98% of hours up38.9
- Reach90% of typical for its age60.2
- Track recordseen on 42 of the last 180 days67.4
- Block relay55 ms behind the first to announce98.9
6 other parts at full marksStability, Software version, Clock, Responsiveness, Sync, Hosting diversity100
- Stability1 unplanned restart100
- Software version100
- Clock0.3 s from ours, 30-day median100
- Responsiveness0 ms of its own to answer100
- Sync0.7 s behind the network100
- Hosting diversityprovider has 0.4% of public nodes100
How to gain up to 30.1 points
- +24.4Uptime
30.02% 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.
- +4.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.6Track recordcomes with time
Seen on 42 of the last 180 days. Nothing to change: this rises as it keeps answering, day after day.
- +0.1Block relay
It passes on new blocks 55 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 | Not seen that day | ||
| 18 Nov | Not seen that day | ||
| 17 Nov | Not seen that day | ||
| 16 Nov | — | ||
| 15 Nov | 92.7 | 100.0% | 3,501 |
| 14 Nov | 56.9 | 43.5% | 3,494 |
| 13 Nov | Not seen that day | ||
| 12 Nov | Not seen that day | ||
| 11 Nov | Not seen that day | ||
| 10 Nov | — | ||
| 9 Nov | 94.3 | 100.0% | 3,467 |
| 8 Nov | 93.7 | 100.0% | 3,487 |
| 7 Nov | 55.0 | 41.2% | 2,815 |
| 6 Nov | Not seen that day | ||
Connection checks, last 7 days96.7% answered
- Since 16 Nov 20:21 UTCstill not answering
- 14 Nov 10:15–21:08 UTC10.9 h
Details
- Operator
- Not claimed yet
- Location
- Paris, Franceapproximate, from its address
- Provider
- Bouygues Telecom SAAS5410
- Software
- kaspad 2.1.0
- Chain tip
- In syncblock 594,329,450
- Peer store
- 3,485 addresses
- Distance
- Nuremberg no answerNew York no answerSingapore no answerfastest connect from each of our sensors, last hour
- Responds in
- 26 mskaspad's reply to a ping from our crawler
- Seen on
- 21 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.