Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Molecule and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Molecule.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Europe | Active |
Amazon Web Services - Databases | Active |
Amazon Web Services - DNS | Active |
Amazon Web Services - EC2 | Active |
Amazon Web Services - EKS | Active |
Amazon Web Services - File Storage | Active |
Auth0 User Authentication | Active |
Molecule Europe | Active |
US | Active |
Amazon Web Services - Databases | Active |
Amazon Web Services - DNS | Active |
Amazon Web Services - EC2 | Active |
Amazon Web Services - EKS | Active |
Auth0 User Authentication | Active |
Molecule | Active |
View the latest incidents for Molecule and check for official updates:
Description: As a result of an ICE outage, there is a possibility that trades were not captured in Molecule for a brief period of time this morning. We have reset all connections with ICE and have requested trade history. All deals should currently be captured in Molecule. Please contact the customer success team at [email protected] if you find any missing trades.
Status: Resolved
Impact: None | Started At: Oct. 14, 2019, 6:05 p.m.
Description: We’re sorry for the service interruption Monday, and we hope it didn’t create a significant inconvenience for you. We want to let you know a bit more detail about what happened. On Monday at 17:05 US Central Time, our primary database restarted without warning. Our systems handled the incident as expected, and when the database came back online, the Molecule application recovered. Recovery was complete by 17:14. Our investigation into the restart is complete, and it appears that the database was restarted by Amazon, because of an underlying hardware problem. This is unusual, but not unprecedented. While recovery was relatively quick, we have already been planning a move to a read replica system – whereby, if the read/write version of our database is affected, reads can continue. This incident lends more urgency to the planning for this feature.
Status: Postmortem
Impact: Major | Started At: Aug. 26, 2019, 10:05 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.