Run diagnostics
POST/looking-glass/check
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 for limits and output handling.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- 429
- 500
- 502
- 503
- 504
Successful response
Missing or invalid key, mismatched ID, or inactive integration
Client IP is not in the integration allowlist (ip_not_allowed).
Unknown Looking Glass point.
Point or address family disabled.
Invalid request, forbidden target or DNS resolution failure.
Personal quota reached, point capacity unavailable, queue full or waiting time expired. Respect Retry-After.
Response Headers
Wait at least this many seconds before starting a new check.
60Unexpected server error
Looking Glass point unavailable or invalid result.
Looking Glass temporarily unavailable. lg_client_ip_unavailable means the client IP could not be determined.
Looking Glass response deadline exceeded.