Live activity at the relay
What you're watching is real encrypted traffic flowing through
relay.meshwhisper.org. Each pulse
is a blob the relay just routed. The relay can't read them — and neither can you.
Blobs, not messages
Each pulse is a single encrypted blob arriving, being forwarded, queued for an offline recipient, triggering a push wake, or draining from the queue when its recipient comes online. The relay knows what category to count it under — it does not know what's inside. Every device on the network also generates a constant stream of indistinguishable chaff packets, so the relay can't even tell real messages from background noise.
Counts only — no identity
The data feeding this visualisation is just five integers per ~250 ms window: received, forwarded, queued, woken, drained. No source IPs. No destination hashes. No per-event timing. The relay batches counts before emitting them so individual sends blur into the chaff stream — even an attacker watching this page in real time can't infer "Alice just sent something."
The data feeding this page
A public Server-Sent Events stream at relay.meshwhisper.org/events.
Try it from a terminal — every event you see here, you see there.
: connected
data: {"in":3,"fwd":2,"queue":1,"wake":0,"drain":0}
data: {"in":1,"fwd":1,"queue":0,"wake":0,"drain":0}
data: {"in":7,"fwd":5,"queue":2,"wake":1,"drain":0}
…