Time: Oct. 23, 2024, 5:57 p.m.

Status: Resolved

Update: We have identified the root cause of this issue and have successfully updated and validated the impacted marks. The affected trades have been revalued. We will share details in a post-mortem soon. Thank you for your patience and understanding during this process.

Time: Oct. 23, 2024, 12:46 p.m.

Status: Investigating

Update: We are aware of an issue related to `user` market data updating correctly. We are investigating as a priority.

Time: Oct. 22, 2024, 3:22 p.m.

Status: Resolved

Update: We implemented a code fix last night to prevent new trade updates from having this problem. Today we will run a script to fix trades with unrecognized user updates between 10/11 and 10/20. We will reach out on a customer-by-customer basis if we identify any trades that may cause large PnL swings.

Time: Oct. 21, 2024, 11:02 p.m.

Status: Identified

Update: We have revalued all trades that were edited through the UI today. We are planning to have a code fix in place tomorrow that will prevent this issue from happening to new trades, and tomorrow we plan to identify and fix any trades that were updated between Oct 11 and yesterday We will continue to monitor

Time: Oct. 21, 2024, 5:20 p.m.

Status: Investigating

Update: We've identified an issue where changes made through the Molecule UI are recognized, and appear on the trade. However, these changes are not carried forward into our valuations table. So the report extracts, valuations pop-ups, and anything else that references valuations is incorrect, for trades that have been manually edited. We are working urgently to identify the full scale and duration of the issue, and to implement a fix

Time: Sept. 12, 2024, 1:27 p.m.

Status: Postmortem

Update: **Summary of Incident** On September 9, 2024, between 18:22 UTC to approximately 18:37 UTC, a brief service disruption impacted our Europe-based users. We regret any inconvenience caused and thank you for your patience and understanding. \*\*What happened?\*\*An outage affected access to our system for users in Europe for a period of 15 minutes. \*\*Why?\*\*The outage occurred due to a human error while preparing for disaster recovery testing, which inadvertently led to the removal of critical system resources. **Corrective/Preventive Actions**To prevent similar incidents in the future, we are the following action: * **Enhanced Protections**: Implement additional safeguards in Molecule's test and production environments to prevent accidental removal or interruption of critical components. We sincerely appreciate your continued patience and understanding as we work to improve the reliability of our services.

Time: Sept. 9, 2024, 7:15 p.m.

Status: Resolved

Update: On September 9, 2024, users experienced an outage from approximately 18:21 UTC to approximately 18:37 UTC. We apologize for the inconvenience and will provide an update with details in the coming days.

Time: July 22, 2024, 2:17 p.m.

Status: Resolved

Update: This incident has been resolved. We have not seen any issues with reconciliations or any 3rd party data.

Time: July 19, 2024, 9:10 p.m.

Status: Monitoring

Update: Molecule has been informed by an FCM (Macquarie) that they have been affected by the outage at Cloudstrike early this morning. We did not see any issues from FCM data for yesterday. We will continue to proactively monitor data tonight and tomorrow and update Customers who may be affected on a case by case basis.

Time: July 5, 2024, 9:35 p.m.

Status: Postmortem

Update: # **Incident Report: Incomplete Valuation Data - Resolved** **Date of Resolution:** July 1, 2024 ## **Summary** On Monday morning, July 1, 2024, an issue where certain trades were missing valuation entries was identified and addressed the same day. We apologize for any inconvenience this may have caused and appreciate your understanding. ## **What happened?** The Molecule application has a feature that limits how far into the future valuation entries will be created when trades are made. However, there was no mechanism to create entries for skipped as\_of dates when they became relevant. These previously excluded entries became relevant for the first time on July 1, and some customers began reporting the issue on Friday, June 28. ## **Why** * When implementing the as\_of\_date limits for entry building, a corresponding job to build skipped entries before they became relevant was not available to be run in production. * The system did not include sufficient checks to identify these issues ahead of time. ## **Corrective/Preventive Actions**  * A script was deployed immediately to generate missing entries, addressing the issue and correcting the problem for impacted customers as soon as possible.  This script will run daily to ensure all entries are built until we remove the limit for good. * An internal check has been created to catch missing entries ahead of time. ‌ We apologize for any inconvenience caused and appreciate your understanding as we work to improve our systems and prevent similar issues in the future.

Time: July 1, 2024, 8:07 p.m.

Status: Resolved

Update: This incident has been resolved. All current-day valuations line up with expectations. Later today we will run a script to fix any missing place-holder valuations for tomorrow's as_of date, and we will continue monitoring forward-dated valuations

Time: July 1, 2024, 7:16 p.m.

Status: Investigating

Update: Multiple trades have not valued for today. We are in the process of fixing manually and doing a root cause analysis. We will reach out to individual risk managers as we clear each customer, and we will update this incident as we get a comprehensive solution.