After some extensive debugging, we've managed to get quick reply back on track.
As part of the fix, there was a short (approx. 10 min) of unexpected downtime.