All Systems Operational

Peach Adaptive Core Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
99.98 % uptime
Today
Data Operational
90 days ago
100.0 % uptime
Today
Loan and Payment Tapes Operational
90 days ago
100.0 % uptime
Today
Database Replica Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Agent Portal Operational
90 days ago
99.88 % uptime
Today
Borrower Portal Operational
90 days ago
100.0 % uptime
Today
Payment Processing Operational
90 days ago
100.0 % uptime
Today
Communications Operational
90 days ago
99.97 % uptime
Today
SMS Operational
90 days ago
100.0 % uptime
Today
Email Operational
90 days ago
100.0 % uptime
Today
Telephony Operational
90 days ago
100.0 % uptime
Today
Physical Mail Operational
90 days ago
99.94 % uptime
Today
Campaigns Operational
90 days ago
99.86 % uptime
Today
Credit Reporting Operational
90 days ago
100.0 % uptime
Today
Compliance Guard Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Nov 13, 2025

No incidents reported today.

Nov 12, 2025

No incidents reported.

Nov 11, 2025

No incidents reported.

Nov 10, 2025

No incidents reported.

Nov 9, 2025

No incidents reported.

Nov 8, 2025

No incidents reported.

Nov 7, 2025

No incidents reported.

Nov 6, 2025
Resolved - After closely monitoring our system for 42 hours without further issue, the incident impacting our Core API has been resolved and all affected service continue to operate normally.
Nov 6, 20:26 UTC
Update - All core services are performing normally, and we are maintaining our standard monitoring posture overnight.
Nov 6, 01:32 UTC
Update - The system remained stable overnight, and service has fully normalized.

We confirmed that impacted endpoints performed within normal operating parameters throughout the night's critical processing window. We are returning to our standard monitoring posture.

Thank you for your patience during this period of elevated observation.

Nov 5, 18:01 UTC
Update - All core services are performing normally, and we are maintaining our elevated monitoring posture overnight. We will post another update if unusual activity is detected.
Nov 5, 02:27 UTC
Update - All affected endpoints continue to operate normally. We are closely monitoring the system after the rollback of the fix that caused the temporary errors and latency.
Nov 5, 01:15 UTC
Monitoring - The rollback for the issue impacting several endpoints has been deployed. We are now closely monitoring the system to confirm full recovery.
Nov 5, 00:09 UTC
Identified - We are currently experiencing increased latency and error rates impacting certain endpoints due to an additional mitigation measure / optimization being rolled out as part of the incident.

We are actively rolling back the fix. We will provide an update within the next hour or as more information becomes available.

Nov 4, 23:49 UTC
Update - Since our last update, the Core API remains stable and fully operational with no further errors or latency spikes for over 24 hours. The team has identified the underlying issue, and we have observed that our mitigation measures have addressed the intermittent latency. Given the stability over the past day, we anticipate resolving this incident tomorrow, but will continue active monitoring until then.
Nov 4, 18:02 UTC
Update - We received a burst of traffic around 9:30pm PT that caused the issue to resume momentarily. We assigned more resources, see that the impact has subsided, and are actively monitoring.
Nov 3, 06:08 UTC
Monitoring - No further errors or latency issues have occurred since last posting. We will continue to monitor the effectiveness of the deployed fix.
Nov 2, 11:13 UTC
Update - We have implemented mitigation measures and have seen recovery in latency and error rates. Our engineers continue to monitor the situation and are actively working to identify the root cause.
Nov 2, 10:18 UTC
Update - We are continuing to investigate the issue.
Nov 2, 09:15 UTC
Investigating - We are currently investigating increased latency and error rates impacting our Core API. Users may experience intermittent errors when making API requests. Our engineers are actively working to identify the root cause and restore full functionality as quickly as possible. We will provide an update within the next hour as more information becomes available.
Nov 2, 08:15 UTC
Nov 5, 2025
Nov 4, 2025
Nov 3, 2025
Nov 2, 2025
Resolved - All metro2 files have been delivered.
Nov 2, 22:44 UTC
Identified - The delivery of some Metro2 files may be delayed. The team is aware of the issue and working to resolve it.
Nov 1, 18:03 UTC
Nov 1, 2025
Resolved - This incident has been resolved.
Nov 1, 08:01 UTC
Identified - Some customer replica snapshots are delayed. We have identified the issue and are working to resolve it.
Oct 31, 17:09 UTC
Oct 31, 2025
Oct 30, 2025
Resolved - There are no longer any across the board latency issues for the `/search` endpoint. However, there are periodic slowdowns when doing a "full text search" with certain inputs.

When using the Peach CRM frontend a "full text search" means using the search box without specifying a search prefix. When using the Peach API this means using the param `_hasTheWords=`.

If you encounter a slow down when using the full text search, a workaround is to specify the appropriate search prefix. e.g., if you are searching for a borrower external ID like `my-external-id` in the search box type `id:my-external-id`. If you are using the API use `.../search?_hasTheWords=my-external-id`

Oct 30, 22:39 UTC
Monitoring - We've released a fix and are monitoring to see if it resolves the issue.
Oct 28, 22:56 UTC
Update - The impact of the increased latency is less widespread than we originally presumed. Only certain classes of input for the previously mentioned parameters are causing the slowdown.

We have a fix we believe will address the issue and will roll it out shortly.

Oct 27, 23:23 UTC
Identified - The Borrower and Interaction search endpoints have increased latency when searching with "full text" queries. These include `_hasTheWords` and `_notTheWords` parameters. We've identified the issue and are working on a fix.
Oct 27, 19:43 UTC