Skip to main content
Use the Looking Glass API to add network diagnostics to support tools, reseller workflows and automation. All six regional endpoints are available on every one of the 50 EDIS Global Looking Glass nodes. No API key or VPS account credentials are required. Requests use HTTPS and return JSON. These endpoints perform network measurements; they do not order, restart or configure a VPS.

​
Choose where the test runs

A request to https://at.edisglobal.com runs from Vienna NDC2. Replace that hostname with one returned by the location directory to test from another region. For a single API hostname with a location selector, use the global hub at https://ping.edisglobal.com. Its routes and request format differ from the regional API.

​
Your first request

This sends one ICMP echo request from Austria. Read summary.received and status to determine whether a reply arrived; summary.averageMs is the round-trip time when available. A successful HTTP request can still report no_reply. For TCP connectivity to a particular service:

​
Regional endpoints

​
Rate limits at a glance

Clients sharing a public IPv4 address share these allowances; IPv6 addresses within one /64 also share an allowance. Regional limits apply separately on each node. Hub requests also consume the selected node’s allowance. Shared service capacity can cause HTTP 429 below these limits. Read rate limits and errors before integrating.

​
Request conventions

  • target is a public IPv4 address, public IPv6 address or public DNS hostname. Supply a bare address or hostname, without a URL scheme, path, port, IPv6 brackets or CIDR suffix.
  • family is the string "4", "6" or "auto". Auto prefers IPv4 when available. For /api/v1/probes, include family explicitly; quick ping, TCP and hub requests default to "auto".
  • Private, loopback, link-local and other reserved destinations are rejected. Hostnames with a mixture of public and non-public DNS answers are also rejected.
  • For POST, send Content-Type: application/json and a JSON object. Do not add undocumented fields. Diagnostic JSON bodies are limited to 1,024 bytes. For GET diagnostics, use query parameters without a request body; duplicate and unknown parameters are rejected.
  • Results are returned after the measurement finishes, not as a background job. Probe timeouts do not include all DNS, HTTP and network overhead.

​
Integrating into a reseller portal

Call the API from your backend, queue requests and share results between users where appropriate. Diagnostic endpoints restrict cross-site browser requests and do not provide a general cross-origin browser API. A backend’s public egress IP shares one client budget across the users it serves. Do not send VPS passwords, Order API credentials or Management API tokens. Use tests for systems you operate or are authorized to diagnose, in accordance with the acceptable use policy. For a manual multi-location test, open ping.edisglobal.com. Continue with result interpretation.
Last modified on October 28, 2026