Disconnect drills and long-term monitoring limits
Distinguish browser drills, client collection and server monitoring without overstating continuous protection.
Updated · Egress Observatory
Disconnect drills require manual action
After establishing a connected baseline, manually disconnect and restore the proxy. The site records samples; it does not change proxy settings, switch nodes or control operating-system traffic.
No successful requests during disconnection only describes those samples. It does not prove protection across every application, protocol or interval between samples.
Use a local collector after closing the page
Background throttling, sleep and closing the page interrupt reliable sampling. For longer records, run the command-line collector on the machine whose egress matters, with explicit intervals and retention limits.
A monitor deployed on a server sees that server egress. Changes in IP, ASN, country or DNS need sources and timestamps. An alert means a change was observed, not automatically that risk increased.