Yes, the issue with our Transaction Log server now appears to be cleared up. It's not clear what the actual problem was, other than the server getting bogged down with too much demand, as our Sysadmin couldn't find anything else amiss aside from server load.
Maybe too many people at the same time were running excessively-broad log searches with an enormous number of results to return. We recommend running log searches to be as narrow and specific as possible, to make the results return faster and avoid bogging down the server for others.
