Public infrastructure

LearnHNS SPV Helper

Aggregate, privacy-preserving activity for spv.learnhns.com/hsd.

Node healthy

The badge checks node configuration and sync progress. It does not measure request reliability or independently verify the latest network tip.

Want to host your own SPV helper?

Independent operators can run a compatible API on their own hostname. Learn about the indexed HSD backend, restricted gateway, the public MIT-licensed starter, and verification steps.

Read the self-hosting guide →

Recent API reliability · approximately 15 minutes

1,169 API requests · 0 HTTP errors · 0 rate limited · 0 server errors · 0 RPC error responses

Current minute and previous 14 minutes, limited by process uptime. Window: 2026-11-21T09:41:00.000Z to 2026-11-21T09:55:38.000Z.

API requests3,641,037
HTTP successful3,627,481
Rate limited6,429
Upstream failures6,532
Chain height356,736
Sync progress100%
Average latency63.52 ms
Measurement uptime27d 2h 36m

Requests by API category

CategoryRequestsHTTP errorsAverageMaximum
Address history 2,689 901 844.06 ms 10,048.45 ms
Block lookups 268,675 0 21.34 ms 4,625.91 ms
Coin lookups 16,894 508 4.89 ms 205.75 ms
Header lookups 2,714 0 3.37 ms 64.67 ms
Node information 226 0 5.41 ms 39.02 ms
Read-only RPC 3,197,127 2,832 8.6 ms 25,183.48 ms
Transaction lookups 152,712 9,315 1,281.27 ms 10,048.76 ms

Why requests failed

Totals cover this process lifetime. HTTP 429 means throttling, not a node outage. HTTP 404 means a record was not found; a coin may already be spent. Rejected requests include invalid input and blocked RPC methods. Timeouts and other upstream failures need investigation.

RPC error responses are counted here even with HTTP 200; they may reflect invalid parameters or an operation-specific failure. They can overlap HTTP errors. Upstream failures in the summary also include health and analytics probes.

CategoryHTTPReasonTotalRecentLast seen (UTC)
Address history 429 Address-history rate limit 854 0 2026-11-21T00:07:37.000Z
Address history 429 General rate limit 16 0 2026-11-20T15:57:44.000Z
Address history 504 Upstream timeout 31 0 2026-11-16T21:23:12.000Z
Coin lookups 400 Request rejected 4 0 2026-11-17T13:10:23.000Z
Coin lookups 404 Record not found 481 0 2026-11-21T00:24:03.000Z
Coin lookups 429 General rate limit 23 0 2026-11-19T19:47:33.000Z
Read-only RPC 200 RPC returned an error 101 0 2026-11-21T03:28:11.000Z
Read-only RPC 403 Request rejected 6 0 2026-11-17T13:10:57.000Z
Read-only RPC 429 General rate limit 2,826 0 2026-11-20T17:34:58.000Z
Transaction lookups 404 Record not found 293 0 2026-11-20T12:07:52.000Z
Transaction lookups 429 General rate limit 2,710 0 2026-11-20T17:34:58.000Z
Transaction lookups 504 Upstream timeout 6,312 0 2026-11-20T13:36:37.000Z

For rate limits, clients should respect Retry-After, reduce concurrency, and avoid repeated full-history scans. The breakdown distinguishes the general limit from the stricter address-history limit.

Node readiness

NetworkmainHSD version8.99.0
Full nodeYesNon-prunedYes
Transaction indexReadyAddress indexReady