pingoru pingoru Flourish Software had 9 outages in the last 2 years totaling 2h 10m of downtime, averaging 0.4 incidents per month.
There were 9 Flourish Software outages since October 9, 2025 totaling 2h 10m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We're currently investigating an issue with the Outbound Order Screen failing to load.
We are monitoring the issue and believe it is resolved.
The issue is resolved.
We are investigating an issue with the QuickBooks integration.
The QuickBooks integration is now operating normally.
We are investigating reports of Flourish Web service issues. Error details: HTTP 503... This issue has persisted for 10 consecutive checks. Status Code: 503 URL: https://app.flourishsoftware.com/bff/auth/login
The Flourish Web service has been restored and is operating normally.
We are investigating reports of disruption in the Metrc API integration for some states.
All METRC state client services appear to be operating normally.
This incident has been resolved.
We are investigating an issue with LeafLink inventory sync. No successful syncs detected in the last monitoring window. (Minimum 1 required)
Inventory syncing to LeafLink appears to be operating normally.
We've identified an issue with some underlying infrastructure and are actively working to resolve this.
The application is now up.
The database failed over due to a replication lag in AWS. We are working with AWS support to investigate this further. No data was lost, the system recovered automatically, and we caught this in real time.
We are currently investigating an issue
The app is now operational. We are investigating the root cause.
Monitoring while we investigate this further
Resolving as we investigate the root cause. We apologize for the interruption.
Amazon Web Services experienced an internal network failure, resulting in one of Flourish’s databases failing over. The application became unstable during this period. No data was lost, and we quickly recovered from this incident. 2026-01-26 21:59:46 UTC \[-\] Started cross AZ failover to DB instance 2026-01-26 22:00:03 UTC \[-\] Completed RDS initiated failover to DB instance
We are investigating reports of service disruption.
The service has been fully restored.
We are upgrading the application infrastructure.
The service has been fully restored.