Over the last several months, we have experienced four distinct service disruptions that prevented reliable access to Treasury Prime’s platform. I know how impactful this is to our customers, and I’m sorry for the pain these outages have caused. We recognize that our service is mission critical for the end users that rely on consistent money movement to live their lives and run their businesses. I’d like to share a bit more context about what happened and how we’re responding to avoid these issues moving forward.

Timeline

May 5 2023 (30 minutes)

A spike in book transfer requests caused contention within our database-backed queue system; once the blocking queries were canceled, a full platform restart remediated the service disruption.

June 21 2023 (43 minutes)

A subsequent spike in book transfer requests again caused contention within our database-backed queue system; once the blocking queries were canceled, a full platform restart remediated the service disruption.

June 26 2023 (58 minutes)

Due to an unusual increase in pending ACH debit payment instructions, we experienced a spike in book transfer requests that caused contention within our database-backed queue system; in this instance, the blocking queries could not be canceled and a database failover was required to