Digital Ocean was down on the West Coast
digitaloceanstatus.com
digitaloceanstatus.com
For folks who complain that Digital Ocean is unreliable compared to other more-expensive providers, did you really expect $5-10/mo hosting to be reliable? It isn't supposed to be rock-solid reliable. It's cheap hosting for messing about with.
And it's not a matter of how much. It's a matter of how much for what you get, versus how much for what you get from elsewhere. A product that is significantly less expensive simply can't have the same level of hardware and technical support. This also shows in the SLA. Smaller, less expensive providers will credit you for lost time. Larger, more expensive providers will credit you for a % of your monthly bill per hour as a penalty for themselves.
Source: http://www.rackspace.com/managed_hosting/support/serviceleve...
Most technology is simply unreliable. Unless you pay a lot more for redundant systems. My internet provider here in NYC, Time Warner Cable, has had 3 outages in 3 weeks, two being a full day in my neighborhood. And that's on a $100/month 50 MB/s down and 5 MB/s up connection, the most expensive one they offer to the home. Unfortunately, like a lot of the US, Time Warner's infrastructure is horribly outdated, so these issues occur regularly. And, as with much of the US, we don't have any other options. Neither of the other cable providers service us. Verizon's FiOS rollout was abandoned. We can get DSL, but it's horribly slow (under 1MB/s up) and is notoriously reliable (when I tried it years back, it was down 8 days out of my 30 day trial period because a Verizon tech 'plugged something in wrong in our street's box'). So, I have to pay for a Verizon hotspot as a backup so I can 'reliably' work from home. Of course, the 1st of the 3 most recent outages Time Warner had, Verizon's LTE network went down at the same time.
So, yeah, that's the 'normal' of technology in the largest city in the United States.
-----------------
Peering Outage in SFO1 Sun Jul 21 19:15:00 2013
Upon further investigation is also appears nlayer might have a larger problem on the west coast. We have taken the circuit out of service and have a ticket opened with them to investigate. Sun Jul 21 19:50:34 2013
We saw some brief outages for one of our peers in SFO1.
While BGP converged on the backbones to reroute the inbound traffic from nlayer to our other peers, you might have experienced a short outage. This is standard bgp behavior and how the internet reroutes around outages.
Sun Jul 21 19:20:01 2013
--------------------
It's not clear to me whether this is telling me that there was an outage or that there is an outage. Regardless, my servers are inaccessible.
I have not been at all happy with the support I get from DO.
I think they only employ BOFHs (http://en.wikipedia.org/wiki/Bastard_Operator_From_Hell)
I know summer is all about Roller Coasters, hot dogs and whatnot but I did not expect to be riding a virtual roller coaster today!
There Debian image is not a standard image and I wanted to know what they had done so that I did not get caught by another 'difference' and they said that they did not have any documentation on what they had changed but I was free to change it to be however I wanted.
The problem with this is that if you use Vagrant or any other automated deployment anywhere else, you will either have to make changes to your build script to account for the changes they made or make your images to be like theirs are.
The entire process is rather busted - they should just use standard images or let me upload my own.
Their response was not at all feeling or understanding.
I have 1 $40 instance and will use it until all my credit is done but will not be returning.