Molecule Outage History

Molecule is up right now

There were 3 Molecule outages since February 13, 2026 totaling 3h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.molecule.io

Major April 28, 2026

Auth0 - Elevated Errors on Public Cloud Environments

Detected by Pingoru
Apr 28, 2026, 09:41 PM UTC
Resolved
Apr 28, 2026, 10:41 PM UTC
Duration
59m
Affected: Auth0 User AuthenticationAuth0 User Authentication
Timeline · 1 update
  1. monitoring Apr 28, 2026, 09:41 PM UTC

    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.

Read the full incident report →

Major April 15, 2026

Report Outtage - Resolved

Detected by Pingoru
Apr 15, 2026, 11:07 AM UTC
Resolved
Apr 15, 2026, 12:58 PM UTC
Duration
1h 50m
Timeline · 5 updates
  1. identified Apr 15, 2026, 11:07 AM UTC

    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.

  2. identified Apr 15, 2026, 11:33 AM UTC

    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.

  3. identified Apr 15, 2026, 12:05 PM UTC

    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.

  4. identified Apr 15, 2026, 12:33 PM UTC

    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.

  5. resolved Apr 15, 2026, 12:58 PM UTC

    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.

Read the full incident report →

Notice February 13, 2026

Morningstar settlement market data not loading

Detected by Pingoru
Feb 13, 2026, 09:25 AM UTC
Resolved
Feb 13, 2026, 10:16 AM UTC
Duration
51m
Timeline · 4 updates
  1. investigating Feb 13, 2026, 09:25 AM UTC

    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.

  2. investigating Feb 13, 2026, 09:50 AM UTC

    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.

  3. monitoring Feb 13, 2026, 10:02 AM UTC

    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.

  4. resolved Feb 13, 2026, 10:16 AM UTC

    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.

Read the full incident report →

Looking to track Molecule downtime and outages?

Pingoru polls Molecule's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Molecule reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Molecule alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Molecule for free

5 free monitors · No credit card required