4 ms·

This is very helpful information. Can you say if you've moved to a different provider or if you're now racking your own machines? And if you do have a new pro

This is very helpful information. Can you say if you've moved to a different provider or if you're now racking your own machines? And if you do have a new provider, can you say who you are and how you evaluated them? I have been doing some research in my (limited) spare time to try to find a new provider, but I still have not made the switch from Linode.

tptacek 11y ago
If you follow the link he posted, you'll see they switched away from Linode almost immediately after the July breach.
- deleted 11y ago
  [deleted]
- ethomson 11y ago
  Indeed I did read it - my question wasn't "did you move" but "to whom did you move".
Thalagyrt 11y ago
We use AWS us-west-1, us-west-2 and Azure Fresno. Azure replaced Linode very quickly after the July incident.
- jsmthrowaway 11y ago
  > Azure replaced Linode very quickly after the July incident. Bah. More virt. Throw down some cash on a cage and fire up AWS Direct Connect, man. It's bliss, you get more choices out here than I did with us-east-1, plus you guys can afford it now. We plopped in physical gear for a couple parts of our AWS infra a few employers ago and cut our Amazon opex by like, two thirds. Not helpful for your using Azure as a reliability strategy, but worth thinking about for your write-heavy databases, for example.
TheSwordsman 11y ago
So we ended on Microsoft Azure in Fresno. In hindsight, they would not be my preferred choice of a non-AWS provider to replace Linode. However, with the situation we were in they were the best choice. We operate all of our datacenters in a multi-master configuration across the WAN, so latency is something we need to be mindful of. We were also in the middle of an emergency situation that required a migration, so we needed a solution that would allow us to evacuate quickly. In the end we decided that we wanted a provider who supported a VPC-like network configuration, and was roughly within the same latency profile as Linode in respect to US-WEST-1 and US-WEST-2. If timing hadn't been a concern, we may have chosen differently. We felt we didn't have the luxury of time.

tptacek 11y ago

If you follow the link he posted, you'll see they switched away from Linode almost immediately after the July breach.

deleted 11y ago
[deleted]
ethomson 11y ago
Indeed I did read it - my question wasn't "did you move" but "to whom did you move".

Thalagyrt 11y ago

We use AWS us-west-1, us-west-2 and Azure Fresno. Azure replaced Linode very quickly after the July incident.

jsmthrowaway 11y ago
> Azure replaced Linode very quickly after the July incident. Bah. More virt. Throw down some cash on a cage and fire up AWS Direct Connect, man. It's bliss, you get more choices out here than I did with us-east-1, plus you guys can afford it now. We plopped in physical gear for a couple parts of our AWS infra a few employers ago and cut our Amazon opex by like, two thirds. Not helpful for your using Azure as a reliability strategy, but worth thinking about for your write-heavy databases, for example.

TheSwordsman 11y ago

So we ended on Microsoft Azure in Fresno. In hindsight, they would not be my preferred choice of a non-AWS provider to replace Linode. However, with the situation we were in they were the best choice. We operate all of our datacenters in a multi-master configuration across the WAN, so latency is something we need to be mindful of. We were also in the middle of an emergency situation that required a migration, so we needed a solution that would allow us to evacuate quickly. In the end we decided that we wanted a provider who supported a VPC-like network configuration, and was roughly within the same latency profile as Linode in respect to US-WEST-1 and US-WEST-2. If timing hadn't been a concern, we may have chosen differently. We felt we didn't have the luxury of time.