Quorum, heartbeat of each Super Validator, and the response of their endpoints.
SV heartbeats and reporting gaps, based on on-chain status reports.
SVs reporting now
13 of 13(quorum 9)
Time with ≥ 9 SVs reporting
100%of the last 30 days
Periods below the quorum
Nonein the last 30 days
Lowest 11 of 13 reporting. DSO activity 100%.
None in the last 30 days: at least 11 of 13 SVs were reporting at every moment (the quorum is 9).
| Hosting | |||||
|---|---|---|---|---|---|
 C7 Technology Services Limited | Up#122,9612m 47s ago | 99.485% | 3h 43m | 4 |  AWS |
 Cumberland 1 | Up#122,9613m 22s ago | 99.991% | 4m | 0 |  AWS |
| Cumberland 2 | Up#122,9611m 34s ago | 99.968% | 14m | 1 | AWS |
 Digital Asset 1 | Up#122,9613m 50s ago | 99.986% | 6m | 0 |  Google Cloud |
| Digital Asset 2 | Up#122,9611m 53s ago | 99.971% | 12m | 1 | Google Cloud |
 Five North 1 | Up#122,9612m 45s ago | 99.992% | 3m | 0 |  Hetzner |
 Global Synchronizer Foundation | Up#122,9611m 56s ago | 98.783% | 8h 46m | 16 | AWS |
 Liberty City Ventures 1 | Degraded#122,9613m 10s ago | 99.963% | 16m | 1 | Google Cloud |
 MPC Holding Inc | Degraded#122,9613m 6s ago | 99.99% | none | 0 | Google Cloud |
 Orb 1 LP 1 | Degraded#122,9613m 27s ago | 99.991% | 4m | 0 | Google Cloud |
 Proof Group 1 | Up#122,9612m 29s ago | 99.442% | 4h 1m | 5 | CoreWeave |
 SV Nodeops Limited | Up#122,9613m 19s ago | 99.919% | 35m | 2 |  AWS |
 Tradeweb Markets 1 | Up#122,9612m 42s ago | 99.991% | 4m | 0 | AWS |
| Started, UTC | Super validator | Component | Duration | State |
|---|---|---|---|---|
| Nov 14, 10:14 | Liberty City Ventures 1 | Participant | 5m 30s | Resolved |
| Nov 12, 06:45 | Proof Group 1 | Participant | 25m | Resolved |
| Nov 12, 01:01 | SV Nodeops Limited | Participant | 18m | Resolved |
| Nov 10, 08:07 | SV Nodeops Limited | Participant | 9m 42s | Resolved |
| Nov 5, 22:49 | Proof Group 1 | Participant | 10m | Resolved |
| Nov 3, 10:21 | C7 Technology Services Limited | Participant | 24m | Resolved |
| Nov 3, 00:04 | Global Synchronizer Foundation | Participant | 28m | Resolved |
| Oct 30, 15:25 | Proof Group 1 | Participant | 2h 32m | Resolved |
| Oct 30, 11:35 | Global Synchronizer Foundation | Participant | 6m 11s | Resolved |
| Oct 28, 18:37 | C7 Technology Services Limited | Participant | 2h 10m | Resolved |
1. On-chain
Each SV writes a status report about every 140 s. It is accepted only after 9 of 13 SVs confirm it.
2. Our indexer
Reads every report since June 2024 through the Scan API, and the DSO’s member list.
3. Each SV
Up while its last accepted report is under 5 minutes old.
4. The network
Counted: time with at least 9 of 13 SVs reporting. Fewer is not proof of an outage.
Example: 5 SVs, quorum 4
Each report keeps its SV counted for 5 min. SV C and SV D go quiet; from minute 29 to 38 only three report, so that stretch is listed as a period below 4, with C and D as not reporting.
Heartbeat of an SV
Threshold
Time with ≥ 9 SVs reporting
Every accepted report proves the DSO confirmed it. Fewer reporting SVs does not prove the network stopped: an SV’s app can stop while its participant still confirms. The 5 minutes is our monitoring rule, not a Canton definition.
Probes do not count. A server of ours times each SV’s endpoints every 30 s; a failure there can be our route, so it is shown as diagnostics only.
GET/api/sv-health/raw
kindstringrequired
Which data: gaps, failures, incidents or probes
fromdate
First UTC day; default 7 days before to
todate
Last UTC day; default today; at most 31 days. For an exact window use since and until (ISO times) instead
svstring
One SV by name; default every SV
sourcestring
For incidents: ledger or probes; default both
servicestring
For failures and probes: one endpoint; default all
formatstring
json (default), csv, tsv or ndjson
curl '/api/sv-health/raw?kind=gaps&from=2026-10-16&to=2026-11-15'
{ "network": "testnet", "kind": "gaps", "from": "2026-10-16T00:00:00.000Z", "to": "2026-11-15T00:00:00.000Z", "truncated": false, "next": null, "rows": [ { "sv": "Digital-Asset-1", "last_report_at": "2026-10-20T08:01:12.000Z", "started_at": "2026-10-20T08:06:12.000Z", "ended_at": "2026-10-20T08:09:40.000Z", "next_report_at": "2026-10-20T08:09:40.000Z", "seconds": 208 }, "…" ] }
| sv | string | SV name |
| last_report_at | date-time | Its last accepted report before the gap |
| started_at | date-time | 5 minutes after that report |
| ended_at | date-time | null | Its next accepted report; null while the gap lasts |
| next_report_at | date-time | null | The same as ended_at |
| seconds | integer | Length of the gap |
