3 ms·

I hate to say it but I recently moved away from Linode after their /64 block in Frankfurt was banned by all Google services. And even though all their kubernete

I hate to say it but I recently moved away from Linode after their /64 block in Frankfurt was banned by all Google services. And even though all their kubernetes nodes have a public ipv4 address they were somehow unable to fallback on this when their ipv6 didn't work. And when I suggested this to their support they acted like I was crazy and said there is no way to switch between ipv4 and ipv6. Well I don't work in networking but I do work for a major telco and I know our networking guys could have done that routing change, easy.

unilynx 5y ago
Are you referring to the geoip issue ? https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28769 https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28769 This was resolved and it didn’t appear something nefarious or any kind of ban was going on, so if you have some references I’d love to see them
- INTPenis 5y ago
  I never said it was "nefarious", I'm saying it was badly handled and it brought down all services in an entire location for days, with no fallback to ipv4, no status communication from Linode. It's not malice, it's just incompetence. Why the block was banned I have no idea and I don't really care, it can happen and they need to be able to handle it. I literally had a support case asking what happened, no response, eventually I had to say "look, I'm moving now because all services are down, please tell me what is going on", no answer, I had to move to get my services back up.
  - maccolgan 5y ago
    It seems to be a fault on Google's side, and not Linode's. It's like blaming the car when the road is closed down.
    - INTPenis 5y ago
      Yeah but again, no one is blaming anyone for the root cause here. Only for the handling.
benatkin 5y ago
Yep, confirmation from their staff here: https://www.linode.com/community/questions/22243/google-and-linode-server-issues https://www.linode.com/community/questions/22243/google-and-...
hughrr 5y ago
We blocked the entire of Linode AS63949 ranges because we were getting attacked from random owned nodes and it was tripping our IDS constantly. Just got fed up with it in the end and decided to hose them. To note, we have had problems with AWS blocking random addresses as well where we've had staff abroad.
- mattl 5y ago
  Same, but DO as well.
  - archon810 5y ago
    Same but also about a hundred others in my block list, except it's not enough because they keep on coming and new ones popping up all the time.
    - mattl 5y ago
      Would you mind sharing? Email address in profile
slenk 5y ago
I am trying to jump through hoops to move to hetzner as I can't get a clean /64 either.

unilynx 5y ago

Are you referring to the geoip issue ? https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28769 https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28769 This was resolved and it didn’t appear something nefarious or any kind of ban was going on, so if you have some references I’d love to see them

INTPenis 5y ago
I never said it was "nefarious", I'm saying it was badly handled and it brought down all services in an entire location for days, with no fallback to ipv4, no status communication from Linode. It's not malice, it's just incompetence. Why the block was banned I have no idea and I don't really care, it can happen and they need to be able to handle it. I literally had a support case asking what happened, no response, eventually I had to say "look, I'm moving now because all services are down, please tell me what is going on", no answer, I had to move to get my services back up.
- maccolgan 5y ago
  It seems to be a fault on Google's side, and not Linode's. It's like blaming the car when the road is closed down.
  - INTPenis 5y ago
    Yeah but again, no one is blaming anyone for the root cause here. Only for the handling.

benatkin 5y ago

Yep, confirmation from their staff here: https://www.linode.com/community/questions/22243/google-and-linode-server-issues https://www.linode.com/community/questions/22243/google-and-...

hughrr 5y ago

We blocked the entire of Linode AS63949 ranges because we were getting attacked from random owned nodes and it was tripping our IDS constantly. Just got fed up with it in the end and decided to hose them. To note, we have had problems with AWS blocking random addresses as well where we've had staff abroad.

mattl 5y ago
Same, but DO as well.
- archon810 5y ago
  Same but also about a hundred others in my block list, except it's not enough because they keep on coming and new ones popping up all the time.
  - mattl 5y ago
    Would you mind sharing? Email address in profile

slenk 5y ago

I am trying to jump through hoops to move to hetzner as I can't get a clean /64 either.