Charles River for Private Markets Status Page

Apr 29, 2026 · resolved Apr 30

The previously reported intermittent update failures have been resolved. The affected lookup‑based persistence has been migrated to a higher‑capacity data storage approach in both Production and UAT. This includes the reference cache and related staging structures used across ingestion workflows. Given the breadth of this change across ingestion processes, we are closely monitoring runs to ensure continued stability and data consistency. Please contact support if you observe any unexpected behavior.

Jul 12, 2025 · resolved Jul 13

### 🔍 Summary On July 12, 2025, a product patch release triggered widespread failures across platform integrations, specifically affecting recipes and SFTP processes. The issue stemmed from a database connection failure and unintended execution of SFTP recipes, leading to queue congestion and delayed data ingestion. ### 📌 Root Cause * A **product patch** released on July 12 caused: * Failures in all recipes directly connected to the database. * Unintended execution of SFTP recipes, which processed all available files from Client’s MA SFTP servers simultaneously. * This led to **queue congestion** and disrupted integration workflows. ### 📊 Impact Summary **Affected Systems:** * Integration recipes \(DB connectors\) * SFTP integrations with client **Impacted Clients:** * Clients using integration services **Business Impact:** * Delayed and out-of-order data ingestion. * Manual intervention required to reset queues. * Risk of inaccurate downstream reporting and analytics. ### ⚠️ Contributing Factors * **No file archiving** during SFTP server migration. * **OS upgrade** from AWS Linux 2 to AWS Linux 2023 introduced a new network interface \(`ens5` instead of `eth0`\). * Existing NAT masquerading scripts were hardcoded to `eth0`, causing failures until updated. ### 🛠️ Mitigation & Resolution * **Immediate Actions:** * Paused polling recipes to prevent further failures. * DevOps team initiated investigation and identified the database connection issue. * **Resolution:** * Database connection issue resolved. * Polling recipes re-enabled. * System stability verified and performance monitoring initiated. ### ✅ Follow-Up Actions * Review and update all scripts to avoid hardcoded network interface dependencies. * Implement file archiving protocols during SFTP migrations. * Enhance patch testing procedures to include integration impact assessments. * Improve alerting and monitoring for recipe execution anomalies.

Jul 12, 2025 · resolved Jul 12

We are currently experiencing issues with platform integrations, resulting in failed or delayed integration runs. Our integration team began investigating the issue and is actively working to identify the root cause and implement a fix. We will share updates as soon as more information becomes available. We appreciate your patience and understanding.

Oct 29, 2024 · resolved Oct 29

On Monday 10/28 we experienced a PowerBI outage that began at 11:15 ET The outage impacted multiple regions, with some Clients experiencing the inability to refresh data due to regional PowerBI gateways going offline We quickly resolved the issue by 13:55 ET by working closely with Microsoft We are in the process of doing a root cause analysis in partnership with Microsoft and remediation to prevent additional occurrences. Additional details to follow.

Feb 1, 2023 · resolved Feb 1

The issue is resolved now. This problem was caused by a bug in the way that Mercatus handled embedded content. A fix was identified that requires no downtime, and that fix has been deployed. If you have any questions, please feel free to reach out to [email protected] Thanks, Mercatus Support