Connection issues?

Same here. Experiencing it now and this is the really first time that I’m having a real issue on DO. What’s weird is that I have several VPS all in the same location (Singapore) but only my Rails VPS (created from 1-click app) is down. When I’m trying to ping it, it shows:

PING 188.166.X.X (188.166.X.X): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10

We are planning to use DO for some of our production apps and this issue is scaring the s**t out of me. Has anyone find a way to fix it and keep it that way?

I seem to have the same issue. My server seems to drop off the internet every 1-3 days. This causes e.g. all my IRC-connections to drop off simultaneously. My droplet resides in Amsterdam.

I have a related issue - i have submitted a ticket.

Is there any resolution to this problem ?

I see it was reported 2 years back and even now I am facing a similar problem without any anomaly at the server.

My server just stops to respond sporadically anytime in the day for 10 odd minutes which is very frustrating for my customers.

Could DO guys suggests a fool proof way to protect this from happening ?

Please suggest asap.

Thanks.

@holms: Please open up a support ticket with a traceroute to your droplet.

I have the same problem, for me it’s much worser. it timeous almost every 10 min. I’m on osx, so it’s just freezes. all i can do is close terminal window. This happends only in AMS datacenter… with ubuntu and debian and centos.

I have been running “ping 198.211.106.1” inside a detached “screen -R” for a while so I am pinging every second. I have not seen the problem since I started pinging. Of course there was also the maintenance. I just stopped the ping and will see how things do now. <br> <br>— 198.211.106.1 ping statistics — <br>1018863 packets transmitted, 1018078 received, +566 errors, 0% packet loss, time 1018926203ms <br>rtt min/avg/max/mdev = 0.217/1.488/5376.771/20.170 ms, pipe 6 <br>

The problem should have fixed during the emergency network maintenance (core routers have been updated). I will try to remove the ping command from crontab and see if this is really the case. <br> <br>Tyler, in case the problem still exists, then ping google.com every 5 minutes instead.

Hi, have this problem as well with one of my droplets. The droplet is running Arch and is located in ams1. Now and then it just gets unresponsive. Pinging the host makes it respond again. I’ve been in contact with support which suggested that i should make a snapshot of my droplet, and then re-create it => hopefully moving it to a new hypervisor. Haven’t tried that yet, but i will! :)

Dan, how often do you run the ping fix for this? I have a cron job set for every 5 minutes to ping the gateway of my droplet, but that doesn’t seem to make it any better. <br> <br>It’s very frustration having my website offline throughout the day.