Intermittent delay in API response for orders and JNLC

We are no longer observing any issues across our APIs. This incident is now marked as resolved. A root cause analysis will be published by tomorrow.

Error rates and latency are improving after remedial actions, we are continuously monitoring for any issue.

Our team is identified issues with one of the service being stale to refresh data and we are working on it.

Core databases and replication appear healthy; impact is limited to specific journal /account operations and is intermittent.
Engineering is actively working to stabilize the affected service and reduce latency; we will provide another update as we learn more.

Accounts are taking longer than expected to fully load, which is occasionally causing some users to see an error (a timeout) when they try to check their journals or orders. We are actively working to quickly finish loading these accounts and stabilize the system.

API response for orders and JNLC were delayed intermittently