Loading published probe observations…
01 / CURRENT PROBE WINDOW
Current Observation
Protocol probe counts from the public export. Count does not mean success, reachability or a unique destination.
Last observation/update: —
PUBLIC PROBE WINDOW
EXPORT BOUNDARY
TCP— units
OUTCOMENOT EXPORTED
ICMP— units
OUTCOMENOT EXPORTED
COUNTS OBSERVED
RESPONDERS · SUCCESS · ROUTE · RTT
UNKNOWN
02 / TCP COUNT CONTINUITY
History
Published history points
—TCP PROBE COUNT—
Each cell is one published history point. Solid cells contain a numeric TCP probe count; striped cells mark points without a numeric value.
Loading published history…
Open recent published observations
| Date | TCP count | Data status |
|---|
03 / EVIDENCE BOUNDARY
What the export can — and cannot — say
Published counts, simple numeric derivations and non-exported network details remain separate.
Observed
- Current published TCP probe count.
- Current published ICMP probe count.
- Published TCP count history and observation dates.
Derived
- Numeric history coverage is calculated from the public series.
- Distinct TCP count values are counted from numeric points.
- Consecutive TCP count changes are calculated from the public series.
Unknown
- Probe destinations, responders and per-probe success or failure.
- Route topology, providers, ASNs, RTT and packet loss.
- The cause, intent or broader meaning of any future change.
04 / PROVENANCE
Method & source boundary
This observer-specific view adds no external enrichment.
Methodology
The current view reads the published TCP probe count from layers.tcp.probe_count and the published ICMP probe count from the dashboard secondary metrics. One visual cell is drawn per exported count unit. The cells are presentation marks, not hosts, packets, replies or paths. History statistics are calculated only from the published TCP probe-count series.