I am not happy with the current default hkps://hkps.pool.sks-keyservers.net especially for GpgOL and Gpg4win.
Too often there are servers in there that do not respond or a very slow.
It's incredibly bad user experience if users are guided in "first steps" instructions to search the key of their recpients e.g. by Kleopatra and then they don't find it.
(main) aheinecke@esus ~/d/m/s/gpgol> time gpg --homedir `mktemp -d` --keyserver hkps://hkps.pool.sks-keyservers.net --recv-key 94A5C9A03C2FE5CA3B095D8E1FDF723CF462B6B1 gpg: keybox '/tmp/tmp.az5DMTpbHW/pubring.kbx' created gpg: keyserver receive failed: No data gpg --homedir `mktemp -d` --keyserver hkps://hkps.pool.sks-keyservers.net 0.00s user 0.00s system 0% cpu 16.486 total
It is also the cause that I have just disabled "auto-key-retrieve" again in GpgOL again. Too often it just takes too long to fail (and we currently have no way to show contents before verification finishes).
I would propose to at least switch to the high availability keyserver pool, but I didn't see that it works with hkps.
Alternatively better quality control on the https pool.
Or as another alternative: Host a high quality keyserver through the GnuPG e.V. and use that as default.