See the whole path
Connect API performance with network conditions. Follow a request beyond the application boundary.
Explore observabilityNetwork intelligence, everywhere
A clearer view of
every connection.
From the first API request to the last mile. Understand your network, find the better route, and keep your infrastructure moving.
14 connected regions. One complete picture.
GLOBAL FABRIC / LIVE SIMULATION
FRA · FrankfurtMedian latency18 ms
50.1109° N / 8.6821° E · SCHEMATICFRA / Frankfurt
128.0k req/s
IAD / Ashburn
151.0k req/s
SIN / Singapore
174.0k req/s
NRT / Tokyo
197.0k req/s
LOCAL SIMULATION / 14 REGIONS CONNECTED / NO LIVE SERVICE DATA
99.999%
Platform availability target
64
Edge locations · 14 regions
18 ms
Median API latency
2.64 Tbps
Provisioned network capacity
Illustrative architecture and metrics. API NetStats is a fictional company. 64 edge locations in this model.
One connected platform
Less noise.
More network intelligence.
Turn distributed signals into a shared understanding of how your infrastructure performs.
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
Find the signal sooner
Correlate latency, loss, and availability across regions. Know where a slowdown begins.
Understand the platformRoute with confidence
Compare measured paths and respond to sustained changes, with stability built into every decision.
Explore route intelligenceA global perspective
The world is connected.
Your insights should be, too.
64 edge locations across 14 regions. A common telemetry model that makes every route understandable, wherever your requests travel.
Explore the global networkBuilt for builders
Your network.
Now programmable.
Clear endpoints. Predictable responses. Put network intelligence into the tools and workflows your team already understands.
Open the API explorernetwork-status.jsonEXAMPLE RESPONSE
{
"status": "operational",
"healthy_regions": 14,
"median_latency_ms": 18,
"availability_target": 99.999,
"timestamp": "2026-09-15T12:00:00Z"
}Designed for clarity, from the first request.JSON