LogoIPCONFIG Docs

Ping Test

Learn how to test network connectivity and latency to any host from multiple global locations

Ping Test

IPConfig's Ping Test service allows you to test network connectivity and measure latency from multiple global locations to any host. This comprehensive tool helps diagnose network issues, optimize performance, and understand global connectivity patterns.

Overview

Our Ping Test service provides:

  • Global Network Testing - Test from 24+ locations worldwide
  • IPv4 and IPv6 Support - Test both protocol versions
  • Detailed Statistics - RTT, packet loss, and routing information
  • Visual Results - Interactive maps and charts
  • Export Options - CSV and email reports
  • Real-time Testing - Live ping results as they happen

Getting Started

Basic Ping Test

  1. Navigate to the Ping Test page
  2. Enter a hostname or IP address (e.g., google.com, 8.8.8.8)
  3. Select IP version (IPv4 or IPv6)
  4. Choose test locations or use "All" for comprehensive testing
  5. Click "Start Ping Test" to begin

The system automatically detects whether you entered a hostname or IP address and handles DNS resolution accordingly.

Test Locations

Our global network includes test nodes in:

  • China: Beijing, Shanghai, Guangzhou, Chengdu
  • Hong Kong - Special Administrative Region
  • Taiwan - Taipei region
  • Singapore - Southeast Asia hub
  • Japan - Tokyo
  • South Korea - Seoul
  • India - Mumbai
  • United States: California, Virginia, Dallas, Chicago, Seattle, Miami, Newark
  • Brazil - São Paulo
  • Germany - Frankfurt
  • United Kingdom - London
  • Qatar - Doha
  • South Africa - Johannesburg

Understanding Results

Each ping test provides detailed information:

Network Statistics

  • RTT (Round Trip Time) - Minimum, average, maximum, and standard deviation
  • Packet Loss - Percentage of lost packets
  • Packets Sent/Received - Total packet counts
  • Test Duration - Total time for the test

Target Information

  • Resolved IP Address - The actual IP being tested
  • Geographic Location - Where the target server is located
  • ISP Information - Internet Service Provider details
  • ASN - Autonomous System Number

Advanced Features

Custom Test Parameters

Ping Count

Choose how many ping packets to send:

  • 1 packet - Quick connectivity check
  • 2 packets - Standard test (default)
  • 3 packets - More reliable average
  • 4 packets - Comprehensive testing

IP Version Selection

  • IPv4 - Traditional internet protocol
  • IPv6 - Modern internet protocol
  • Auto - System determines best option

Location Selection

  • All Locations - Comprehensive global test
  • Regional - Test from specific regions
  • Custom - Select individual test nodes

Interactive Visualizations

World Map View

  • Global overview of all test results
  • Color-coded latency indicators
  • Clickable nodes for detailed information
  • Zoom and pan capabilities

Regional Maps

  • China Map - Detailed view of Chinese test nodes
  • USA Map - United States test locations
  • Focused views for better regional analysis

Results Table

  • Sortable columns by latency, location, or status
  • Filtering options by success/failure
  • Detailed statistics for each test node
  • Export functionality

API Usage

Basic Ping Request

Test connectivity programmatically using our API:

curl -X POST "https://ipconfig.com/api/ping" \
  -H "Content-Type: application/json" \
  -d '{
    "host": "google.com",
    "lang": "en",
    "ipVersion": "ipv4",
    "areas": ["all"],
    "count": 2
  }'

Request Parameters

ParameterTypeRequiredDescription
hoststringYesHostname or IP address to ping
langstringNoResponse language (en or zh)
ipVersionstringNoIP version (ipv4 or ipv6)
areasarrayNoTest locations (["all"] or specific areas)
countnumberNoPing count (1-4, default: 2)

Response Format

{
  "success": true,
  "data": {
    "result": true,
    "code": "PingSuccess",
    "message": "Ping Success",
    "pingHost": "google.com",
    "IPversion": "ipv4",
    "totalNodes": 24,
    "successNodes": 23,
    "failedNodes": 1,
    "pingResultDetail": [
      {
        "code": "PingSuccess",
        "message": "Ping Success.",
        "result": true,
        "pingServerArea": "Singapore",
        "pingServerAreaEN": "Singapore",
        "pingIPLocation": {
          "Address": "United States,California,Mountain View",
          "ISP": "Google LLC",
          "asn": "AS15169"
        },
        "pingResult": {
          "pingHost": "google.com",
          "pingIP": "142.250.191.14",
          "sendPackets": 2,
          "receivedPackets": 2,
          "lossPacket": 0,
          "rttMinTime": 1.234,
          "rttAvgTime": 1.456,
          "rttMaxTime": 1.678,
          "rttMdevTime": 0.222,
          "totalElapsedTime": 50,
          "pingStatisticsDetail": "PING google.com (142.250.191.14) 56(84) bytes of data..."
        }
      }
    ]
  },
  "meta": {
    "isLoggedIn": false,
    "remainingCount": 49,
    "dailyLimit": 50
  }
}

Common Use Cases

Network Troubleshooting

Connectivity Issues

  • Test if a server is reachable
  • Identify network outages
  • Diagnose routing problems
  • Verify DNS resolution

Performance Analysis

  • Measure latency from different locations
  • Identify slow network paths
  • Compare IPv4 vs IPv6 performance
  • Monitor network quality over time

Website and Service Monitoring

Global Performance

  • Test website accessibility worldwide
  • Identify regional performance issues
  • Monitor CDN effectiveness
  • Validate global infrastructure

Service Validation

  • Verify server deployments
  • Test load balancer configuration
  • Validate DNS propagation
  • Check service availability

Development and Testing

Infrastructure Testing

  • Validate new server deployments
  • Test network configuration changes
  • Verify firewall rules
  • Check routing policies

Performance Optimization

  • Choose optimal server locations
  • Evaluate CDN providers
  • Test different hosting providers
  • Optimize network architecture

Understanding Ping Results

RTT (Round Trip Time)

RTT measurements indicate network latency:

  • < 10ms - Excellent (local/nearby servers)
  • 10-50ms - Good (regional connections)
  • 50-100ms - Fair (cross-continental)
  • 100-200ms - Poor (distant/congested)
  • > 200ms - Very poor (satellite/heavily congested)

Packet Loss

Packet loss indicates network reliability:

  • 0% - Perfect (no packets lost)
  • < 1% - Excellent (minimal loss)
  • 1-5% - Good (acceptable for most uses)
  • 5-10% - Poor (noticeable impact)
  • > 10% - Very poor (significant problems)

Standard Deviation (Mdev)

Standard deviation indicates consistency:

  • Low mdev - Consistent latency
  • High mdev - Variable/jittery connection
  • Very high mdev - Unstable connection

Consistent low latency is often more important than absolute minimum latency for many applications.

Export and Sharing

CSV Export

Export detailed results for analysis:

  • All test data in spreadsheet format
  • Statistical summaries for each location
  • Timestamp information for historical tracking
  • Custom formatting options

Email Reports

Send results via email:

  • Formatted HTML reports with charts
  • PDF attachments for documentation
  • Scheduled reports for monitoring
  • Custom recipient lists

image

image

Share URLs

Generate shareable links:

  • Permanent URLs for specific tests
  • Embedded widgets for websites
  • Social media sharing with previews
  • API endpoints for integration

Rate Limits and Pricing

Free Tier Limits

Free Users: 50 ping tests per day per IP address Registered Users: 1000 credits upon registration

  • Each ping test consumes credits based on the number of test nodes
  • Typical test (24 nodes) = 24 credits
  • Failed nodes still consume credits to prevent abuse

Credit Consumption

Test ScopeNodesCredits Used
Single Location11 credit
Regional (Asia)88 credits
All Locations2424 credits
Custom SelectionVariable1 per node

Best Practices

Test Planning

  1. Start small - Test single locations first
  2. Use appropriate count - 2 packets for most tests
  3. Consider timing - Network conditions vary by time
  4. Test both protocols - IPv4 and IPv6 may differ

Result Interpretation

  1. Look at trends - Single tests may not be representative
  2. Consider geography - Distance affects latency
  3. Check multiple metrics - Don't focus only on average RTT
  4. Understand limitations - Ping doesn't test bandwidth

Troubleshooting

  1. Verify target - Ensure hostname/IP is correct
  2. Check connectivity - Test from your location first
  3. Consider firewalls - Some servers block ping
  4. Try different protocols - IPv4 vs IPv6 may differ

Troubleshooting Common Issues

No Response from Target

Possible Causes:

  • Server blocks ICMP packets
  • Firewall filtering
  • Network outage
  • Incorrect hostname/IP

Solutions:

  • Try different test locations
  • Verify the target is correct
  • Test with a known-good host
  • Check if target supports ping

High Latency

Possible Causes:

  • Geographic distance
  • Network congestion
  • Routing issues
  • Server overload

Solutions:

  • Test from closer locations
  • Try at different times
  • Compare with other targets
  • Check target server status

Packet Loss

Possible Causes:

  • Network congestion
  • Routing problems
  • Firewall interference
  • Server issues

Solutions:

  • Increase ping count for better statistics
  • Test from multiple locations
  • Try different times of day
  • Contact network administrator

Next Steps

After learning about Ping Testing:

Support

Need help with ping testing?

  • Check our FAQ section
  • Contact support for technical issues
  • Join our community for discussions
  • Report bugs or request features