Modern Treasury - Notice history

All systems operational

Platform/API - Operational

Ledgers API - Operational

Compliance API - Operational

Push to Warehouse - Operational

Marketing Website - Operational

Notice history

Jun 2023

Intermittent issue validating routing numbers during Payment Order creation
  • Resolved
    Resolved

    This incident has been resolved.

  • Investigating
    Investigating

    Some customers are experiencing valid routing numbers being marked as invalid. We are currently investigating this incident.

Resolved
  • Resolved
    Resolved

    This incident has been resolved.

Partner Issue: SVB
  • Resolved
    Resolved

    Modern Treasury determined that the errors were a result of a change made by SVB to their SSH connection configuration. For further details on this change, we recommend that customers reach out to their client service team at the bank. Modern Treasury has implemented a patch to account for the new configuration. We have confirmation from SVB that all files were processed correctly and on time. All payment flows are operating as normal.

  • Investigating
    Update

    We are continuing to investigate. We are still not able to successfully connect to bank servers.

  • Investigating
    Investigating

    We are currently investigating an issue with SVB. We are unable to connect to SVB servers to transmit payments.

May 2023

Partner Issue: Lob
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Update

    Error rates have dropped, and we are currently monitoring the result. Customers should be able to create check payment orders.

  • Monitoring
    Monitoring

    One of our partners is experiencing a problem. You can see more information https://lob.statuspage.io/ for updates.

    Customers are unable to create check payment orders.

Apr 2023

Error in Payment Order Approvals
  • Resolved
    Resolved

    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.

  • Investigating
    Investigating

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

An automated up-time check has failed.
  • Resolved
    Resolved

    The incident has been resolved.

  • Investigating
    Investigating

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

Partner Issue: JPMC file transmission delays and increased API latency
  • Resolved
    Resolved

    The issue has been resolved by JPMC.

  • Monitoring
    Update

    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.

  • Monitoring
    Monitoring

    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.

  • Identified
    Identified

    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.

Apr 2023 to Jun 2023

Next