Live data from Hacker News

Hypergrowth isn’t always easy

tailscale.com

51–53 of 53 posts

Re: Hypergrowth isn’t always easy

#51
post #50

It makes me wonder why they do not allow you to have a failover that is in your own tailnet. Ex: let me use one of my servers as the control plane, if stuff goes down let that coordinate everything. Maybe its too close to self hosting for them to do it?

The server that acts as the control plane needs to have full access to the outside internet. You can’t do NAT hole-punching through STUN if you are yourself behind a NAT.

(There is Headscale though)

Re: Hypergrowth isn’t always easy

#52
post #44

Interesting post. I appreciate their candor and self-criticism, but, as a customer, I'm consistently surprised by how robust Tailscale ends up being, and how rarely I've experienced an issue that actually broke my tailnet. The sort of downtime that might keep me from accessing the admin tool or something else like that is rare enough, but my nodes have almost (?) never failed to talk to each other. Pretty great. Cave…

The reason for that is that all nodes talk p2p to each other. There is no central communication server like with many other vpn solutions. So even if Tailscale would go down for days you won't have any downtime between your nodes.

Re: Hypergrowth isn’t always easy

#53
post #35

Earlier quoted context omitted.

A network partition between the client and server is a network partition between two nodes in a distributed system, which is the P.

If there was a network partition, but it sounded like their service just went down.

it went down because of a network partition
Post reply on HN