This incident has been resolved.

The issue was identified with one of the DB in the region which was under heavy load from the cluster. We did some changes and tuning to the application side to reduce the load. We will be continuing to monitor progress.

The previous change didn't help. We are continuing to investigate the issue.

We have implemented a change and monitoring results.

We are continuing to investigate this issue.

We are currently investigating the issue.
Currently, this is affecting a subset of customers in the region.