Appearance
Network status
The live health of the KriptoNyx network and every public service is published on a status page, open to anyone, with no login.
| Status page | explorer.testnet.kriptonyx.com/status/ |
| Procedures | How KriptoNyx is monitored and patched |
The page refreshes every 30 seconds. It is produced by the same monitoring that runs the checks, so what it shows is the result of the most recent sweep, not a statement written by hand.
What the page shows
The headline gives the overall verdict:
| Verdict | Meaning |
|---|---|
| All systems operational | Every check is passing |
| Some checks are failing | At least one check is failing, but none has yet failed long enough to count as an outage |
| A service is down | At least one check has failed three times in a row |
| Starting up | The monitor has just started and has not completed a sweep |
Below it, 18 indicators in four groups:
| Group | Indicators |
|---|---|
| Chain | Node synced · Blocks being produced · Chain height advancing · Node peers |
| RPC | Public RPC · RPC serving chain 3009 · RPC up to date · RPC response time |
| Services | Explorer · Staking · DEX · ICO · Faucet · Bridge · API |
| Infrastructure | Host resources · Application processes · TLS certificates |
The footer shows when monitoring began, how many health checks have run, and how often they run.
What each state means
| State | Meaning |
|---|---|
| Operational | The check is passing |
| Degraded | The check is failing, but has not yet failed three times in a row. Often a transient blip that clears on the next check |
| Down | The check has failed three consecutive times. This is an outage, and it opens an incident |
| Unknown | The check could not reach a conclusion. This is never reported as an outage on its own |
Degraded is not an outage
A single failed request is noise. The page shows it as degraded so it is visible, but only three consecutive failures — three minutes — count as down. See failure detection.
Infrastructure lines are roll-ups
Each Infrastructure indicator covers several underlying checks and shows the worst state among them. Host resources, for example, covers disk, memory and load together.
This is deliberate. The page shows that the host is monitored and healthy without publishing what any resource actually reads, so it gives nothing away about the infrastructure behind it.
Incidents
Every outage is listed — ongoing and resolved — with when it started and how long it lasted. An incident opens when a check goes down and closes on the first healthy check afterwards.
The history is rebuilt from the monitoring log whenever the monitor starts, so a restart does not lose or duplicate an incident, and one that was open across a restart still closes correctly.
Machine-readable status
The data behind the page is available as JSON from the same place:
bash
curl -s https://explorer.testnet.kriptonyx.com/status/apijson
{
"verdict": "ok",
"checkedAt": "2026-09-19T09:26:26.653Z",
"checksPerSweep": 39,
"groups": [
{ "name": "Chain", "services": [
{ "label": "Node synced", "state": "operational" },
{ "label": "Blocks being produced", "state": "operational" }
] }
],
"history": {
"monitoringSince": "2026-09-18T20:29:17.581Z",
"sweeps": 781,
"intervalSeconds": 60,
"open": [],
"recent": []
}
}verdict is one of ok, degraded, down or starting; each indicator's state is one of operational, degraded, down or unknown. open lists incidents in progress and recent those recently resolved.
This is useful for an application that wants to warn its users — for example, showing a banner when Public RPC is not operational rather than letting transactions fail silently.
Treat it as informational
This endpoint exists to drive the status page. Read the fields you need defensively, poll no more often than the page itself — every 30 seconds — and do not build anything that fails if a new field appears.