5 ms·

Linode is great during stable periods but when there is an outage or DDOS they are completely absent. I was sick to death of waiting whilst my Fremont instances

Linode is great during stable periods but when there is an outage or DDOS they are completely absent. I was sick to death of waiting whilst my Fremont instances were down due to power issues and receiving no response from support tickets. And based on their security incidents Linode is absolutely in the hobby box category as well. At least Amazon is PCI DSS compliant.

hoop 14y ago
I don't know if this is still true, but when I started using Linode some years ago, Fremont was easily their worst datacenter. I've been in Newark without issue for some time now and I heard most of the other datacenters are pretty solid also. Regarding their support, I've submitted tickets at sometimes very odd hours and gotten responses back within minutes. What I really find amusing though is that you follow up your complaint of "completely absent during outage" with a reference to Amazon.
chc 14y ago
> And based on their security incidents Linode is absolutely in the hobby box category as well. Was that plural a typo or have there been more since the admin console phish that I missed?
ceejayoz 14y ago
> I was sick to death of waiting whilst my Fremont instances were down due to power issues and receiving no response from support tickets. Do you want their engineers bringing up the datacenter or answering up a bunch of e-mails with "we're working on bringing up the datacenter"?
- biot 14y ago
  For a company providing critical computing resources, during an incident there should be one person responsible for managing incident response. It actually shouldn't be an engineer; the person's job should be to bug engineers as little as possible but provide periodic updates in a central location (a site of the form https://status.example.com https://status.example.com) which is available to all customers.
- oasisbob 14y ago
  That's a false dichotomy. Communication and coordination are important parts of incident response. Key engineers shouldn't be doing either. If an org doesn't have dedicated people to communicate with their customers and triage support during an outage -- especially one where a facility loses power -- they're doing something wrong. When I was in a support role, I stayed up all night with the engineers during planned maintenance to answer questions, respond to tweets, &c. And if things went pear shaped, I'd already be up to speed.

hoop 14y ago

I don't know if this is still true, but when I started using Linode some years ago, Fremont was easily their worst datacenter. I've been in Newark without issue for some time now and I heard most of the other datacenters are pretty solid also. Regarding their support, I've submitted tickets at sometimes very odd hours and gotten responses back within minutes. What I really find amusing though is that you follow up your complaint of "completely absent during outage" with a reference to Amazon.

chc 14y ago

> And based on their security incidents Linode is absolutely in the hobby box category as well. Was that plural a typo or have there been more since the admin console phish that I missed?

ceejayoz 14y ago

> I was sick to death of waiting whilst my Fremont instances were down due to power issues and receiving no response from support tickets. Do you want their engineers bringing up the datacenter or answering up a bunch of e-mails with "we're working on bringing up the datacenter"?

biot 14y ago
For a company providing critical computing resources, during an incident there should be one person responsible for managing incident response. It actually shouldn't be an engineer; the person's job should be to bug engineers as little as possible but provide periodic updates in a central location (a site of the form https://status.example.com https://status.example.com) which is available to all customers.
oasisbob 14y ago
That's a false dichotomy. Communication and coordination are important parts of incident response. Key engineers shouldn't be doing either. If an org doesn't have dedicated people to communicate with their customers and triage support during an outage -- especially one where a facility loses power -- they're doing something wrong. When I was in a support role, I stayed up all night with the engineers during planned maintenance to answer questions, respond to tweets, &c. And if things went pear shaped, I'd already be up to speed.