Looking Glass
Diagnostic points, manual checks and browser HTTPS latency.
Integration guide
Network diagnostics and browser latency measurements
Looking Glass points
Diagnostic points from the current registry. Optional location_id filters the list; no matches return data=[]. Disabled points remain listed with disabled flags. The three latency URLs are called directly by the browser to measure HTTPS latency, without an API key. See [Looking Glass](./looking-glass-guide).
Run diagnostics
Synchronous Ping/Traceroute/MTR from the selected point to a public target. Client IP is derived from the connection; client_ip and api_id are not accepted in JSON. Quotas are independent per integration. Users behind a partner backend share its IP limit within that integration. A check may wait up to five seconds for capacity; the response remains synchronous. No automatic retries or Idempotency-Key: after disconnect or HTTP 504 the command may have executed. A nonzero exit code or timed_out=true can be returned with HTTP 200. See [Looking Glass](./looking-glass-guide) for limits and output handling.