# Whisper NIC: live operational dashboard for this node, ns1. > Each node reports its own counters; every number is read at serve time, never > typed by hand. A registry should show how the service is actually running, not just how big it is. The web page at is a live, dark dashboard: DNS queries per second and egress traffic over the window, the graph-vs-upstream decision split, query-type / response-code / transport breakdowns, P50/P99 latency, the busiest names, egress destinations and tenants, and side-by-side ns1 / ns2 cards with a combined roll-up. A **scope toggle** (Combined / ns1 / ns2) re-scopes the whole page; the charts auto-refresh roughly every 30 seconds. The page reads `GET /stats/data.json` from this same node and renders it client side (uPlot for the time-series, hand-rolled SVG for the donuts and bars). With JavaScript off — or while the data is still warming up after a reset — the page falls back to the plain-text counters below, and never shows a broken chart. Each node keeps its own numbers and reports only those, so they are always true to the box that answered. This document is the no-JavaScript mirror; the same counters are served identically from ns1 and ns2. ## Operational status (this node: ns1) - **DNS resolutions answered:** 19 - **Resolutions by type:** A 9, AAAA 4, DNSKEY 6 - **WHOIS queries served (port 43):** 0 - **RDAP queries served:** 1 - **Top resolvers (k-anonymised):** - **Zone serial:** 1783349648 - **Uptime:** 3m - **Answer-cache hit rate:** 0% Resolver figures count every answer this node has served. The top-resolver list publishes only masked, k-anonymised prefixes, never an individual client address. A blank line means that counter is not wired or is briefly unavailable on this node. ## The registry today - **28** agent identities (the RDAP index size) - **21** agents registered across accounts - **338** authoritative zone records served - **19** DNS answers served by this node Each agent identity is a single `/128` with reverse DNS, an RDAP record, and a WHOIS entry. Look any of them up from the how-to on the overview: . ## The ground it stands on - **AS219419** our autonomous system: IPv6-only, RPKI-signed, MANRS-compliant - **2a04:2a01::/32** the address block, one `/128` per agent The block sits within RIPE allocation `2a04:2a00::/31`, and every agent record refers up to RIPE's own record for `2a04:2a01::/32`. The chain from a single agent address to the regional registry is one anyone can walk. ## The map behind the answers - **7.43B** nodes in the live internet graph - **39.8B** relationships between them Before it connects, an agent can ask one keyless question from inside its own address: who really runs this host, and is it safe. The answer comes back from this map of the live internet, every identity answer DNSSEC-signed. Updated **2026-07-06 15:00 UTC**. Live figures carry a current timestamp; a last-known-good figure is labelled as of its snapshot, so a stale number is never paired with a minute-precise now. The published figures are licensed for reuse; see the data licence: . --- - **The complete record:** - **Policy:** - **Naming:** - **Reserved and premium names:** - **Data licence:** - **The home for your agents:** - **AS219419:** © viaGraph B.V. (dba Whisper Security)