Stats aggregates network-wide XRP Ledger metrics so you can answer "is the network healthy?" and "what's the load profile today?" without running your own indexer.

Live at stats.honeycluster.io.

Stats reads from the same Clio cluster that powers the API. Counts are aggregated in short windows (typically 1-minute buckets) and kept in Honeycluster's analytics store — see @honeycluster/db's analytics schema in the monorepo for the exact shape.

Nothing on this page is secret or proprietary — every number comes from public XRPL data you could compute yourself with a full-history Clio node and enough patience.

• •
  Capacity planning — check peak throughput for the last 7 days before you size a listener or a database.
• •
  Incident correlation — if your integration sees an error spike, the Stats page tells you whether the network also hiccupped or whether the problem is local to you.
• •
  Geographic rollout — the geolocation map helps pick regions for latency-sensitive deployments. Honeycluster routes to the nearest healthy region automatically, but you still want to know where the validator density is.
• •
  Ecosystem research — the domains view surfaces which projects are active on-chain, useful for tracking integrations or partnership outreach.

Because Stats reads the same data plane as the API, a dashboard you build yourself on top of Honeycluster will match the numbers here. If there's a divergence, it's almost always a time-window mismatch — Stats uses closed ledger boundaries, not wall-clock seconds.

See Full-History Queries (coming soon) for how to replicate specific Stats charts in your own code.