The good news is that lately there are only 2 or 3 problems we keep seeing. In the past the problem was always different, but we kept attacking them anyway. It paid off... the end is now in sight. Once we fix these last few problems the entire codebase will be updated to "current generation" code. (in the old days we didn't have DB clusters or memcache, and not all the code is converted to our modern programming guidelines.....)
Anyway, if you experienced that last little service outage, this is just to let you know we were aware of it, and it's a known problem we're already working on.