alert-explorer-3089
kaspad 2.1.0 has been out since 22 Sep 2026. This node runs kaspad 2.0.1. Its software part no longer scores full marks until it runs 2.1.0. How to upgrade ยท Release notes
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
- Uptime91.12% of hours up51.3
- Stability8 unplanned restarts40
- Software version75
- Reach53% of typical for its age35.2
- Sync7.5 s behind the network95.5
- Track recordseen on 45 of the last 180 days68.7
- Block relay203 ms behind the first to announce65.9
3 other parts at full marksClock, Responsiveness, Hosting diversity100
- Clock0.4 s from ours, 30-day median100
- Responsiveness2 ms of its own to answer100
- Hosting diversityprovider has 2.3% of public nodes100
How to gain up to 38.0 points
- +19.5Uptime
8.88% 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.
- +6.5Reach
Less known than typical for its age. Check that it advertises an address other nodes can reach (kaspad --externalip).
- +6.0Stability
8 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.
- +2.5Software version
Upgrade to kaspad 2.1.0, the newest release.
- +1.7Block relay
It passes on new blocks 203 ms after the first node. A steady, low-latency connection and spare CPU help; so do more outbound peers (kaspad --outpeers=16).
- +1.6Track recordcomes with time
Seen on 45 of the last 180 days. Nothing to change: this rises as it keeps answering, day after day.
- +0.2Sync
Its chain ran 7.5 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 | โ | 2,383 | |
| 18 Nov | 61.6 | 75.0% | 3,453 |
| 17 Nov | โ | 3,411 | |
| 16 Nov | โ | 3,523 | |
| 15 Nov | โ | 3,514 | |
| 14 Nov | 89.1 | 100.0% | 3,517 |
| 13 Nov | 89.6 | 100.0% | 3,519 |
| 12 Nov | 61.4 | 75.0% | 3,510 |
| 11 Nov | 61.9 | 75.0% | 3,536 |
| 10 Nov | 57.8 | 66.7% | 3,537 |
| 9 Nov | โ | 3,524 | |
| 8 Nov | 89.6 | 100.0% | 3,519 |
| 7 Nov | 88.3 | 100.0% | 3,248 |
| 6 Nov | 82.5 | 100.0% | 1,539 |
Connection checks, last 7 days95.7% answered
- 17 Nov 14:25โ16:45 UTC2.3 h
- 17 Nov 04:21โ04:46 UTC26 min
- 17 Nov 04:00โ04:07 UTC6 min
- 17 Nov 03:47โ03:56 UTC9 min
- 17 Nov 03:15โ03:26 UTC10 min
Details
- Operator
- Not claimed yet
- Location
- Lauterbourg, Franceapproximate, from its address
- Provider
- Contabo GmbHAS51167
- Software
- kaspad 2.0.1
- Chain tip
- Catching upat block 596,274,161
- Runs on
- MyKAI
- Running
- 12 hourssince its last restart
- Peer store
- 2,383 addresses
- Known to
- 39 public nodeshave its address in their peer storeLess known than typical for its age. Check that it advertises an address other nodes can reach (kaspad --externalip).
- Distance
- Nuremberg 7 msNew York 83 msSingapore 798 msfastest connect from each of our sensors, last hour
- Responds in
- 84 mskaspad's reply to a ping from our crawler
- Clock
- 0.6 s behindat its latest handshake
- Seen on
- 29 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.