To clear up some of the conjecture, here is what happened:
The domain registration for puri.sm was indeed suspended because of a payment issue. We’re still investigating why the registration wasn’t paid automatically and addressing that for next time.
We paid the registration manually as soon as we discovered the issue, but unfortunately we were hit by San Marino’s office hours again being much ahead of our own. Services were not restored automatically upon making the payment, and we were not able to contact them until their office opened for business the next day.
(All credit to @JCS for staying up into the early morning to catch them when they opened 
)
Although we had previously moved from a third party registrar to a direct registration with TIM San Marino and were able to contact them directly, they are still not available 24x7.
Librem One services were affected because the name servers for librem.one were ns1.puri.sm through ns3.puri.sm. The Librem One registration was active, but its authoritative name servers were no longer resolvable. Caches may have kept this up for some, particularly because this was a problem resolving their name servers and not one affecting those domains themselves.
To address this, we are creating name server records in other domains, starting with ns1.librem.one, so no domain becomes a single point of failure for the others. We are also examining additional redundancy, such as alternative host names for some of our critical infrastructure.