Observed endpoints
Endpoints actually recorded for this target in the selected window. A provider-managed target may rotate across more than one endpoint.
Loading…
Worker × target history
Target & node performance history
Follow one exact benchmark path through time: source worker → provider → protocol → target. See speed, retention, latency, loss, observed endpoint changes and QC outcomes without mixing source workers.
Exact target · historical drill-down
Source—one physical worker
Rankable samples—— total observations
Median retention——
Benchmark outcomes——
Historical performance
Select a target to load its timeline.
Loading…
QC & attempt health
QC describes measurement usability; scheduler outcomes describe whether each benchmark execution completed or degraded.
Loading…
Recent observations
Newest runs for the exact worker/target pair. This table includes both rankable and non-rankable QC states.
| UTC | Endpoint | Download | Retention | Latency | Loss | QC | Attempt result |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
How to read this: performance medians use only QC-rankable measurements. QC and scheduler counts intentionally include all recorded attempts so a slow/retesting target does not disappear from its own history.