compare plc

mirror coverage and live event comparison

source on tangled. hosted on wisp.place <3

Coverage

15 min window  ·  lag = mirror recv − primary recv, same server clock  · 
host host Mirror being tracked by the server. ● green = connected, ● red = disconnected (will reconnect automatically). total events total events All operations received from this host since the server started, across all op types. Not windowed — resets on server restart. ops (15 min) ops (15 min) Operations received from this host in the rolling 15-minute window. Used as the numerator for coverage and missed calculations. coverage coverage Share of plc.directory's ops in the 15-min window that this mirror also delivered. 100% = no ops missed. Calculated as mirror ops ÷ primary ops. missed missed Ops seen by plc.directory in the 15-min window that this mirror has not delivered. May indicate the mirror is lagging, dropping events, or behind on propagation. lag p50 / p95 / p99 lag p50 / p95 / p99 How many milliseconds after plc.directory this mirror delivered each op, corrected for network distance. Correction = mirror OTT − primary OTT, where OTT = TCP RTT ÷ 2 (SYN/SYN-ACK, pure network latency). Positive = mirror is behind. Small negatives = within noise floor. coverage bar Visual ratio of received (green) vs missed (red) ops in the 15-min window.
connecting to server…
coverage history  ·  non-overlapping 5 min intervals now →

Live Compare

direct WebSocket connections from browser  ·  receive latency = now − event.createdAt
op types:
events / second
enable a host above to compare