Diagnostic Tools
Run ping and traceroute diagnostics for domains and IP addresses
Ping Results
PING vapeorder.in (23.227.38.72): 56 data bytes 64 bytes from 23.227.38.72: seq=0 ttl=50 time=4.658 ms 64 bytes from 23.227.38.72: seq=1 ttl=50 time=1.722 ms 64 bytes from 23.227.38.72: seq=2 ttl=50 time=1.682 ms 64 bytes from 23.227.38.72: seq=3 ttl=50 time=1.711 ms 64 bytes from 23.227.38.72: seq=4 ttl=50 time=1.716 ms --- vapeorder.in ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 1.682/2.297/4.658 ms
Traceroute Results
traceroute to vapeorder.in (23.227.38.72), 10 hops max, 46 byte packets 1 ip-10-0-0-119.ec2.internal (10.0.0.119) 1.252 ms 1.059 ms 1.751 ms 2 244.5.7.3 (244.5.7.3) 5.976 ms 244.5.0.133 (244.5.0.133) 6.296 ms 244.5.5.235 (244.5.5.235) 5.284 ms 3 240.6.88.32 (240.6.88.32) 2.899 ms 240.4.112.42 (240.4.112.42) 3.631 ms 240.6.88.35 (240.6.88.35) 3.108 ms 4 242.22.179.17 (242.22.179.17) 4.570 ms 242.12.42.3 (242.12.42.3) 3.400 ms 242.7.27.1 (242.7.27.1) 4.355 ms 5 240.3.180.79 (240.3.180.79) 4.917 ms 4.877 ms 240.3.180.77 (240.3.180.77) 5.171 ms 6 240.64.220.131 (240.64.220.131) 4.531 ms 240.64.220.128 (240.64.220.128) 4.260 ms 240.64.220.130 (240.64.220.130) 4.067 ms 7 52.46.166.112 (52.46.166.112) 4.508 ms 5.620 ms 4.820 ms 8 52.46.166.113 (52.46.166.113) 4.876 ms *
Cached results from: 6/20/2026, 8:26:22 AM
About Ping & Traceroute
Ping: Tests the reachability of a host (domain or IP address) on an Internet Protocol (IP) network and measures the round-trip time for messages sent from the originating host to a destination computer. Lower ping times (measured in milliseconds) indicate a faster, more responsive connection. High ping times or packet loss can indicate network congestion or problems with the connection or server.
Traceroute: Shows the path (or route) that data packets take from your computer to a destination server. It lists all the routers (hops) the packets pass through and the time it takes to reach each hop. Traceroute helps diagnose network bottlenecks, identify points of failure, and understand the network path to a specific host.