ab//

// network

what is Per-detector network waterfall baseline?

For each {tool x proxyClass} egress, the per-detector request waterfall — dns/tcp/tls/ttfb/response milliseconds and the gate HTTP status — plus the timing sub-object (perf.now resolution, clock skew, server-observed RTT). This is the baseline the tls/ip layers compare a live trial against.. null phases are cross-origin-blocked (no Timing-Allow-Origin) — carried honestly, not zeroed. The datacenter egress (curl-impersonate) was gated 403 by both datadome and akamai; the residential egresses (nodriver, camoufox) passed 200. serverObservedRtt is 8.1ms on the direct 'none' egress versus ~90-96ms through residential proxies.

source capture as of 2026-06-14

in the benchmark

Per-detector network waterfall baseline is tracked as part of the network taxonomy. see how tracked tools score against it on the capability matrix.

related

where to go from here