We have confirmed that the root cause of this issue stems from a service disruption
reported by our upstream database provider. The host machine running our database failed to recover from a scheduled maintenance event, and our provider was forced to rebuild the host from scratch. In doing so, the credentials of our database user were overwritten or corrupted, causing connection attempts to fail. We reset the user credentials as part of our troubleshooting efforts, restoring connectivity approx. 18 minutes after the initial connection failure.