167.148.203.166 Ping

Carrier
DNS

Nationwide Ping Latency Map

Nationwide Ping Latency Map
  • Timeout
  • >250ms
  • 201ms-250ms
  • 101ms-200ms
  • 51ms-100ms
  • <=50ms
100%
RegionFastestSlowestAverage
All Nodes广东广州1移动 14ms重庆江津移动 超时2144ms
China Telecom------
China Unicom------
China Mobile广东广州1移动 14ms重庆江津移动 超时2144ms
East China安徽池州移动 58ms安徽黄山移动 超时2554ms
South China广东广州1移动 14ms广东佛山移动 超时1814ms
Central China湖北恩施移动 69ms河南漯河移动 2946ms2575ms
North China山西太原移动 83ms北京移动 2945ms1902ms
Southwest贵州贵阳移动 33ms重庆江津移动 超时1492ms
Northwest新疆昌吉移动 118ms甘肃庆阳移动 2947ms2316ms
Northeast黑龙江鸡西移动 95ms辽宁鞍山移动 超时1744ms
HK/MO/TW------

DNS Resolution Stats

1

Showing: 76/76

NodeResponse IPIP LocationResponse Time网络质量
移动北京移动中国/香港/abuseradar.com/2945ms很慢
移动天津移动中国/香港/abuseradar.com/2943ms很慢
移动上海移动中国/香港/abuseradar.com/2936ms很慢
移动重庆江津移动中国/香港/abuseradar.com/Timeout超时
移动重庆沙坪坝移动中国/香港/abuseradar.com/2937ms很慢
移动重庆九龙坡移动中国/香港/abuseradar.com/2932ms很慢
移动河北石家庄移动中国/香港/abuseradar.com/86ms良好
移动河北唐山1移动中国/香港/abuseradar.com/2934ms很慢
移动河北唐山移动中国/香港/abuseradar.com/95ms良好
移动河南三门峡移动中国/香港/abuseradar.com/2944ms很慢
移动河南漯河移动中国/香港/abuseradar.com/2946ms很慢
移动河南驻马店移动中国/香港/abuseradar.com/2939ms很慢
移动河南信阳移动中国/香港/abuseradar.com/2942ms很慢
移动云南昆明移动中国/香港/abuseradar.com/41ms优秀
移动辽宁鞍山移动中国/香港/abuseradar.com/Timeout超时
移动辽宁大连移动中国/香港/abuseradar.com/2933ms很慢
移动辽宁盘锦移动中国/香港/abuseradar.com/1009ms很慢
移动黑龙江鸡西移动中国/香港/abuseradar.com/95ms良好
移动湖南永州移动中国/香港/abuseradar.com/2915ms很慢
移动湖南长沙移动中国/香港/abuseradar.com/2918ms很慢
移动湖南邵阳移动中国/香港/abuseradar.com/2929ms很慢
移动安徽池州移动中国/香港/abuseradar.com/58ms良好
移动安徽滁州移动中国/香港/abuseradar.com/2928ms很慢
移动安徽黄山移动中国/香港/abuseradar.com/Timeout超时
移动安徽合肥移动中国/香港/abuseradar.com/2937ms很慢
移动山东济南移动中国/香港/abuseradar.com/2954ms很慢
移动山东烟台移动中国/香港/abuseradar.com/156ms一般
移动山东聊城移动中国/香港/abuseradar.com/2946ms很慢
移动山东菏泽移动中国/香港/abuseradar.com/2942ms很慢
移动新疆昌吉移动中国/香港/abuseradar.com/118ms一般
移动新疆伊犁移动中国/香港/abuseradar.com/1035ms很慢
移动江苏徐州移动中国/香港/abuseradar.com/2945ms很慢
移动江苏苏州2移动中国/香港/abuseradar.com/2946ms很慢
移动江苏泰州移动中国/香港/abuseradar.com/Timeout超时
移动江苏盐城2移动中国/香港/abuseradar.com/2934ms很慢
移动江苏南通移动中国/香港/abuseradar.com/2936ms很慢
移动江苏苏州移动中国/香港/abuseradar.com/2942ms很慢
移动浙江宁波移动中国/香港/abuseradar.com/2934ms很慢
移动浙江金华移动中国/香港/abuseradar.com/2936ms很慢
移动浙江温州移动中国/香港/abuseradar.com/2933ms很慢
移动浙江杭州移动中国/香港/abuseradar.com/2936ms很慢
移动江西南昌移动中国/香港/abuseradar.com/Timeout超时
移动江西宜春移动中国/香港/abuseradar.com/2949ms很慢
移动湖北恩施移动中国/香港/abuseradar.com/69ms良好
移动广西贵港移动中国/香港/abuseradar.com/35ms优秀
移动广西南宁移动中国/香港/abuseradar.com/2923ms很慢
移动广西玉林移动中国/香港/abuseradar.com/35ms优秀
移动广西柳州移动中国/香港/abuseradar.com/2987ms很慢
移动甘肃庆阳移动中国/香港/abuseradar.com/2947ms很慢
移动山西太原移动中国/香港/abuseradar.com/83ms良好
移动山西晋中移动中国/香港/abuseradar.com/2932ms很慢
移动山西大同移动中国/香港/abuseradar.com/2937ms很慢
移动内蒙古巴彦淖尔移动中国/香港/abuseradar.com/97ms良好
移动内蒙古呼和浩特移动中国/香港/abuseradar.com/2939ms很慢
移动内蒙古包头移动中国/香港/abuseradar.com/2932ms很慢
移动陕西西安2移动中国/香港/abuseradar.com/2938ms很慢
移动陕西西安1移动中国/香港/abuseradar.com/2935ms很慢
移动陕西渭南移动中国/香港/abuseradar.com/2700ms很慢
移动吉林通化移动中国/香港/abuseradar.com/2940ms很慢
移动福建厦门2移动中国/香港/abuseradar.com/2923ms很慢
移动福建漳州移动中国/香港/abuseradar.com/2926ms很慢
移动福建厦门移动中国/香港/abuseradar.com/538ms很慢
移动贵州贵阳移动中国/香港/abuseradar.com/33ms优秀
移动贵州黔南移动中国/香港/abuseradar.com/42ms优秀
移动广东清远移动中国/香港/abuseradar.com/2673ms很慢
移动广东佛山移动中国/香港/abuseradar.com/Timeout超时
移动广东广州1移动中国/香港/abuseradar.com/14ms优秀
移动广东湛江移动中国/香港/abuseradar.com/2930ms很慢
移动广东广州移动中国/香港/abuseradar.com/2911ms很慢
移动西藏拉萨移动中国/香港/abuseradar.com/2932ms很慢
移动四川成都1移动中国/香港/abuseradar.com/57ms良好
移动四川成都2移动中国/香港/abuseradar.com/62ms良好
移动四川乐山移动中国/香港/abuseradar.com/2939ms很慢
移动四川广安移动中国/香港/abuseradar.com/2940ms很慢
移动宁夏银川移动中国/香港/abuseradar.com/2929ms很慢
移动宁夏中卫移动中国/香港/abuseradar.com/2922ms很慢

Ping Test Findings for 167.148.203.166

Tested
Oct 1, 2026, 2:23 AM
Completed probes
76/76
Valid Ping response probes
70 (92.1%)
Average round-trip time
2144 ms

This ICMP Ping test ran on 2026-09-30 against 167.148.203.166. Of 76 nodes, 70 returned a valid Ping response, giving a node-level response rate of 92.1%, with RTT at 2932 ms median, 2945 ms P90 and 2947 ms P95. The response rate and latenc

167.148.203.166 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 (%)

92.1%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.050100Mobile: 92.1%92.1%Mobile

P50 round-trip time

Round-trip time (ms)

2932 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.01.5k3kMobile: 2932 ms2932 msMobile
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

  • 6 of 76 nodes did not return a valid Ping response, so the node-level response rate was 92.1%, below the 98% warning threshold.
  • Median RTT was 2932 ms, above the 300 ms critical threshold; P90 was 2945 ms and P95 was 2947 ms, both above the 1000 ms critical threshold.
  • Only the mobile carrier had participating nodes: 76 nodes with 70 valid responses. telecom, unicom and overseas reported 0 nodes, so no carrier comparison is supported by this data.
  • All valid responses came from a single response IP, with no multi-address response distribution observed.

Improvement recommendations

  • The Ping response rate is 92.1%, 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.
  • P50 reached 2932 ms, above the 300 ms review threshold. Repeat the same probes at a different time and investigate the relevant network path only if the elevated median persists.
  • P95 reached 2947 ms, above the 1000 ms review threshold. Retest the slow probes and compare their routes or service stages before changing production configuration.

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