Molecule had 13 outages in the last 2 years totaling 126h 17m of downtime — averaging 0.5 incidents per month.
There were 13 Molecule outages since July 1, 2024 totaling 126h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
We continue to monitor the Auth0 status but have not registered any impacts to the Molecule platform at this time. However, since user logins may be impacted, we continue to stay alert. Please report any login issues to [email protected] immediately.
We have identified the issue causing the current outage of our reporting capabilities within Molecule. This is isolated to reports and all other functionality remains functional. We are working on a resolution and will be back with you shortly.
We are working to resolve the issue causing the current outage of our reporting capabilities within Molecule. This is isolated to reports and all other functionality remains functional. We are working on a resolution and will be back as soon as we have an update.
Molecule's reporting functionality is currently unavailable. We are actively working with our third-party vendor to resolve the issue. All other features remain fully operational. We will provide an update as soon as possible.
Our team is actively working with our third-party vendor to restore reporting services as quickly as possible. All other functionality remains unaffected. We appreciate your patience and will share another update shortly.
Reporting services have been fully restored. We appreciate your patience while we worked to resolve this issue and apologize for any disruption to your workflow.
We are currently experiencing a technical issue which has prevented the Morningstar settlement market data from updating for yesterday (2026-02-12). Separately, no copied market data has been generated for today. Our Engineering team is actively investigating the issue. We will provide an update as soon as the matter has been resolved. Thank you for your understanding.
Market data is loading on delay. Performance is degraded due to a large market file. We have scaled up our processing workings to handle the load. We investigating further to ensure full processing of market files and will continue to monitor until we are confident this is resolved. Everything else is up, working and accessible.
We are monitoring the market data which continues to load after we scaled up our workers to handle the processing. A large data file backed up our processing of market data which we are now steadily processing. We are actively checking data across all customers to ensure market data has loaded. Please contact [email protected] if you are missing market data.
An EU Severity 1 incident occurred where market data is not loading or copying, causing downtime for customers; the issue was triggered by a web alert and began at 9:22:03 AM UTC on 2/13/2026 (the incident was created by a web alert at 8:51:02 AM UTC); the cause is EU workers not scaling up because the Horizontal Pod Autoscaler didn't obtain CPU metrics, and the response involved manually scaling the workers to process the market data queue first and verifying customer accounts. Further root cause analysis will be performed and actions taken to ensure this scaling issue doesn't reoccur. We apologize for any interruption in your daily business.
We are currently experiencing an issue with our cloud provider that is causing delays in data processing. We are working to resolve this as quickly as we can and will continue to post periodic updates as we have them. We appreciate your patience as we work through this.
Our cloud provider is continuing to work through a widespread issue impacting the region where our U.S. application runs. We spent the morning testing solutions to run resources in a cloud region that is not impacted and we are confident that we can do so if the need arises. Up to this point, we have not had a major impact to our application, however, workload typically increases in the afternoon when end-of-day data processing begins. We are prepared to deploy additional resources in the second region to keep up with data processing. We will continue to provide updates throughout the afternoon.
Our cloud provider has addressed the issue and we can confirm improvements. Earlier this afternoon, we deployed additional resources to a second region to keep up with workload. We will continue to monitor our resources closely and provide periodic updates.
This incident has been resolved. We appreciate your patience while working through this.
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.
**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.
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.
This incident has been resolved. We have not seen any issues with reconciliations or any 3rd party data.