DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Question

why can't ping the host?

  • Posted August 30, 2013

hi, today I can’t ping my host 192.241.213.63, why? I try to reboot the droplet, after restart, Droplet History show

  1. Power Cycle
  2. Vnc Disable but the question is still, why ?
Subscribe
Share
Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

pablo • August 30, 2013

I was able to ping it, as well. Are you behind a firewall? Are you trying to ping from a Windows or *nix machine? What command did you execute?

andrejevicnemanja • August 30, 2013

I just pinged it. <br> <br>Pinging 192.241.213.63 with 32 bytes of data: <br>Reply from 192.241.213.63: bytes=32 time=197ms TTL=48 <br>Reply from 192.241.213.63: bytes=32 time=192ms TTL=48 <br>Reply from 192.241.213.63: bytes=32 time=196ms TTL=48 <br>Reply from 192.241.213.63: bytes=32 time=195ms TTL=48 <br> <br>Ping statistics for 192.241.213.63: <br> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), <br>Approximate round trip times in milli-seconds: <br> Minimum = 192ms, Maximum = 197ms, Average = 195ms

Alberto Rositani • August 30, 2013

192.241.213.63 is pingable. <br> <br>PING 192.241.213.63 (192.241.213.63): 56 data bytes <br>64 bytes from 192.241.213.63: icmp_seq=0 ttl=49 time=231.448 ms <br> <br>— 192.241.213.63 ping statistics — <br>1 packets transmitted, 1 packets received, 0.0% packet loss <br>round-trip min/avg/max/stddev = 231.448/231.448/231.448/0.000 ms