Here’s the thing: you don’t necessarily need to use biometric data to store a passkey. That’s how the vast majority of current implementations do it, but it’s not required by the spec. Personally I store all my passkeys in Bitwarden, meaning I can lock them behind my master password with no bio data involved. It also means that my passkeys are platform non-specific and are stored on my own self-hosted Bitwarden instance instead of in some mega-corp’s cloud.

As for SSH vs passkeys, AFAIK they’re both based on the same encryption but SSH keys are just super low level (the raw key in what’s essentially a text file) vs. the more abstracted passkey system that, in theory, is more user-friendly.

I have the same problem with CloudFlare’s 1.1.1.1. Are the two services related? I also remember the same issue going on with archive.is

Looks like they’re federated again, as of the update 10 minutes ago.