Well, the downtime just shows how no one is immune to downtime.

So keep that in mind when you customer is scolding you because their application is down for 5 minutes and they want their money back

Β· Β· Web Β· 1 Β· 4 Β· 14

And for some reason, people seems more forgiving when [BIG CORP] goes down compared to the [LOCAL HOSTING COMPANY] does.

@selea @arh Most likely the DNS registry deleted Facebook for indecency, which is allowed under 47 US Code 230 (Section 230). The entry was totally deleted, which is why their service went down.

The DNS providers can do that to any website or ISP under Section 230. There is no legal requirement to prove anything was indecent, which has no legal definition that I'm aware of.

Whoever controls the DNS controls the clearnet entirely.

@jh Their BGP was gone and considering Facebook runs their own nameserver (which now technically didn't exist on the clearnet anymore)...

The registries didn't delete them.

@jh @selea @arh

This seems scary until you realize that 13 people can literally shut down DNS because they have the secret private keys to the root servers that the Internet relies on.

It wouldn't shut down IP-based connections but it would definitely shut down anything that relied on DNS.

@oklomsy @jh @arh

Na, they cant shutdown DNS. They just carry the keys for the root zone, and not everyone of them have a real key either

And it needs to be done on location, so it is nothing they can do from home :)

@selea Oh yeah, forgot about that.

These people have to be together to be able to do it.

@selea, I don’t think Facebook’s customers were very chill about the downtime, which could have costed them millions.

Sign in to participate in the conversation

A instance dedicated - but not limited - to people with an interest in the GNU+Linux ecosystem and/or general tech. Sysadmins to enthusiasts, creators to movielovers - Welcome!