Observe the edge
Synthetic probes and compact request aggregates produce a consistent stream of measurements.
The API NetStats platform
From raw signals to a clear decision.
Explore a unified approach to API monitoring, edge telemetry, and network route intelligence.
Connect the signals
A shared region, route, and time model puts latency and availability into context.
Explain the change
Compare baselines and identify whether a shift belongs to the API, a region, or a path.
Choose with evidence
Surface a stable alternative, share a diagnosis, or integrate the result into your own workflow.
Conceptual product architecture. This website does not collect telemetry or operate a live network.
01 / Global observability
Context travels
with every signal.
Regional medians can hide a difficult path. API NetStats connects the request, the edge location, and the selected route so operators can follow the same event across layers.
Separate response time from transport time. Compare p95 latency with packet loss. Keep units, sample windows, and regional identifiers visible.
Network overviewLIVE SIMULATION / 60 SECONDS
Global API latency
18.0 ms median
-60s-45s-30s-15sNOW
Blue: median ~18 ms / Violet: P95 ~32 ms14/14 healthy regions
02 / Routing intelligence
A faster path.
A stable decision.
A single slow probe should not reroute a network. The model compares rolling measurements and requires a sustained improvement before selecting an alternative.
Every selection includes its reason, measurement window, and previous path. Operators retain the context behind the change.
Inspect regional routes03 / API analytics
Performance you
can explain.
Read traffic rates alongside error ratios and percentile latency. Aggregates show the shape of a workload without requiring raw payloads in the analysis layer.
Read the telemetry exampleOne measurement vocabulary
Milliseconds for round trips, seconds for windows, and explicit UTC timestamps. No ambiguous chart axes.
Evidence before automation
Keep a human-readable selection reason alongside each routing decision, with enough context to reproduce it.
Useful at every scale
Start with a regional view. Move into individual paths when the aggregate signals a problem.