3 out of the 4 sites you mentioned are affected by a recent incident with the tls-alpn-01 challenge, leading to a mass revocation. If your ACME account was registered with a valid and currently working email address, that email address would have given a notice for this.
See the following output of the testing application specially designed for help with the aformentioned mass revocation (https://tls-alpn-check.letsencrypt.org/checkhost):
[sportswil.no]: The certificate retrieved from your web server has serial 03f30ce65553eb216622e54fcfc1b409459a and was found in our affected data set. Please renew your certificate as soon as possible. Help is available at Questions about Renewing before TLS-ALPN-01 Revocations
[beeincity.no]: FQDN was not found in the impacted list.
[beeistro.no]: The certificate retrieved from your web server has serial 047af26addcc7016a81d343c1757aec7c5f4 and was found in our affected data set. Please renew your certificate as soon as possible. Help is available at Questions about Renewing before TLS-ALPN-01 Revocations
[goalsofheightandheart.no]: The certificate retrieved from your web server has serial 04d1bf976e9d467370443a93e1a28e50b5af and was found in our affected data set. Please renew your certificate as soon as possible. Help is available at Questions about Renewing before TLS-ALPN-01 Revocations
Strange thing is though: Certbot can't be affected by that incident, as it can't even use the tls-alpn-01 challenge. Have you used a different ACME client in the recent past?
Also, your site beeincity.no isn't affected.