Status is Honeycluster's public uptime page. Every region, every upstream (Clio and rippled), and every public endpoint is health-checked on a tight interval; the results are published here with no delay.

Live at status.honeycluster.io.

An endpoint is reported as operational when:

1. •
   Health probes complete within the latency SLO for the region.
2. •
   The upstream Clio or rippled node passes ledger-validation checks (it's on the current consensus head, not a stale replica).
3. •
   Edge proxies in the region can reach the upstream and have capacity to accept new connections.

A failed condition in any of these demotes the region to degraded (still serving, slower) or down (failing over to the next region). DNS + GeoIP routing automatically steers traffic away from a demoted region; Status is how you see that happening externally.

Most integrations don't need to poll Status — the edge proxy's regional failover is transparent from the client's perspective, and retries with backoff handle the rare 5xx that leaks through during a failover window.

The exception is a control-plane app that wants to surface network health to its users (exchanges, wallets, dashboards). In that case, scrape the Status feed on a 30-second interval and cache locally — don't hot-poll on every request.

When an incident is created, Honeycluster on-call updates the page with investigating → identified → monitoring → resolved state transitions and timestamped notes. After resolution, a postmortem link is added within 72 hours for major incidents.

If your integration is affected and you don't see a matching incident on the Status page, that's a signal the issue might be local to your setup rather than a Honeycluster-wide problem — but open a support ticket either way so we can correlate.