We experienced an Exchange outage this morning with our on-prem stand alone Exchange 2016 server. After investigating, this appears to be a resource issue. Here are some screenshots collected during the disruption. Main issue is that Outlook clients were temporarily unable to connect. Problem seemed to resolve itself after a few minutes, but many users impacted.
See this related article I posted a while back discussing how resources should be allocated and for a bit more info on our environment:
https://docs.microsoft.com/en-us/answers/questions/474373/exchange-2016-resources-and-constant-msexchangeaut.html
Screenshots collected during outage...

I did allocate an additional 4GB of RAM to this ESXi based Exchange server VM and this is what resources look like now. I used the hot add memory feature, so the server was never rebooted. Confirmed it recognizes the 24Gb RAM now where it had 20 before. I'm curious what would make the noderunner.exe processes go a bit nuts with CPU resources and now be totally quiet. There aren't any mailbox moves going on or anything like that. Wondering if the CPU may work harder when memory resources a stretched thin?
Prior to this outage it appears the "Resource-Exhaustion-Detect" warning log entry appeared on average about 5 times per day starting August 10th or so.
