The issue has been resolved. It was caused by a slowdown in our processing of subscription messages that caused api servers to become unresponsive.