Of 10 RPC-infrastructure networks in our catalog, 2 produce live telemetry we can serve with provenance right now. The remaining 8 are named in the refusal list below — that is what "no estimates, no zero-fill" looks like when it is enforced. RPC is the smallest live sector we cover: most RPC vendors treat their request volumes as the product they sell, so public supply-side telemetry is rare — the two that do publish (via their public status pages) are covered here.
11 verified telemetry rows ·
2 networks with live rows ·
5 distinct metrics ·
2 upstream sources
Last 24h: 11 fresh rows across
2 networks ·
11 rows from first-party / on-chain sources (non-aggregator)
Sorted by distinct live metrics. "non-agg rows" counts rows from the network's own API or chain (not market aggregators) — that is where supply-side truth lives.
| symbol | network | live metrics | total rows | non-agg rows | freshest as_of (UTC) | feed class |
|---|---|---|---|---|---|---|
| CHS | Chainstack | 3 | 9 | 9 | 2026-09-02 12:27:01 | status-page feed |
| QN | Quicknode | 2 | 2 | 2 | 2026-09-02 05:54:19 | status-page feed |
Revision activity is the count of new telemetry rows we recorded per network. For the RPC sector this tracks operational health publishing — incident counts, service component states — not node growth. A spike usually means an incident window; that is exactly what a monitoring customer subscribes to.
| network | name | rows, last 7d | rows, prior 7d | Δ activity |
|---|---|---|---|---|
| CHS | Chainstack | 9 | 0 | +100.0% |
| QN | Quicknode | 2 | 0 | +100.0% |
Sampled rows from non-aggregator sources (the providers' own status APIs), newest first. The verify link is the exact upstream endpoint the value came from — open it and the number should be in the same ballpark right now, that is the product.
| network | metric | value | source | as_of (UTC) | check at origin |
|---|---|---|---|---|---|
| CHS | active_incidents | 4 incidents | chainstack_status | 2026-09-02 12:27:01 | verify ↗ |
| QN | components_operational | 559 components | quicknode_statuspage | 2026-09-02 05:54:19 | verify ↗ |
Each bar is one hour of collector writes for this sector, straight from the ledger's own timestamps. A gap would mean the collectors were down; we would publish the gap, not paper over it.
| hour (UTC) | rows recorded |
|---|---|
| 2026-09-02 03:00:00 | 3 |
| 2026-09-02 05:00:00 | 2 |
| 2026-09-02 06:00:00 | 3 |
| 2026-09-02 12:00:00 | 3 |
These are named because that is the finding: a sector report that only lists winners is a brochure. For each network below, either the network publishes no public stats API, or every telemetry surface is key-gated (RPC infrastructure vendors sell access — their request volumes are exactly the product they charge for). Evidence for each refusal is logged in our coverage blockers register with a check date. We will not estimate, zero-fill, or back-fill them — a missing metric is absent, not zero.
| network | catalog symbol |
|---|---|
| Alchemy | ALCH |
| Blast Api | BLST |
| Bundlebear | BUND |
| Drpc | DRPC |
| Erpc | ERPC |
| Infura Depin | INFR |
| Nodies | NODS |
| Zeeve | ZEE |
Everything on this page is queryable per-network and per-metric via the API:
curl -s "https://kairossignal.com/v1/network/QN" | python3 -m json.tool | head -40 curl -s "https://kairossignal.com/v1/supply?network=QN,CHS" # filter the feed to these networks
Pricing — from $0.49 · Register an agent key (free credits granted per our fair-use policy, no card) · API docs · All networks