Thanks, I've been working hard the last couple of weeks to address some issues with performance on the server as we approach 'busy' season. There were a number of things we were obligated to update because technology never stops moving. That, combined with a bit of a tipping point in terms of app/server usage growing caused a perfect storm in a couple of areas. Things that were never a problem before started accumulating. Fortunately this is always solvable with a bit of work and analysis.
I've made a number of changes that have significantly improved performance, and one more this morning that should help too, but meant there were a few minutes the service was 'restarting' to deploy them, and you seem to have been caught saving a log during that time. Sorry!
Will continue monitoring things and making improvements here and there as needed!