You're right of course that Whois isn't involved in those things. Other comments indicate it's scheduled maintenance, which means EPP is down and most registrars have status updates out indicating changes to these TLDs are unavailable.
Curious how this will work in practise. The passkey has to be stored somewhere. Logically, that's in 1Password itself, which would mean you can _only_ login if you have access to a device that's already signed in. Or, in iCloud Keychain, which is what the video seems to show, which would shift the trust model to my Apple ID. What happens if I get locked out of that?
And what happens if biometrics are unavailable on my device (like, after first boot)? Does 1Password then fall back to my macOS login password?
Their blog post is unclear on details, but it feels like there are multiple trade-offs to this where some might want to stick to the current Master Password + Secret Key model.
If you're happy not having a home-grown open source solution, New Relic is essentially free if you don't have many servers and turn off extended metrics. If you start adding in more integrations, it's gonna cost you, but for basic monitoring and nice graphs hosted externally from your systems itself, it works nicely.
And with that computing power it's easy to install qemu-kvm and virtualise your own servers which is more scalable (and easier to move when the hardware you're renting becomes redundant) than having one or two monolithic servers with every conceivable piece of software installed, conflicting dependencies, etc.
The biggest additional cost to this is renting more IPv4 addresses, which Hetzner charge handsomely for now that there are so few available.