Ping

pro

GET/v1/network/ping

Performs real ICMP ping (RFC 792) from up to 18 geographically distributed cloud regions via the Globalping network. Probes run from AWS, GCP, or Azure datacenters and return min/avg/max/median RTT, jitter (standard deviation), packet loss percentage, and per-packet timing data. Supports filtering by cloud provider, region, geography, or probe zone.

What It Does

Creates ICMP Echo Request measurements via the Globalping network, targeting probes in specific cloud provider regions (AWS, GCP, Azure). Returns actual ICMP round-trip times with comprehensive statistics: min/avg/max/median RTT, jitter (standard deviation across zones), aggregate packet loss percentage, resolved IP address, and probe network ASN. Supports filtering by cloud provider regions, probe zone IDs, or geographic region.

Why It's Useful

Get authentic ICMP latency data from real cloud provider regions — not HTTP overhead, but true network-level round-trip times per RFC 792 (ICMP) and RFC 4443 (ICMPv6). Essential for CDN optimization, multi-cloud performance comparison, SLA verification, geographic load balancing decisions, and ensuring consistent user experience across regions. Jitter and median metrics provide a more accurate picture than averages alone.

Use Cases

SRE / Platform Engineer

Global Performance Baseline

Measure service latency from all major geographic regions before a global launch. Establish baseline p50/p95 latency metrics per region and set alerting thresholds.

Identify regions with poor performance before users complain and set data-driven SLA targets.

Cloud Architect

Multi-Cloud Provider Comparison

Compare ICMP latency from AWS, GCP, and Azure regions to your service simultaneously. Evaluate network-level performance differences between cloud providers for the same geographic region.

Data-driven multi-cloud architecture and provider selection decisions backed by real latency data.

DevOps Engineer

CDN & Anycast Verification

Compare latency with and without CDN from various cloud provider regions. Verify anycast is routing users to the nearest edge. Detect CDN misconfigurations where certain regions hit distant origins.

Validate CDN effectiveness, identify geographic routing gaps, and optimize edge configuration.

NOC Engineer

SLA Monitoring & Incident Response

During an incident, quickly measure reachability and latency from 18 global vantage points to determine if an outage is regional or global. Compare against baseline metrics.

Rapidly scope the geographic impact of incidents and verify SLA compliance with evidence.

Parameters

Name	Type	Required	Description
`host`	string	Required	Target hostname or IP address to pingExample: `example.com`
`provider`	string	Optional	Cloud provider for region filtering: "aws", "gcp", or "azure". Defaults to "gcp".Example: `gcp`
`region`	string	Optional	Cloud provider region code. When combined with provider, pings from the nearest probe zone for that region.Example: `us-east-1`
`zones`	string	Optional	Comma-separated probe zone IDs (e.g., us-east,eu-west,ap-northeast). Use /ping/locations to see available zones.Example: `us-east,eu-west,ap-northeast`
`geography`	string	Optional	Filter by geography: North America, South America, Europe, Asia Pacific, Oceania, Middle East, AfricaExample: `Europe`

Response Fields

Field	Type	Description
`host`	string	The target host that was pinged
`measurement_type`	string	Measurement type: "icmp"
`results`	array	Per-zone ping results with ICMP stats, resolved IP, and probe network info
`results[].icmp_stats`	object	ICMP statistics: min, max, avg RTT (ms), packets_sent, packets_received, packet_loss
`results[].timings`	array	Per-packet timing data with TTL and RTT in milliseconds
`results[].resolved_address`	string	Resolved IP address of the target from this probe's perspective
`results[].probe_network`	string	Network name of the probe (e.g., "Amazon.com", "Google")
`results[].probe_asn`	number	ASN of the probe network
`zones_tested`	number	Number of probe zones tested
`successful`	number	Number of zones with successful pings
`failed`	number	Number of zones where ping failed
`avg_latency_ms`	number	Mean ICMP latency across all zones
`median_latency_ms`	number	Median (p50) ICMP latency across all zones — more robust than average
`jitter_ms`	number	Jitter (standard deviation) of latency across zones — measures consistency
`packet_loss_pct`	number	Aggregate packet loss percentage across all zones
`min_latency`	object	Zone with lowest latency (zone, city, latency_ms)
`max_latency`	object	Zone with highest latency (zone, city, latency_ms)
`available_zones`	object	Available probe zones grouped by geography
`available_providers`	object	Count of regions per cloud provider (aws, gcp, azure)

Code Examples

cURL

curl "https://api.edgedns.dev/v1/network/ping" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "host=example.com"

JavaScript

const response = await fetch(
  'https://api.edgedns.dev/v1/network/ping?host=example.com',
  {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  }
);

const data = await response.json();
console.log(data);

Python

import requests

response = requests.get(
    'https://api.edgedns.dev/v1/network/ping',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={
    'host': 'example.com'
    }
)

data = response.json()
print(data)

Read the full Ping guide

Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.

Read the guide →

Related Endpoints

Traceroute

Real ICMP traceroute from 18 global cloud regions

Response Time

Measure server response latency

External References

Learn more about the standards and protocols behind this endpoint.

IANA AS Numbers IEEE OUI Registry

Try This Endpoint

Test the Ping endpoint live in the playground.

Open in Playground Get API Key