Question
NYC3 droplets having intermittent connectivity loss?
I created two droplets on NYC3. Both are CentOS 6.5 x86_64 and are still stock exactly as they are when the droplet is created. I have not upgraded any packages nor changed any configurations. I have not done anything to these droplets other than ping them or ssh into them and run top.
Both droplets have been experiencing several-minute periods of no ping response and are unresponsive. Support has so far not investigated this enough to confirm there is an issue. I should also note that I still have internet connectivity locally when these droplets start becoming unresponsive. I have also tried pinging them from different locations/service providers while they are down and have confirmed it’s nothing on my end.
Is anyone else experiencing a similar issue on NYC3? If so, please speak up because so far support thinks I’m just some idiot who is breaking my droplets with bad iptables configs. My droplets are currently STOCK for the sole purpose of attempting to prove this issue is not my doing - thus I’m essentially wasting time I could be spending deploying our company’s apps.
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.
×
Same problem, created a new droplet in NYC3 around an hour ago and still no internet access, doesn’t even reach the default gateways.
BTW did you configure it to have IPv6 and/or internal network as well?