We had an error this morning that impacted a subset of users. The result of this error was that payment orders could not be approved. This error was detected by our system and rolled back within 60 minutes of detection. You may notice duplicate audit record event from during the time of the incident. No payment orders were improperly processed as a result of this error.

The incident has been resolved.

The issue has been resolved by JPMC.

No change in status. JPMC is still experiencing delays for file transmissions and increased latency on the API for balances, transactions, and various payment initiation.

Modern Treasury will continue to monitor and provide updates as we receive them.

Host to host file transfers continue to be impacted (transactions & balances) along with API responses. Various payments are experiencing disruptions as well. Root cause is still unknown; JPMC is continuing to investigate.

Modern Treasury will continue to monitor and provide updates as we receive them.

The issue was caused by a disruption in a downstream provider, but this only affected our uptime check. No customer was impacted.

The Modern Treasury website has recovered.

This incident has been resolved.

We've identified the problem. Our canary tests are affected, but no customers are impacted.

The Modern Treasury API latency has recovered and all operations are normal.

This incident was caused by resource contention in our shared database cluster that started at around 0100 PT. Our on-calls were paged within minutes, and began investigating the issue.

Our API latencies began sporadically exceeding our internal SLOs at 0200 PT, and then were consistently above our SLOs at 0700 PT. Ultimately, the incident response team resolved the performance degradation through a combination of workload management and query optimizations. The API performance returned to SLO levels at around 0950 PT.

The Modern Treasury API latency has recovered. We are currently monitoring.