Modern Treasury - Notice history

All systems operational

Platform/API - Operational

Ledgers API - Operational

Push to Warehouse - Operational

Marketing Website - Operational

Notice history

View current status

Apr 2023

Error in Payment Order Approvals
ResolvedPartial outage38 minutes
  • ResolvedUTC

    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.

  • InvestigatingUTC

    We are currently investigating an error where payment orders that need approval cannot be approved.

An automated up-time check has failed.
ResolvedMajor outage9 minutes
  • ResolvedUTC

    The incident has been resolved.

  • InvestigatingUTC

    The Modern Treasury application and API may be experiencing degraded performance. We are investigating.

Partner Issue: JPMC file transmission delays and increased API latency
ResolvedDegraded performance
  • ResolvedUTC

    The issue has been resolved by JPMC.

  • UpdateUTC

    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.

  • MonitoringUTC

    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.

  • IdentifiedUTC

    JPMC is experiencing delays for files transmissions and increased latency for API responses. JPMC is aware of the issue and is working on a resolution.

    Internal Accounts at JPMC may experience delays in balances, transactions, payment statuses.

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

Mar 2023

An automated up-time check has failed. (False positive)
Resolved38 minutes
  • ResolvedUTC

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

  • InvestigatingUTC

    The Modern Treasury application and API may be experiencing degraded performance. We are investigating.

An automated up-time check has failed. (False Positive)
Resolved8 minutes
  • ResolvedUTC

    The Modern Treasury website has recovered.

  • InvestigatingUTC

    The Modern Treasury website contact forms may be experiencing degraded performance. We are investigating.

An automated up-time check has failed. (False Positive)
Resolved29 minutes
  • ResolvedUTC

    This incident has been resolved.

  • IdentifiedUTC

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

  • InvestigatingUTC

    The Modern Treasury application and API may be experiencing degraded performance. We are investigating.

Partner Issue: Auth0
ResolvedDegraded performance53 minutes
  • ResolvedUTC

    The Modern Treasury web app login has recovered.

    For more details from Auth0 about this, see https://status.auth0.com/incidents/41gk3rcgm9vg

  • MonitoringUTC

    Logging into Modern Treasury's web app via OAuth will take longer than usual, and may require a few tries. The payments and ledgers APIs are not affected. Existing payments are not affected.
    More information and updates will be available at https://status.auth0.com

High API Latencies
ResolvedDegraded performance2 hours 45 minutes
  • ResolvedUTC

    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.

  • MonitoringUTC

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

  • InvestigatingUTC

    The Modern Treasury API may be experiencing degraded performance. We are investigating.

Feb 2023

An automated up-time check has failed. (False Positive)
Resolved7 minutes
  • ResolvedUTC

    We just resolved the issue!

  • InvestigatingUTC

    The Modern Treasury application and API may be experiencing degraded performance. We are investigating.

An automated up-time check has failed. (Plaid Server Errors)
Resolved2 hours 37 minutes
  • ResolvedUTC

    Plaid has resolved the issue

  • MonitoringUTC

    Plaid has implemented a fix and they are monitoring the issue.

  • IdentifiedUTC

    https://status.plaid.com/incidents/5hmjqm2h2nlp

    Plaid is experiencing API Errors. API calls against Modern Treasury using a Plaid integration will fail; everything else is operational.

Notice - Plaid Planned Maintenance
Resolved

  • https://status.plaid.com/incidents/kq147hcgkrgl

    Plaid is planning maintenance from 9:00pm to 1:00am PT from Tuesday, February 21st to February 22nd, 2023. During this time, API calls against Modern Treasury using a Plaid Integration may fail; everything else will continue to be operational.

    UTC
An automated up-time check has failed. (Plaid scheduled maintenance)
ResolvedPartial outage27 minutes
  • ResolvedUTC
  • IdentifiedUTC

    From 12:25 am PT to 12:38 am PT, Plaid was down for maintenance, causing API requests to Plaid to fail.

  • InvestigatingUTC

    Plaid API is down for maintenance.

Previous

Feb 2023 to Apr 2023

Next