It’s always possible you hit one of the servers when something was updating itself. Or possibly something had failed and was restarting.
The outage yesterday was caused by an out of memory error. The DB engine runs on its own server and it handles summit, association, regioninfo and all the user logs. That’s all it does. Yesterday something as yet unidentified did something that meant all 3GB of memory was used. More was needed and there was no more. At this point the wheels came off the car and the DB engine said sayonara and stopped. No more DB engine = no summits info = no SOTAwatch. No DB engine means no viewing or adding QSO logs.
I was sat in the server room in the office trying to get a recalcitrant Ubuntu 16 computer to play nice and only when someone bugged me on Teams did I look at my laptop and notice we had a suboptimal SOTA service level Fixing that is more important than keeping a $45B corporation running so the Ubuntu machine had to wait. All I did was log into the DB server, view the log, see that it had exhausted the memory and restart the DB engine. Sometimes another component needs a kick when it has been unable to talk to the DB engine but everything was working as soon as the DB engine came online. Winner, winner, chicken dinner! The Ubuntu machine is still broken however.