api4.ipify.org Ping

Carrier
DNS

Nationwide Ping Latency Map

Nationwide Ping Latency Map
  • Timeout
  • >250ms
  • 201ms-250ms
  • 101ms-200ms
  • 51ms-100ms
  • <=50ms
100%
RegionFastestSlowestAverage
All Nodes河南开封联通 63ms北京联通 超时134ms
China Telecom------
China Unicom河南开封联通 63ms北京联通 超时134ms
China Mobile------
East China福建厦门联通 115ms上海数据中心联通 超时145ms
South China广西贵港联通 124ms广东揭阳联通 199ms181ms
Central China河南开封联通 63ms湖南邵阳联通 超时96ms
North China天津联通 76ms北京联通 超时163ms
Southwest贵州黔南联通 128ms重庆联通 超时148ms
Northwest宁夏银川联通 77ms陕西西安联通 超时134ms
Northeast吉林辽源联通 86ms辽宁沈阳联通 超时112ms
HK/MO/TW------

DNS Resolution Stats

3

Showing: 76/76

NodeResponse IPIP LocationResponse Time网络质量
联通北京联通美国/ Inc.//CloudflareTimeout超时
联通天津联通美国/ Inc.//Cloudflare76ms良好
联通上海联通美国/ Inc.//Cloudflare230ms较慢
联通上海数据中心--Timeout超时
联通重庆联通美国/ Inc.//CloudflareTimeout超时
联通河北邯郸联通美国/ Inc.//Cloudflare133ms一般
联通河北邢台联通美国/ Inc.//CloudflareTimeout超时
联通河北唐山联通美国/ Inc.//Cloudflare129ms一般
联通河南开封联通美国/ Inc.//Cloudflare63ms良好
联通河南洛阳联通美国/ Inc.//Cloudflare68ms良好
联通河南平顶山联通美国/ Inc.//Cloudflare65ms良好
联通河南漯河联通美国/ Inc.//Cloudflare68ms良好
联通河南商丘联通美国/ Inc.//Cloudflare168ms一般
联通河南驻马店联通美国/ Inc.//Cloudflare73ms良好
联通河南郑州联通美国/ Inc.//Cloudflare69ms良好
联通河南郑州1联通美国/ Inc.//Cloudflare69ms良好
联通云南曲靖联通美国/ Inc.//Cloudflare129ms一般
联通云南昆明联通美国/ Inc.//Cloudflare186ms一般
联通辽宁铁岭联通美国/ Inc.//Cloudflare140ms一般
联通辽宁沈阳联通美国/ Inc.//CloudflareTimeout超时
联通辽宁抚顺联通美国/ Inc.//Cloudflare136ms一般
联通辽宁鞍山联通美国/ Inc.//Cloudflare146ms一般
联通黑龙江鸡西联通美国/ Inc.//Cloudflare95ms良好
联通湖南岳阳联通美国/ Inc.//Cloudflare123ms一般
联通湖南永州联通美国/ Inc.//Cloudflare130ms一般
联通湖南邵阳1联通美国/ Inc.//Cloudflare123ms一般
联通湖南衡阳联通美国/ Inc.//Cloudflare127ms一般
联通湖南邵阳联通美国/ Inc.//CloudflareTimeout超时
联通安徽芜湖联通美国/ Inc.//CloudflareTimeout超时
联通安徽滁州联通美国/ Inc.//CloudflareTimeout超时
联通安徽马鞍山联通美国/ Inc.//Cloudflare205ms较慢
联通山东龙口联通美国/ Inc.//Cloudflare138ms一般
联通山东济宁联通美国/ Inc.//Cloudflare145ms一般
联通山东枣庄联通美国/ Inc.//CloudflareTimeout超时
联通山东青岛联通美国/ Inc.//CloudflareTimeout超时
联通山东菏泽联通美国/ Inc.//CloudflareTimeout超时
联通江苏苏州联通美国/ Inc.//CloudflareTimeout超时
联通江苏盐城联通美国/ Inc.//CloudflareTimeout超时
联通江苏徐州联通美国/ Inc.//CloudflareTimeout超时
联通江苏南京联通美国/ Inc.//Cloudflare119ms一般
联通浙江宁波联通美国/ Inc.//CloudflareTimeout超时
联通浙江杭州联通美国/ Inc.//CloudflareTimeout超时
联通浙江温州1联通美国/ Inc.//Cloudflare124ms一般
联通浙江温州联通美国/ Inc.//CloudflareTimeout超时
联通浙江杭州联通美国/ Inc.//Cloudflare120ms一般
联通江西南昌联通美国/ Inc.//CloudflareTimeout超时
联通湖北恩施联通美国/ Inc.//CloudflareTimeout超时
联通广西贵港联通美国/ Inc.//Cloudflare124ms一般
联通甘肃兰州联通美国/ Inc.//Cloudflare141ms一般
联通甘肃庆阳联通美国/ Inc.//Cloudflare141ms一般
联通甘肃平凉1联通美国/ Inc.//Cloudflare150ms一般
联通甘肃平凉联通美国/ Inc.//Cloudflare145ms一般
联通山西长治联通美国/ Inc.//Cloudflare132ms一般
联通山西晋中联通美国/ Inc.//Cloudflare133ms一般
联通山西运城联通美国/ Inc.//Cloudflare140ms一般
联通内蒙古包头联通美国/ Inc.//Cloudflare396ms较慢
联通内蒙古赤峰联通美国/ Inc.//CloudflareTimeout超时
联通陕西西安联通美国/ Inc.//CloudflareTimeout超时
联通陕西渭南联通美国/ Inc.//CloudflareTimeout超时
联通吉林辽源联通美国/ Inc.//Cloudflare86ms良好
联通吉林梅河口联通美国/ Inc.//Cloudflare92ms良好
联通吉林通化联通美国/ Inc.//Cloudflare86ms良好
联通福建厦门联通美国/ Inc.//Cloudflare115ms一般
联通福建宁德联通美国/ Inc.//Cloudflare124ms一般
联通福建福州联通美国/ Inc.//Cloudflare131ms一般
联通贵州贵阳联通美国/ Inc.//CloudflareTimeout超时
联通贵州黔南联通美国/ Inc.//Cloudflare128ms一般
联通广东清远联通美国/ Inc.//Cloudflare193ms一般
联通广东佛山联通美国/ Inc.//Cloudflare184ms一般
联通广东韶关联通美国/ Inc.//Cloudflare192ms一般
联通广东揭阳联通美国/ Inc.//Cloudflare199ms一般
联通广东湛江联通美国/ Inc.//Cloudflare191ms一般
联通青海西宁联通美国/ Inc.//Cloudflare133ms一般
联通青海西宁2联通美国/ Inc.//Cloudflare153ms一般
联通四川广安联通美国/ Inc.//CloudflareTimeout超时
联通宁夏银川联通美国/ Inc.//Cloudflare77ms良好

Ping Test Findings for api4.ipify.org

Tested
Sep 20, 2026, 7:13 PM
Completed probes
76/76
Valid Ping response probes
52 (68.4%)
Average round-trip time
134 ms

This ICMP Ping test ran on 2026-09-20 against api4.ipify.org. Of 76 nodes, 52 returned a valid Ping response, giving a 68.4% response rate, with RTT at 131 ms median, 192 ms P90 and 202 ms P95. A low response rate was detected and warrants

api4.ipify.org Ping performance by network

Valid Ping response rate counts probes that received an ICMP echo response. P50 is the round-trip time at or below which half of valid responses completed; it is not packet-level loss.

Valid Ping response rate

Valid Ping response rate (%)

68.4%Highest rate
Valid Ping response rateValid Ping response rate counts probes that received an ICMP echo response. P50 is the round-trip time at or below which half of valid responses completed; it is not packet-level loss.050100Unicom: 68.4%68.4%Unicom

P50 round-trip time

Round-trip time (ms)

131 msLowest P50
P50 round-trip timeValid Ping response rate counts probes that received an ICMP echo response. P50 is the round-trip time at or below which half of valid responses completed; it is not packet-level loss.075150Unicom: 131 ms131 msUnicom
Valid Ping response rate counts probes that received an ICMP echo response. P50 is the round-trip time at or below which half of valid responses completed; it is not packet-level loss.

Key findings

  • On the unicom carrier, 52 of 76 nodes returned a valid ICMP echo response, a node-level response rate of 68.4%, leaving 24 nodes without a valid result.
  • Unicom RTT percentiles were 131 ms median, 192 ms P90 and 202 ms P95, with a 134 ms average, indicating a fairly tight distribution.
  • The telecom, mobile and overseas groups each had 0 nodes, so no comparable response rate or RTT data was produced for them.
  • Responses came from 3 unique source IPs, and the node error count was 0, so unanswered nodes produced no error records.

Improvement recommendations

  • The Ping response rate is 68.4%, below the 98% review threshold. Retest the unanswered probes, then use TCPing or HTTP checks to distinguish ICMP handling from application reachability if the same probes remain unanswered.

These results describe this distributed test only and do not establish long-term availability, security, or a root cause.