Snapshot 45811
Normalized text
Scripts and page chrome removed; this is what change detection compares.
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Modern Treasury Status - Incident history</title>
<link>https://status.moderntreasury.com</link>
<description>Modern Treasury</description>
<pubDate>Mon, 12 Oct 2026 02:00:00 +0000</pubDate>
<item>
<title>Cell usw2-04 Database Maintenance</title>
<description>
Type: Maintenance
Affected Components: Ledgers API, Platform/API
Sep 24, 18:42:51 GMT+0 - Identified - We are planning a scheduled maintenance for cell usw2-04.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
]]>
</content:encoded>
<pubDate>Mon, 12 Oct 2026 02:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmufvqd8700gu1amh173r8fx1</link>
<guid>https://status.moderntreasury.com/maintenance/cmufvqd8700gu1amh173r8fx1</guid>
</item>
<item>
<title>Cell us005 Database Maintenance</title>
<description>
Type: Maintenance
Affected Components: Ledgers API, Platform/API
Oct 3, 18:22:38 GMT+0 - Identified - We are planning a scheduled maintenance for cell us005.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
]]>
</content:encoded>
<pubDate>Mon, 12 Oct 2026 00:30:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmuspz1mn02gj0wryiemg9fzx</link>
<guid>https://status.moderntreasury.com/maintenance/cmuspz1mn02gj0wryiemg9fzx</guid>
</item>
<item>
<title>Cell us001 Database Maintenance</title>
<description>
Type: Maintenance
Affected Components: Ledgers API, Platform/API
Oct 3, 18:21:44 GMT+0 - Identified - We are planning a scheduled maintenance for cell us001.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
]]>
</content:encoded>
<pubDate>Sun, 11 Oct 2026 23:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmuspxw7u02pl1nry05uzxswd</link>
<guid>https://status.moderntreasury.com/maintenance/cmuspxw7u02pl1nry05uzxswd</guid>
</item>
<item>
<title>Cell use2-03 Database Maintenance</title>
<description>
Type: Maintenance
Duration: 30 minutes
Affected Components: Ledgers API, Platform/API
Sep 23, 16:48:05 GMT+0 - Identified - We are planning a scheduled maintenance for cell use2-03.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Oct 5, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 5, 00:30:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>00:30:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Mon, 5 Oct 2026 00:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmuec6xeq00yn13qmbu8anh27</link>
<guid>https://status.moderntreasury.com/maintenance/cmuec6xeq00yn13qmbu8anh27</guid>
</item>
<item>
<title>Modern Treasury app: Outage</title>
<description>
Type: Incident
Duration: 3 hours and 4 minutes
Affected Components: Platform/API
Oct 2, 16:14:07 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 2, 18:51:28 GMT+0 - Resolved - This incident has been resolved. Oct 2, 15:47:46 GMT+0 - Investigating - We are investigating an outage for the Modern Treasury app. Customers may experience errors when attempting to access the Modern Treasury platform.
API traffic is unaffected.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 3 hours and 4 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>16:14:07</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>18:51:28</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>15:47:46</var> GMT+0</small><br><strong>Investigating</strong> -
We are investigating an outage for the Modern Treasury app. Customers may experience errors when attempting to access the Modern Treasury platform.
API traffic is unaffected..</p>
]]>
</content:encoded>
<pubDate>Fri, 2 Oct 2026 15:47:46 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmur501bb01xw1mlgikl5e3vu</link>
<guid>https://status.moderntreasury.com/incident/cmur501bb01xw1mlgikl5e3vu</guid>
</item>
<item>
<title>Sandbox Payments </title>
<description>
Type: Incident
Duration: 2 hours and 46 minutes
Affected Components: Platform/API
Sep 25, 16:11:09 GMT+0 - Identified - We identified an issue in the sandbox environment where payment orders become stuck in a processing state after an underlying processing failure. Production environments are unaffected. The team identified the cause and is working on a fix. Sep 25, 18:08:04 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 25, 18:57:28 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 2 hours and 46 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>16:11:09</var> GMT+0</small><br><strong>Identified</strong> -
We identified an issue in the sandbox environment where payment orders become stuck in a processing state after an underlying processing failure. Production environments are unaffected. The team identified the cause and is working on a fix..</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>18:08:04</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>18:57:28</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Fri, 25 Sep 2026 16:11:09 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmuh5r5l001670wlb5uhuf93b</link>
<guid>https://status.moderntreasury.com/incident/cmuh5r5l001670wlb5uhuf93b</guid>
</item>
<item>
<title>Cell us002 Database Maintenance</title>
<description>
Type: Maintenance
Duration: 30 minutes
Affected Components: Ledgers API, Platform/API
Sep 20, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 20, 01:30:00 GMT+0 - Completed - Maintenance has completed successfully Sep 13, 18:06:52 GMT+0 - Identified - We are planning a scheduled maintenance for cell us002.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
]]>
</content:encoded>
<pubDate>Sun, 20 Sep 2026 01:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmu04lqee02en1nl00uoyx964</link>
<guid>https://status.moderntreasury.com/maintenance/cmu04lqee02en1nl00uoyx964</guid>
</item>
<item>
<title>Partner Maintenance: Wells Fargo Wire Payments v1 API(s) in Production</title>
<description>
Type: Maintenance
Duration: 5 hours and 45 minutes
Affected Components: Slack, Payments: Partner Bank
Sep 11, 23:00:30 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Sep 12, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 12, 07:45:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 5 hours and 45 minutes</p>
<p><strong>Affected Components:</strong> , </p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>23:00:30</var> GMT+0</small><br><strong>Identified</strong> -
We are planning for a scheduled maintenance during that time..</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>07:45:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sat, 12 Sep 2026 02:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmtxk7mvs01fi0wnr5qydmi3c</link>
<guid>https://status.moderntreasury.com/maintenance/cmtxk7mvs01fi0wnr5qydmi3c</guid>
</item>
<item>
<title>Cell us000 Database Maintenance</title>
<description>
Type: Maintenance
Duration: 30 minutes
Affected Components: Ledgers API, Platform/API
Aug 31, 17:13:19 GMT+0 - Identified - We are planning a scheduled maintenance for cell us000.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Sep 9, 04:30:01 GMT+0 - Identified - Maintenance is now in progress Sep 9, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>04:30:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Wed, 9 Sep 2026 04:30:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmthhys4d0a5b13s2gmxmnvug</link>
<guid>https://status.moderntreasury.com/maintenance/cmthhys4d0a5b13s2gmxmnvug</guid>
</item>
<item>
<title>Partner Maintenance : Wells Fargo Instant Payments v1</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Payments: Partner Bank
Aug 26, 17:40:16 GMT+0 - Identified - Gateway maintenance is scheduled for the following API services.
| API | Instant Payments v1 |
| --- | ------------------- |
During maintenance, the services may experience intermittently unavailability. Sep 7, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 7, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>17:40:16</var> GMT+0</small><br><strong>Identified</strong> -
Gateway maintenance is scheduled for the following API services.
| API | Instant Payments v1 |
| --- | ------------------- |
During maintenance, the services may experience intermittently unavailability..</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Mon, 7 Sep 2026 04:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmtadq6iw052e0ll8pf2uja2w</link>
<guid>https://status.moderntreasury.com/maintenance/cmtadq6iw052e0ll8pf2uja2w</guid>
</item>
<item>
<title>Partner Maintenance: Comerica Bank RTP Network Suspension</title>
<description>
Type: Maintenance
Duration: 4 days and 6 hours
Affected Components: Payments: Partner Bank
Aug 28, 20:17:06 GMT+0 - Identified - Comerica Bank is temporarily suspending participation on the RTP (Instant Payments) network while it converts to Fifth Third Bank, from Thursday, September 3, 2026 at 9:00 PM ET through Tuesday, September 8, 2026 at 3:00 AM ET.
During this window, any RTP payment sent to the following Comerica routing numbers will be rejected: 121137522, 111000753, 067012099, 072000096.
This affects the receiving/counterparty side only; no Modern Treasury Internal Accounts are impacted. We recommend completing any time-sensitive RTP payments to these accounts before the window begins, or holding until normal processing resumes after September 8\. No action is required once the window closes; processing will resume automatically. Sep 4, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 8, 07:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 days and 6 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>20:17:06</var> GMT+0</small><br><strong>Identified</strong> -
Comerica Bank is temporarily suspending participation on the RTP (Instant Payments) network while it converts to Fifth Third Bank, from Thursday, September 3, 2026 at 9:00 PM ET through Tuesday, September 8, 2026 at 3:00 AM ET.
During this window, any RTP payment sent to the following Comerica routing numbers will be rejected: 121137522, 111000753, 067012099, 072000096.
This affects the receiving/counterparty side only; no Modern Treasury Internal Accounts are impacted. We recommend completing any time-sensitive RTP payments to these accounts before the window begins, or holding until normal processing resumes after September 8\. No action is required once the window closes; processing will resume automatically..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Fri, 4 Sep 2026 01:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmtde7ktf02kw0wming7xonoz</link>
<guid>https://status.moderntreasury.com/maintenance/cmtde7ktf02kw0wming7xonoz</guid>
</item>
<item>
<title>Database Maintenance</title>
<description>
Type: Maintenance
Duration: 15 minutes
Affected Components: Platform/API
Aug 10, 20:30:40 GMT+0 - Identified - No downtime expected Aug 16, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 16, 23:15:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 15 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>20:30:40</var> GMT+0</small><br><strong>Identified</strong> -
No downtime expected.</p>
<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>23:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>23:15:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 16 Aug 2026 23:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmsnorpbb01mh0rlcx3p6eezw</link>
<guid>https://status.moderntreasury.com/maintenance/cmsnorpbb01mh0rlcx3p6eezw</guid>
</item>
<item>
<title>Partner Maintenance : Wells Fargo OAuth2 API and Developer Portal My Apps page</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Payments: Partner Bank
Aug 6, 13:44:16 GMT+0 - Identified - Wells Fargo Gateway is performing maintenance for the OAuth 2 API for the production environment on Wednesday August 12 from 10:00 PM ET - 2:00 AM ET.
**OAuth 2:** Any API keys (bearer tokens) generated during this maintenance window may not work as expected and return a 401 error. Any API keys created before or after this maintenance window will work normally as long as they are still within 24 hours of when they were first generated.
**My Apps:** Please avoid creating new Apps or updating existing Apps during this maintenance window. Aug 13, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 13, 06:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>13:44:16</var> GMT+0</small><br><strong>Identified</strong> -
Wells Fargo Gateway is performing maintenance for the OAuth 2 API for the production environment on Wednesday August 12 from 10:00 PM ET - 2:00 AM ET.
**OAuth 2:** Any API keys (bearer tokens) generated during this maintenance window may not work as expected and return a 401 error. Any API keys created before or after this maintenance window will work normally as long as they are still within 24 hours of when they were first generated.
**My Apps:** Please avoid creating new Apps or updating existing Apps during this maintenance window..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Thu, 13 Aug 2026 02:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmshkhn9b00a60kpqvl9dghvd</link>
<guid>https://status.moderntreasury.com/maintenance/cmshkhn9b00a60kpqvl9dghvd</guid>
</item>
<item>
<title>Partner Maintenance : Wells Fargo OAuth2 API and Developer Portal My Apps page</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Payments: Partner Bank
Aug 6, 13:41:24 GMT+0 - Identified - Wells Fargo Gateway is performing maintenance for the OAuth 2 API for the sandbox environment on Monday August 10 from 2:00 PM ET - 6:00 PM ET.
**OAuth 2:** Any API keys (bearer tokens) generated during this maintenance window may not work as expected and return a 401 error. Any API keys created before or after this maintenance window will work normally as long as they are still within 24 hours of when they were first generated.
**My Apps:** Please avoid creating new Apps or updating existing Apps during this maintenance window. Aug 10, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 10, 22:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>13:41:24</var> GMT+0</small><br><strong>Identified</strong> -
Wells Fargo Gateway is performing maintenance for the OAuth 2 API for the sandbox environment on Monday August 10 from 2:00 PM ET - 6:00 PM ET.
**OAuth 2:** Any API keys (bearer tokens) generated during this maintenance window may not work as expected and return a 401 error. Any API keys created before or after this maintenance window will work normally as long as they are still within 24 hours of when they were first generated.
**My Apps:** Please avoid creating new Apps or updating existing Apps during this maintenance window..</p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Mon, 10 Aug 2026 18:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmshkdynu009m0kpqs5e2in00</link>
<guid>https://status.moderntreasury.com/maintenance/cmshkdynu009m0kpqs5e2in00</guid>
</item>
<item>
<title>Errors Approving Payment Orders</title>
<description>
Type: Incident
Duration: 12 hours and 42 minutes
Affected Components: Platform/API
Aug 3, 18:42:50 GMT+0 - Identified - We identified an issue affecting the Payment Order approval pages in the Modern Treasury dashboard. Beginning at approximately 2:00 PM ET on August 3, 2026, customers may see errors when approving a Payment Order, a blank Payment Order detail view, or an empty "pending my approval" list.
Payment origination and the processing of already-approved payments are not affected. Customers in all cells may be impacted. A fix is currently deploying, and we will provide an update shortly. Aug 3, 18:43:25 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 3, 18:43:53 GMT+0 - Resolved - This incident has been resolved. Aug 3, 18:44:44 GMT+0 - Identified - We are continuing to work on a fix for this incident. Aug 3, 18:55:32 GMT+0 - Resolved - This incident has been resolved as of 12PM PST.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 12 hours and 42 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>18:42:50</var> GMT+0</small><br><strong>Identified</strong> -
We identified an issue affecting the Payment Order approval pages in the Modern Treasury dashboard. Beginning at approximately 2:00 PM ET on August 3, 2026, customers may see errors when approving a Payment Order, a blank Payment Order detail view, or an empty "pending my approval" list.
Payment origination and the processing of already-approved payments are not affected. Customers in all cells may be impacted. A fix is currently deploying, and we will provide an update shortly..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>18:43:25</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>18:43:53</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>18:44:44</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>18:55:32</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved as of 12PM PST..</p>
]]>
</content:encoded>
<pubDate>Mon, 3 Aug 2026 18:42:50 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmsdku28j01ws0kmsf9xcxieg</link>
<guid>https://status.moderntreasury.com/incident/cmsdku28j01ws0kmsf9xcxieg</guid>
</item>
<item>
<title>Delays In Processing Incoming Transactions & Incoming Payment Details</title>
<description>
Type: Incident
Duration: 4 hours and 52 minutes
Affected Components: Platform/API
Jul 21, 18:45:07 GMT+0 - Investigating - We are currently investigating a delay in ingestion for certain bank integrations. Beginning at approximately 11:30 AM ET on July 21, 2026, customers may see a delay in information appearing in the dashboard and API. Outgoing payments and payment origination are not affected.
Customers in cells US001, USW2-04, US002, and US005 may be impacted. You can find your cell number on the [**settings**](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Jul 21, 19:03:33 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jul 21, 20:17:25 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 21, 23:37:23 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>19:03:33</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident..</p>
<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>20:17:25</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>23:37:23</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Tue, 21 Jul 2026 18:45:07 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmrv06xlo01o21bs6fafoht8d</link>
<guid>https://status.moderntreasury.com/incident/cmrv06xlo01o21bs6fafoht8d</guid>
</item>
<item>
<title>Partner Maintenance: BNY API</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Payments: Partner Bank
Jun 17, 15:39:19 GMT+0 - Identified - Bank of New York (BNY) API Endpoints will be unavailable on Sunday, June 28, 2026, between 2:00 AM ET - 6:00 AM ET while they perform system maintenance in their production environment.
During this timeframe, all BNY API connection requests will fail and will need to be re-attempted after the service has been restored. Jun 28, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 28, 10:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>15:39:19</var> GMT+0</small><br><strong>Identified</strong> -
Bank of New York (BNY) API Endpoints will be unavailable on Sunday, June 28, 2026, between 2:00 AM ET - 6:00 AM ET while they perform system maintenance in their production environment.
During this timeframe, all BNY API connection requests will fail and will need to be re-attempted after the service has been restored..</p>
<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 28 Jun 2026 06:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmqi8l0s300822jpftfqdq8ta</link>
<guid>https://status.moderntreasury.com/maintenance/cmqi8l0s300822jpftfqdq8ta</guid>
</item>
<item>
<title>Partner Maintenance: SVB API Banking: Instant Payments </title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Payments: Partner Bank
Jun 12, 00:41:20 GMT+0 - Identified - Please be aware that SVB’s Instant Payments API service will undergo enterprise maintenance activities on:
The Instant Payments API will be unavailable during this time. The listed timeframe is an estimate, and represents the longest expected interruption. Jun 21, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 21, 10:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>00:41:20</var> GMT+0</small><br><strong>Identified</strong> -
Please be aware that SVB’s Instant Payments API service will undergo enterprise maintenance activities on:
The Instant Payments API will be unavailable during this time. The listed timeframe is an estimate, and represents the longest expected interruption..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 21 Jun 2026 06:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmqa7axsd03h6p9qbuz928d6g</link>
<guid>https://status.moderntreasury.com/maintenance/cmqa7axsd03h6p9qbuz928d6g</guid>
</item>
<item>
<title>Elevated App Errors in Cell US000</title>
<description>
Type: Incident
Duration: 1 hour and 2 minutes
Affected Components: Platform/API
Jun 15, 19:07:37 GMT+0 - Investigating - Customers on cell us000 may be experiencing intermittent errors when accessing the application. Affected behavior may include the ability to search and view objects.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Jun 15, 20:02:05 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 15, 20:09:15 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>20:02:05</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>20:09:15</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Mon, 15 Jun 2026 19:07:37 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmqfl56wd0ar22jqj48igplvs</link>
<guid>https://status.moderntreasury.com/incident/cmqfl56wd0ar22jqj48igplvs</guid>
</item>
<item>
<title>Partner Maintenance: SVB API Banking: Instant Payments </title>
<description>
Type: Maintenance
Duration: 5 hours
Affected Components: Payments: Partner Bank
Jun 13, 07:30:00 GMT+0 - Completed - Maintenance has completed successfully Jun 12, 00:26:32 GMT+0 - Identified - Please be aware that SVB’s Instant Payments API service will undergo enterprise maintenance activities on:
The Instant Payments API will be unavailable during this time. The listed timeframe is an estimate, and represents the longest expected interruption. Jun 13, 02:30:01 GMT+0 - Identified - Maintenance is now in progress
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 5 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>07:30:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>00:26:32</var> GMT+0</small><br><strong>Identified</strong> -
Please be aware that SVB’s Instant Payments API service will undergo enterprise maintenance activities on:
The Instant Payments API will be unavailable during this time. The listed timeframe is an estimate, and represents the longest expected interruption..</p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>02:30:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
]]>
</content:encoded>
<pubDate>Sat, 13 Jun 2026 02:30:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmqa6rx0p03c6qrdgn1nyqaoj</link>
<guid>https://status.moderntreasury.com/maintenance/cmqa6rx0p03c6qrdgn1nyqaoj</guid>
</item>
<item>
<title>Partner Maintenance: Wells Fargo Wire Payments v1 API(s) in Production</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: Payments: Partner Bank
Jun 7, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 7, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Jun 7, 06:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> -
We are planning for a scheduled maintenance during that time..</p>
]]>
</content:encoded>
<pubDate>Sun, 7 Jun 2026 06:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmpy9l76y02njqulja89d4qne</link>
<guid>https://status.moderntreasury.com/maintenance/cmpy9l76y02njqulja89d4qne</guid>
</item>
<item>
<title>Database Maintenance</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: Ledgers API, Platform/API
Jun 7, 06:00:00 GMT+0 - Identified - Modern Treasury will perform database maintenance in all cells on Jun 6 at 11PM PT. Jun 7, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 7, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> , </p>
<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Modern Treasury will perform database maintenance in all cells on Jun 6 at 11PM PT..</p>
<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 7 Jun 2026 06:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmppuniv500hip8qhenttydf8</link>
<guid>https://status.moderntreasury.com/maintenance/cmppuniv500hip8qhenttydf8</guid>
</item>
<item>
<title>Investigating Intermittent Authentication Errors</title>
<description>
Type: Incident
Duration: 54 minutes
Affected Components: Platform/API
Jun 2, 21:49:25 GMT+0 - Investigating - We are investigating reports of intermittent authentication errors affecting API requests and Dashboard access. Some customers may be experiencing 401 responses when attempting to authenticate.
Our engineering team is actively investigating the issue. We will provide an update as soon as we have more information. Jun 2, 22:13:46 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 2, 22:28:02 GMT+0 - Monitoring - We have rolled back to a stable deploy and authentication errors should be resolved. We are continuing to monitor the situation. Jun 2, 22:43:44 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 54 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>21:49:25</var> GMT+0</small><br><strong>Investigating</strong> -
We are investigating reports of intermittent authentication errors affecting API requests and Dashboard access. Some customers may be experiencing 401 responses when attempting to authenticate.
Our engineering team is actively investigating the issue. We will provide an update as soon as we have more information..</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>22:13:46</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident..</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>22:28:02</var> GMT+0</small><br><strong>Monitoring</strong> -
We have rolled back to a stable deploy and authentication errors should be resolved. We are continuing to monitor the situation..</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>22:43:44</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Tue, 2 Jun 2026 21:49:25 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmpx677aa00nknwp90mwndw7u</link>
<guid>https://status.moderntreasury.com/incident/cmpx677aa00nknwp90mwndw7u</guid>
</item>
<item>
<title>Database Maintenance</title>
<description>
Type: Maintenance
Duration: 2 hours
Affected Components: Platform/API, Ledgers API
May 24, 06:00:00 GMT+0 - Identified - Modern Treasury will perform database maintenance on May 23 at 11PM PT. May 24, 06:00:01 GMT+0 - Identified - Maintenance is now in progress May 24, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 2 hours</p>
<p><strong>Affected Components:</strong> , </p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Modern Treasury will perform database maintenance on May 23 at 11PM PT..</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 24 May 2026 06:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmp7cqn300lblnpmde1lrsvb7</link>
<guid>https://status.moderntreasury.com/maintenance/cmp7cqn300lblnpmde1lrsvb7</guid>
</item>
<item>
<title>Payment Orders: Approval Options </title>
<description>
Type: Incident
Duration: 2 hours and 1 minute
Affected Components: Platform/API
May 21, 17:24:17 GMT+0 - Investigating - Some clients on cell us001 may be unable to see or apply approval options on Payment Orders in the Modern Treasury UI. Our team is actively investigating and will provide updates as we learn more.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app. May 21, 17:53:36 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 21, 18:14:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 21, 19:24:48 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>17:53:36</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident. .</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>18:14:00</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>19:24:48</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Thu, 21 May 2026 17:24:17 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmpfrg0hk01y9nirpv3ncfq59</link>
<guid>https://status.moderntreasury.com/incident/cmpfrg0hk01y9nirpv3ncfq59</guid>
</item>
<item>
<title>Database Maintenance</title>
<description>
Type: Maintenance
Duration: 20 minutes
Affected Components: Platform/API, Ledgers API
May 10, 02:45:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The UI will be down. May 10, 02:45:01 GMT+0 - Identified - Maintenance is now in progress May 10, 03:05:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 20 minutes</p>
<p><strong>Affected Components:</strong> , </p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>02:45:00</var> GMT+0</small><br><strong>Identified</strong> -
We are planning for a scheduled maintenance during that time. The UI will be down..</p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>02:45:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>03:05:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 10 May 2026 02:45:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmoomspq003fwoxy6ovhpnkbm</link>
<guid>https://status.moderntreasury.com/maintenance/cmoomspq003fwoxy6ovhpnkbm</guid>
</item>
<item>
<title>Partner Maintenance: SVB Upcoming API and RTP Maintenance</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Slack, Payments: Partner Bank
Apr 26, 05:00:00 GMT+0 - Identified - Silicon Valley Bank has announced scheduled maintenance that may impact Real-Time Payments (RTP) and API services.
During the maintenance windows below, customers may experience intermittent disruptions or temporary unavailability when sending RTP payments or interacting with SVB-related API endpoints.
If workflows rely on RTP or SVB APIs during these times, we recommend planning processing activity outside of the maintenance windows where possible. Apr 26, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 26, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> , </p>
<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Silicon Valley Bank has announced scheduled maintenance that may impact Real-Time Payments (RTP) and API services.
During the maintenance windows below, customers may experience intermittent disruptions or temporary unavailability when sending RTP payments or interacting with SVB-related API endpoints.
If workflows rely on RTP or SVB APIs during these times, we recommend planning processing activity outside of the maintenance windows where possible..</p>
<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>05:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 26</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 26 Apr 2026 05:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmntdlhz201cwfd3d9s42kuen</link>
<guid>https://status.moderntreasury.com/maintenance/cmntdlhz201cwfd3d9s42kuen</guid>
</item>
<item>
<title>Partner Maintenance: SVB Upcoming API and RTP Maintenance</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Slack, Payments: Partner Bank
Apr 20, 05:00:00 GMT+0 - Identified - Silicon Valley Bank has announced scheduled maintenance that may impact Real-Time Payments (RTP) and API services.
During the maintenance windows below, customers may experience intermittent disruptions or temporary unavailability when sending RTP payments or interacting with SVB-related API endpoints.
If workflows rely on RTP or SVB APIs during these times, we recommend planning processing activity outside of the maintenance windows where possible. Apr 20, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 20, 09:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> , </p>
<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Silicon Valley Bank has announced scheduled maintenance that may impact Real-Time Payments (RTP) and API services.
During the maintenance windows below, customers may experience intermittent disruptions or temporary unavailability when sending RTP payments or interacting with SVB-related API endpoints.
If workflows rely on RTP or SVB APIs during these times, we recommend planning processing activity outside of the maintenance windows where possible..</p>
<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>05:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Mon, 20 Apr 2026 05:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmntdj54v01mkkkq2v5c993ro</link>
<guid>https://status.moderntreasury.com/maintenance/cmntdj54v01mkkkq2v5c993ro</guid>
</item>
<item>
<title>Partner Maintenance: Wells Fargo Instant Payments v1 API(s) in Production</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Platform/API
Apr 19, 06:00:00 GMT+0 - Identified - Wells Fargo Gateway is performing maintenance for the following API(s): Instant Payments v1\. Sending payments via Wells Fargo may experience intermittent interruptions during this time. Apr 19, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 19, 10:00:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Wells Fargo Gateway is performing maintenance for the following API(s): Instant Payments v1\. Sending payments via Wells Fargo may experience intermittent interruptions during this time..</p>
<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 19 Apr 2026 06:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmnrojk2r01nma4gkmb0bffs9</link>
<guid>https://status.moderntreasury.com/maintenance/cmnrojk2r01nma4gkmb0bffs9</guid>
</item>
<item>
<title>Partner Maintenance: Wells Fargo Instant Payments v1 API(s) in Production</title>
<description>
Type: Maintenance
Duration: 4 hours
Affected Components: Platform/API
Apr 12, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 12, 13:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 12, 09:00:00 GMT+0 - Identified - Wells Fargo Gateway is performing maintenance for the following API(s): Instant Payments v1\. Sending payments via Wells Fargo may experience intermittent interruptions during this time.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 4 hours</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
Wells Fargo Gateway is performing maintenance for the following API(s): Instant Payments v1\. Sending payments via Wells Fargo may experience intermittent interruptions during this time..</p>
]]>
</content:encoded>
<pubDate>Sun, 12 Apr 2026 09:00:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmnge5tml006rsqm8sc1vgmiz</link>
<guid>https://status.moderntreasury.com/maintenance/cmnge5tml006rsqm8sc1vgmiz</guid>
</item>
<item>
<title>Partner Maintenance: Wells Fargo Wire Payments v1 API(s) in Production</title>
<description>
Type: Maintenance
Duration: 45 minutes
Affected Components: Payments: Partner Bank
Apr 12, 06:50:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Apr 12, 06:50:01 GMT+0 - Identified - Maintenance is now in progress Apr 12, 07:35:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 45 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>06:50:00</var> GMT+0</small><br><strong>Identified</strong> -
We are planning for a scheduled maintenance during that time..</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>06:50:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>07:35:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sun, 12 Apr 2026 06:50:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmns1fax204innif5d57gc73e</link>
<guid>https://status.moderntreasury.com/maintenance/cmns1fax204innif5d57gc73e</guid>
</item>
<item>
<title>Partner Maintenance: Wells Fargo Instant Payments v1 API(s) in Production</title>
<description>
Type: Maintenance
Duration: 5 hours and 50 minutes
Affected Components: Payments: Partner Bank
Apr 11, 05:25:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Apr 11, 05:25:01 GMT+0 - Identified - Maintenance is now in progress Apr 11, 11:15:00 GMT+0 - Completed - Maintenance has completed successfully
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Maintenance</p>
<p><strong>Duration:</strong> 5 hours and 50 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>05:25:00</var> GMT+0</small><br><strong>Identified</strong> -
We are planning for a scheduled maintenance during that time..</p>
<p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>05:25:01</var> GMT+0</small><br><strong>Identified</strong> -
Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>11:15:00</var> GMT+0</small><br><strong>Completed</strong> -
Maintenance has completed successfully.</p>
]]>
</content:encoded>
<pubDate>Sat, 11 Apr 2026 05:25:00 +0000</pubDate>
<link>https://status.moderntreasury.com/maintenance/cmns1hvnn04jvdvi8wyw1jbh7</link>
<guid>https://status.moderntreasury.com/maintenance/cmns1hvnn04jvdvi8wyw1jbh7</guid>
</item>
<item>
<title> Payment Orders: Transmission Delays</title>
<description>
Type: Incident
Duration: 14 hours and 50 minutes
Affected Components: Platform/API
Apr 8, 11:40:39 GMT+0 - Resolved - This incident has been resolved. Apr 8, 02:19:15 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. We have identified impacted customers and working with them to resolve. Apr 7, 20:51:05 GMT+0 - Investigating - We’re currently investigating an issue possibly impacting ACH/EFT payment orders. A subset of payments may experience delays in transmission and/or fail to process. Apr 7, 23:36:51 GMT+0 - Identified - We are continuing to work on a fix for this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 14 hours and 50 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>11:40:39</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>02:19:15</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result. We have identified impacted customers and working with them to resolve..</p>
<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>20:51:05</var> GMT+0</small><br><strong>Investigating</strong> -
We’re currently investigating an issue possibly impacting ACH/EFT payment orders. A subset of payments may experience delays in transmission and/or fail to process..</p>
<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>23:36:51</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident. .</p>
]]>
</content:encoded>
<pubDate>Tue, 7 Apr 2026 20:51:05 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmnp3gh8014vr13js84it7p09</link>
<guid>https://status.moderntreasury.com/incident/cmnp3gh8014vr13js84it7p09</guid>
</item>
<item>
<title>Partner Issue: Federal Reserve</title>
<description>
Type: Incident
Duration: 3 hours and 55 minutes
Affected Components: , Payments: Partner Bank,
Third Party Services →
Mar 3, 19:54:51 GMT+0 - Resolved - The Federal Reserve reports that FedACH Services have been restored and are operating normally.
For updates and additional details, please visit the Federal Reserve’s [**status page**](https://www.frbservices.org/app/status/serviceStatus.do).
If you have any further questions please reach out to our Support Team at support@moderntreasury.com Mar 3, 16:00:12 GMT+0 - Monitoring - The Federal Reserve has reported a service disruption impacting the FedACH system.
Customers may experience delays in ACH payment processing and related reporting. Modern Treasury systems remain fully operational.
For updates and additional details, please visit the Federal Reserve’s [status page](https://www.frbservices.org/app/status/serviceStatus.do).
</description>
<content:encoded>
<.
If you have any further questions please reach out to our Support Team at support@moderntreasury.com.</p>
<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:00:12</var> GMT+0</small><br><strong>Monitoring</strong> -
The Federal Reserve has reported a service disruption impacting the FedACH system.
Customers may experience delays in ACH payment processing and related reporting. Modern Treasury systems remain fully operational.
For updates and additional details, please visit the Federal Reserve’s [status page](https://www.frbservices.org/app/status/serviceStatus.do)..</p>
]]>
</content:encoded>
<pubDate>Tue, 3 Mar 2026 16:00:12 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmmasnkq10cxm50p1yeitolcv</link>
<guid>https://status.moderntreasury.com/incident/cmmasnkq10cxm50p1yeitolcv</guid>
</item>
<item>
<title>Elevated Reconciliation Delays: cell us001</title>
<description>
Type: Incident
Duration: 3 hours and 55 minutes
Affected Components: Marketing Website, Platform/API, Slack, Ledgers API, Payments: Partner Bank, Push to Warehouse
Feb 25, 19:28:02 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 25, 20:15:23 GMT+0 - Resolved - This incident has been resolved. Feb 25, 16:19:54 GMT+0 - Investigating - We have detected delays in our reconciliation system impacting customers on cell us001 and are working to resolve the issue.
You can find your cell number on the [**settings**](https://app.moderntreasury.com/settings) page of the Modern Treasury app.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
]]>
</content:encoded>
<pubDate>Wed, 25 Feb 2026 16:19:54 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmm28pt9t0chfx4rzn9krehnr</link>
<guid>https://status.moderntreasury.com/incident/cmm28pt9t0chfx4rzn9krehnr</guid>
</item>
<item>
<title>Elevated Reconciliation Delays</title>
<description>
Type: Incident
Duration: 5 days, 23 hours and 48 minutes
Feb 3, 18:30:00 GMT+0 - Investigating - We have detected delays in our reconciliation system impacting customers on cell {{us001}} and are working to resolve the issue.
Reconciliation is continuing to process, but transactions may take longer than usual to reconcile after creation. Our team is actively investigating the cause and monitoring system performance.
You can find your cell number on the [**settings**](https://app.moderntreasury.com/settings) page in the Modern Treasury application. Feb 3, 19:08:59 GMT+0 - Investigating - We are currently investigating this incident. Feb 3, 21:15:04 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 9, 18:17:39 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page in the Modern Treasury application..</p>
<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>19:08:59</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>21:15:04</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>18:17:39</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Tue, 3 Feb 2026 18:30:00 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cml706wug0247fd2sfkzzc6gn</link>
<guid>https://status.moderntreasury.com/incident/cml706wug0247fd2sfkzzc6gn</guid>
</item>
<item>
<title>Elevated Reconciliation Delays</title>
<description>
Type: Incident
Duration: 39 minutes
Affected Components: Platform/API
Feb 3, 18:30:00 GMT+0 - Investigating - We have detected delays in our reconciliation system impacting customers on cell {{us001}} and are working to resolve the issue.
Reconciliation is continuing to process, but transactions may take longer than usual to reconcile after creation. Our team is actively investigating the cause and monitoring system performance.
You can find your cell number on the [**settings**](https://app.moderntreasury.com/settings) page in the Modern Treasury application. Feb 3, 19:08:59 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page in the Modern Treasury application..</p>
<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>19:08:59</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Tue, 3 Feb 2026 18:30:00 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cml706wpn09zf8qowq9mdo53q</link>
<guid>https://status.moderntreasury.com/incident/cml706wpn09zf8qowq9mdo53q</guid>
</item>
<item>
<title>Modern Treasury Webhooks: Latency</title>
<description>
Type: Incident
Duration: 1 hour and 22 minutes
Affected Components: Platform/API
Jan 30, 19:03:13 GMT+0 - Investigating - We are currently investigating this incident. Jan 30, 19:22:06 GMT+0 - Identified - We've identified the cause and are continuing to work on a fix for this incident. This issue affects customers in Cell 001.
You can find your cell number on the [**settings**](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Jan 30, 20:25:19 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>20:25:19</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Fri, 30 Jan 2026 19:03:13 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cml193omw00ewgb0mvu8khgdd</link>
<guid>https://status.moderntreasury.com/incident/cml193omw00ewgb0mvu8khgdd</guid>
</item>
<item>
<title>Partner Issue: US Bank</title>
<description>
Type: Incident
Duration: 4 hours and 18 minutes
Affected Components: Payments: Partner Bank
Jan 26, 20:35:59 GMT+0 - Investigating - Modern Treasury has been alerted of an ongoing issue at US Bank affecting ACH Origination.
Customers of impacted banks could experience payment processing and reporting delays. Modern Treasury systems are not impacted. Jan 27, 00:54:18 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 4 hours and 18 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>20:35:59</var> GMT+0</small><br><strong>Investigating</strong> -
Modern Treasury has been alerted of an ongoing issue at US Bank affecting ACH Origination.
Customers of impacted banks could experience payment processing and reporting delays. Modern Treasury systems are not impacted..</p>
<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>00:54:18</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Mon, 26 Jan 2026 20:35:59 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmkvmnkh00jvmz20rs7lu2qty</link>
<guid>https://status.moderntreasury.com/incident/cmkvmnkh00jvmz20rs7lu2qty</guid>
</item>
<item>
<title>Reconciliation: JPMC Batch Reporting</title>
<description>
Type: Incident
Duration: 11 days, 7 hours and 22 minutes
Affected Components: Platform/API
Jan 23, 14:00:31 GMT+0 - Monitoring - Modern Treasury has identified a new JPMC reporting pattern for transactions. Customers using batched reporting may experience temporary reconciliation delays while reconciliation calibration occurs. We will provide updates as progress is made. Feb 3, 21:22:12 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 11 days, 7 hours and 22 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>14:00:31</var> GMT+0</small><br><strong>Monitoring</strong> -
Modern Treasury has identified a new JPMC reporting pattern for transactions. Customers using batched reporting may experience temporary reconciliation delays while reconciliation calibration occurs. We will provide updates as progress is made..</p>
<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>21:22:12</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Fri, 23 Jan 2026 14:00:31 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmkqy7fwi073z11ih2f0kxj7g</link>
<guid>https://status.moderntreasury.com/incident/cmkqy7fwi073z11ih2f0kxj7g</guid>
</item>
<item>
<title>Elevated App and API Errors in Cell US000</title>
<description>
Type: Incident
Duration: 1 hour and 9 minutes
Affected Components: Platform/API
Jan 20, 21:50:00 GMT+0 - Investigating - After an infrastructure upgrade in us000, we are seeing increased errors in the dashboard and on the Ledger Account / Ledger Account Category List API endpoints. We are actively investigating. Jan 20, 22:59:16 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 9 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>21:50:00</var> GMT+0</small><br><strong>Investigating</strong> -
After an infrastructure upgrade in us000, we are seeing increased errors in the dashboard and on the Ledger Account / Ledger Account Category List API endpoints. We are actively investigating..</p>
<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>22:59:16</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Tue, 20 Jan 2026 21:50:00 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmkn6uy850tng4liiaeer1rs3</link>
<guid>https://status.moderntreasury.com/incident/cmkn6uy850tng4liiaeer1rs3</guid>
</item>
<item>
<title>App and API Access Issues in Cell US000</title>
<description>
Type: Incident
Duration: 17 minutes
Affected Components: Ledgers API, Platform/API
Jan 14, 21:24:00 GMT+0 - Identified - * API outage in cell US000
* Login unavailable for all customers Jan 14, 21:41:00 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 17 minutes</p>
<p><strong>Affected Components:</strong> , </p>
<p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>21:24:00</var> GMT+0</small><br><strong>Identified</strong> -
* API outage in cell US000
* Login unavailable for all customers.</p>
<p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>21:41:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Wed, 14 Jan 2026 21:24:00 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmkekw0cz03hq3xgce1fi4i1g</link>
<guid>https://status.moderntreasury.com/incident/cmkekw0cz03hq3xgce1fi4i1g</guid>
</item>
<item>
<title>App and Connectivity Issue</title>
<description>
Type: Incident
Duration: 25 minutes
Affected Components: Platform/API
Jan 7, 19:12:01 GMT+0 - Postmortem - **Impact**
* Login was unavailable for customers.
* API traffic was unavailable for **us000** and **us002** for approximately **36 minutes**, from **10:34 AM to 11:10 AM**.
* All other cells were **unaffected**.
**Affected cells**
* us000, us002
**What Happened**
As part of ongoing infrastructure work to improve long-term stability and reduce operational overhead, we previously decommissioned an unused internal service and later removed related configuration.
On January 7, an AWS-initiated maintenance event caused a restart of a database connection service used by our platform. During the restart, a missing configuration dependency prevented the service from starting correctly. As traffic increased, the remaining healthy capacity was exhausted, leading to a temporary outage affecting logins and API traffic.
**Resolution**
The issue was identified and resolved, and service was fully restored. We have implemented additional safeguards and monitoring to prevent similar incidents in the future. Jan 7, 18:52:09 GMT+0 - Investigating - Users are currently unable to access the Modern Treasury application. Our engineering team is investigating. Jan 7, 19:12:00 GMT+0 - Resolved - This is now resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 25 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>19:12:01</var> GMT+0</small><br><strong>Postmortem</strong> -
**Impact**
* Login was unavailable for customers.
* API traffic was unavailable for **us000** and **us002** for approximately **36 minutes**, from **10:34 AM to 11:10 AM**.
* All other cells were **unaffected**.
**Affected cells**
* us000, us002
**What Happened**
As part of ongoing infrastructure work to improve long-term stability and reduce operational overhead, we previously decommissioned an unused internal service and later removed related configuration.
On January 7, an AWS-initiated maintenance event caused a restart of a database connection service used by our platform. During the restart, a missing configuration dependency prevented the service from starting correctly. As traffic increased, the remaining healthy capacity was exhausted, leading to a temporary outage affecting logins and API traffic.
**Resolution**
The issue was identified and resolved, and service was fully restored. We have implemented additional safeguards and monitoring to prevent similar incidents in the future..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>18:52:09</var> GMT+0</small><br><strong>Investigating</strong> -
Users are currently unable to access the Modern Treasury application. Our engineering team is investigating..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>19:12:00</var> GMT+0</small><br><strong>Resolved</strong> -
This is now resolved..</p>
]]>
</content:encoded>
<pubDate>Wed, 7 Jan 2026 18:52:09 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmk4dkuhi04h713icepbk5zry</link>
<guid>https://status.moderntreasury.com/incident/cmk4dkuhi04h713icepbk5zry</guid>
</item>
<item>
<title>Modern Treasury Webhooks: Latency</title>
<description>
Type: Incident
Duration: 1 hour and 2 minutes
Affected Components: Platform/API
Jan 7, 16:09:02 GMT+0 - Identified - We've identified the cause and are continuing to work on a fix for this incident. This issue affects customers in Cell 001 and Cell 005.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Jan 7, 17:06:04 GMT+0 - Monitoring - Delayed webhooks have begun resolving and we are currently monitoring. Jan 7, 17:11:00 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>17:06:04</var> GMT+0</small><br><strong>Monitoring</strong> -
Delayed webhooks have begun resolving and we are currently monitoring..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>17:11:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Wed, 7 Jan 2026 16:09:02 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmk47r2s6001ezpafz55qbmlr</link>
<guid>https://status.moderntreasury.com/incident/cmk47r2s6001ezpafz55qbmlr</guid>
</item>
<item>
<title>Modern Treasury API: Elevated Latency - Cell: US001</title>
<description>
Type: Incident
Duration: 57 minutes
Affected Components: Ledgers API, Platform/API
Jan 6, 20:25:29 GMT+0 - Investigating - We are investigating elevated latency in the API and UI in cell US001\.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Jan 6, 21:22:44 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Jan <var data-var='date'> 6</var>, <var data-var='time'>21:22:44</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Tue, 6 Jan 2026 20:25:29 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmk31h0xn00nafjx9cvj6xzaq</link>
<guid>https://status.moderntreasury.com/incident/cmk31h0xn00nafjx9cvj6xzaq</guid>
</item>
<item>
<title>App and API Access Issues in Cell US001</title>
<description>
Type: Incident
Duration: 1 hour and 15 minutes
Affected Components: Platform/API
Dec 17, 15:33:29 GMT+0 - Investigating - We are currently investigating this incident.
You can find your cell number on the [settings](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Dec 17, 15:50:49 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 17, 16:06:08 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 17, 16:48:31 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>15:50:49</var> GMT+0</small><br><strong>Identified</strong> -
We are continuing to work on a fix for this incident..</p>
<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>16:06:08</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>16:48:31</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Wed, 17 Dec 2025 15:33:29 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmja68h66064drrnz8x8rt4xk</link>
<guid>https://status.moderntreasury.com/incident/cmja68h66064drrnz8x8rt4xk</guid>
</item>
<item>
<title>Ledgers: Transaction Endpoint </title>
<description>
Type: Incident
Duration: 1 hour and 25 minutes
Affected Components: Ledgers API
Dec 10, 19:23:28 GMT+0 - Investigating - Our engineers have identified unexpected behavior affecting the Ledger Transaction endpoint’s performance and are actively investigating. Dec 10, 19:58:08 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 10, 20:48:37 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 25 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>19:23:28</var> GMT+0</small><br><strong>Investigating</strong> -
Our engineers have identified unexpected behavior affecting the Ledger Transaction endpoint’s performance and are actively investigating..</p>
<p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>19:58:08</var> GMT+0</small><br><strong>Monitoring</strong> -
We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>20:48:37</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Wed, 10 Dec 2025 19:23:28 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmj0ed9vm015p9bco0ipvqiv2</link>
<guid>https://status.moderntreasury.com/incident/cmj0ed9vm015p9bco0ipvqiv2</guid>
</item>
<item>
<title>500 Errors Affecting Search Functionality</title>
<description>
Type: Incident
Duration: 16 minutes
Affected Components: Platform/API
Dec 9, 21:02:28 GMT+0 - Investigating - Our team identified an issue that affected all search requests, which may have resulted in 500 Internal Server Errors for some users. Dec 9, 21:18:41 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 16 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>21:02:28</var> GMT+0</small><br><strong>Investigating</strong> -
Our team identified an issue that affected all search requests, which may have resulted in 500 Internal Server Errors for some users..</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>21:18:41</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Tue, 9 Dec 2025 21:02:28 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmiz2gqgi05hnek8s3ktewbnr</link>
<guid>https://status.moderntreasury.com/incident/cmiz2gqgi05hnek8s3ktewbnr</guid>
</item>
<item>
<title>Elevated Reconciliation Delays: cell us005</title>
<description>
Type: Incident
Duration: 1 hour and 52 minutes
Affected Components: Platform/API
Nov 26, 17:10:36 GMT+0 - Investigating - We have detected delays in our reconciliation system impacting customers on cell us005 and are working to resolve the issue.
You can find your cell number on the [**settings**](https://app.moderntreasury.com/settings) page of the Modern Treasury app. Nov 26, 17:43:17 GMT+0 - Identified - We have identified and quarantined the issue. The reconciliation processing rate is improving. Nov 26, 19:02:49 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
< page of the Modern Treasury app..</p>
<p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>17:43:17</var> GMT+0</small><br><strong>Identified</strong> -
We have identified and quarantined the issue. The reconciliation processing rate is improving..</p>
<p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>19:02:49</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Wed, 26 Nov 2025 17:10:36 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmig9ghci01w4j8jf7gevuny6</link>
<guid>https://status.moderntreasury.com/incident/cmig9ghci01w4j8jf7gevuny6</guid>
</item>
<item>
<title>APP: Inability to Approve Payment Orders</title>
<description>
Type: Incident
Duration: 27 minutes
Affected Components: Platform/API
Nov 20, 21:26:39 GMT+0 - Investigating - We're actively investigating issues related to Payment Order approvals. Nov 20, 21:53:32 GMT+0 - Resolved - This incident has been resolved.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 27 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>21:26:39</var> GMT+0</small><br><strong>Investigating</strong> -
We're actively investigating issues related to Payment Order approvals..</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>21:53:32</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
]]>
</content:encoded>
<pubDate>Thu, 20 Nov 2025 21:26:39 +0000</pubDate>
<link>https://status.moderntreasury.com/incident/cmi7xynzu053dsq07vdid58un</link>
<guid>https://status.moderntreasury.com/incident/cmi7xynzu053dsq07vdid58un</guid>
</item>
</channel>
</rss>