Public Aggregate Data

AeroNyx Network Stats

These metrics summarize aggregate AeroNyx privacy protocol activity. They are designed for public transparency and AI-search citation without exposing user traffic details.

Public Privacy Nodes
3

3 active regions

Encrypted Traffic
276.04 GB

296,397,115,828 total encrypted bytes forwarded

Encrypted Packets
256,875,559

Reported by 3 nodes

24h Availability
100.00%

864 valid heartbeat samples

Protocol Synchronization

Rust nodes are building a signed peer view

AeroNyx privacy nodes report only aggregate discovery state: healthy reporting nodes, verified peer counts, restart recovery evidence, and PeerStore lifecycle events. This proves the network is moving from static registration toward node-to-node discovery while preserving the blind-node invariant.

Protocol Status
healthy

3 healthy of 3 reporting nodes

Verified Peer View
3

3 foundation-ready nodes

Peer Lifecycle Events
192

72 accepted · 120 refreshed · 0 rejected

Restart Recovery
3 / 3

Latest gossip timestamp: 1,782,815,647

What These Metrics Mean

Encrypted traffic is the aggregate number of encrypted payload bytes forwarded by AeroNyx privacy protocol sessions. Encrypted packets count protocol-level forwarding events reported by online Rust nodes.

Node and region counts describe public privacy-node candidates that can participate in privacy routing. Availability is computed from signed heartbeat samples.

Peer lifecycle events summarize how Rust nodes accept, refresh, reject, and recover peer records in PeerStore. The public page intentionally publishes only aggregate buckets, not node identities, endpoints, routes, or user traffic.

Privacy Boundary

aggregate AeroNyx Privacy Protocol operations only; no node public keys, client public IPs, destinations, DNS contents, packet payloads, domains, URLs, browsing history, voucher secrets, or wallet-level traffic

Generated at 2026-06-30T10:34:12.717Z