Flourish Software Outage History

Flourish Software is up right now

Pingoru has recorded 40 incidents for Flourish Software: 38 in the last 12 months and 1 in the last 90 days.

Source: status.flourishsoftware.com

40incidents recorded
38last 12 months
1last 90 days
12 minutestypical duration

Incidents, newest first

Major August 11, 2026 Outbound Order Screen Issue 12m Flourish Web

Started Aug 11, 2026, 01:54 PM UTC· resolved Aug 11, 2026, 02:06 PM UTC

  1. investigating Aug 11, 2026, 01:54 PM UTC

    We're currently investigating an issue with the Outbound Order Screen failing to load.

  2. monitoring Aug 11, 2026, 01:59 PM UTC

    We are monitoring the issue and believe it is resolved.

  3. resolved Aug 11, 2026, 02:06 PM UTC

    The issue is resolved.

Read the full incident report →

Major July 16, 2026 QuickBooks Integration Service Disruption 24m Quickbooks API

Started Jul 16, 2026, 03:51 AM UTC· resolved Jul 16, 2026, 04:15 AM UTC

  1. investigating Jul 16, 2026, 03:51 AM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Jul 16, 2026, 04:15 AM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major June 24, 2026 QuickBooks Integration Service Disruption 24m Quickbooks API

Started Jun 24, 2026, 04:30 PM UTC· resolved Jun 24, 2026, 04:55 PM UTC

  1. investigating Jun 24, 2026, 04:38 PM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Jun 24, 2026, 04:55 PM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major June 20, 2026 QuickBooks Integration Service Disruption 2m Quickbooks API

Started Jun 20, 2026, 02:01 PM UTC· resolved Jun 20, 2026, 02:04 PM UTC

  1. investigating Jun 20, 2026, 02:01 PM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Jun 20, 2026, 02:04 PM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major June 17, 2026 Flourish Web Service Disruption 2m Flourish Web

Started Jun 17, 2026, 01:38 PM UTC· resolved Jun 17, 2026, 01:40 PM UTC

  1. investigating Jun 17, 2026, 01:38 PM UTC

    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

  2. resolved Jun 17, 2026, 01:40 PM UTC

    The Flourish Web service has been restored and is operating normally.

Read the full incident report →

Major June 13, 2026 Flourish Web Service Disruption 9m Flourish Web

Started Jun 13, 2026, 09:13 AM UTC· resolved Jun 13, 2026, 09:22 AM UTC

  1. investigating Jun 13, 2026, 09:13 AM UTC

    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

  2. resolved Jun 13, 2026, 09:22 AM UTC

    The Flourish Web service has been restored and is operating normally.

Read the full incident report →

Major June 6, 2026 QuickBooks Integration Service Disruption 3m Quickbooks API

Started Jun 06, 2026, 10:39 AM UTC· resolved Jun 06, 2026, 10:42 AM UTC

  1. investigating Jun 06, 2026, 10:39 AM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Jun 06, 2026, 10:42 AM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Notice June 4, 2026 Metrc API Integration Service Disruption 31m Metrc CO API, Metrc DC API, Metrc LA API, Metrc MA API and 12 more

Started Jun 04, 2026, 10:11 PM UTC· resolved Jun 04, 2026, 10:42 PM UTC

  1. investigating Jun 04, 2026, 10:11 PM UTC

    We are investigating reports of disruption in the Metrc API integration for some states.

  2. investigating Jun 04, 2026, 10:42 PM UTC

    All METRC state client services appear to be operating normally.

  3. resolved Jun 04, 2026, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 4, 2026 LeafLink Inventory Sync Service Disruption 42m Leaflink

Started Jun 04, 2026, 10:01 PM UTC· resolved Jun 04, 2026, 10:43 PM UTC

  1. investigating Jun 04, 2026, 10:01 PM UTC

    We are investigating an issue with LeafLink inventory sync. No successful syncs detected in the last monitoring window. (Minimum 1 required)

  2. resolved Jun 04, 2026, 10:43 PM UTC

    Inventory syncing to LeafLink appears to be operating normally.

Read the full incident report →

Major May 8, 2026 QuickBooks Integration Service Disruption 1m Quickbooks API

Started May 08, 2026, 07:49 PM UTC· resolved May 08, 2026, 07:50 PM UTC

  1. investigating May 08, 2026, 07:49 PM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved May 08, 2026, 07:50 PM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major April 10, 2026 QuickBooks Integration Service Disruption 3m Quickbooks API

Started Apr 10, 2026, 10:35 AM UTC· resolved Apr 10, 2026, 10:38 AM UTC

  1. investigating Apr 10, 2026, 10:35 AM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Apr 10, 2026, 10:38 AM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major April 7, 2026 QuickBooks Integration Service Disruption 1m Quickbooks API

Started Apr 07, 2026, 09:38 PM UTC· resolved Apr 07, 2026, 09:39 PM UTC

  1. investigating Apr 07, 2026, 09:38 PM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Apr 07, 2026, 09:39 PM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major March 20, 2026 QuickBooks Integration Service Disruption 6m Quickbooks API

Started Mar 20, 2026, 04:38 AM UTC· resolved Mar 20, 2026, 04:45 AM UTC

  1. investigating Mar 20, 2026, 04:38 AM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Mar 20, 2026, 04:45 AM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major March 20, 2026 QuickBooks Integration Service Disruption 7m Quickbooks API

Started Mar 20, 2026, 03:24 AM UTC· resolved Mar 20, 2026, 03:32 AM UTC

  1. investigating Mar 20, 2026, 03:24 AM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Mar 20, 2026, 03:32 AM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major March 16, 2026 QuickBooks Integration Service Disruption 5m Quickbooks API

Started Mar 16, 2026, 03:17 PM UTC· resolved Mar 16, 2026, 03:22 PM UTC

  1. investigating Mar 16, 2026, 03:17 PM UTC

    We are investigating an issue with the QuickBooks integration.

  2. resolved Mar 16, 2026, 03:22 PM UTC

    The QuickBooks integration is now operating normally.

Read the full incident report →

Major March 8, 2026 LeafLink Inventory Sync Service Disruption 1m Leaflink

Started Mar 08, 2026, 02:22 PM UTC· resolved Mar 08, 2026, 02:23 PM UTC

  1. investigating Mar 08, 2026, 02:22 PM UTC

    We are investigating an issue with LeafLink inventory sync. No successful syncs detected in the last monitoring window. (Minimum 1 required)

  2. resolved Mar 08, 2026, 02:23 PM UTC

    LeafLink inventory sync is now functioning normally. Detected 8423 successful syncs in the last monitoring window.

Read the full incident report →

Major March 8, 2026 LeafLink Inventory Sync Service Disruption 1m Leaflink

Started Mar 08, 2026, 01:32 PM UTC· resolved Mar 08, 2026, 01:33 PM UTC

  1. investigating Mar 08, 2026, 01:32 PM UTC

    We are investigating an issue with LeafLink inventory sync. No successful syncs detected in the last monitoring window. (Minimum 1 required)

  2. resolved Mar 08, 2026, 01:33 PM UTC

    LeafLink inventory sync is now functioning normally. Detected 9144 successful syncs in the last monitoring window.

Read the full incident report →

Major March 8, 2026 LeafLink Inventory Sync Service Disruption 1m Leaflink

Started Mar 08, 2026, 09:49 AM UTC· resolved Mar 08, 2026, 09:50 AM UTC

  1. investigating Mar 08, 2026, 09:49 AM UTC

    We are investigating an issue with LeafLink inventory sync. No successful syncs detected in the last monitoring window. (Minimum 1 required)

  2. resolved Mar 08, 2026, 09:50 AM UTC

    LeafLink inventory sync is now functioning normally. Detected 8983 successful syncs in the last monitoring window.

Read the full incident report →

Critical January 30, 2026 Service Outage 7m Flourish Web, Flourish POS

Started Jan 30, 2026, 02:00 PM UTC· resolved Jan 30, 2026, 02:07 PM UTC

  1. identified Jan 30, 2026, 02:00 PM UTC

    We've identified an issue with some underlying infrastructure and are actively working to resolve this.

  2. resolved Jan 30, 2026, 02:07 PM UTC

    The application is now up.

  3. postmortem Jan 30, 2026, 02:55 PM UTC

    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.

Read the full incident report →

Critical January 26, 2026 Application Service Interruption 5m Flourish Web, Flourish POS

Started Jan 26, 2026, 10:04 PM UTC· resolved Jan 26, 2026, 10:10 PM UTC

  1. investigating Jan 26, 2026, 10:04 PM UTC

    We are currently investigating an issue

  2. investigating Jan 26, 2026, 10:07 PM UTC

    The app is now operational. We are investigating the root cause.

  3. monitoring Jan 26, 2026, 10:08 PM UTC

    Monitoring while we investigate this further

  4. resolved Jan 26, 2026, 10:10 PM UTC

    Resolving as we investigate the root cause. We apologize for the interruption.

  5. postmortem Jan 29, 2026, 02:17 AM UTC

    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

Read the full incident report →

Major January 20, 2026 LeafLink Inventory Sync Service Disruption 3m Leaflink

Started Jan 20, 2026, 08:33 PM UTC· resolved Jan 20, 2026, 08:36 PM UTC

  1. investigating Jan 20, 2026, 08:33 PM UTC

    We are investigating an issue with LeafLink inventory sync. No successful syncs detected in the last monitoring window. (Minimum 1 required)

  2. resolved Jan 20, 2026, 08:36 PM UTC

    LeafLink inventory sync is now functioning normally. Detected 4888 successful syncs in the last monitoring window.

Read the full incident report →

Notice January 14, 2026 Flourish Service Disruption 56s Flourish Web

Started Jan 14, 2026, 10:00 PM UTC· resolved Jan 14, 2026, 10:01 PM UTC

  1. investigating Jan 14, 2026, 10:00 PM UTC

    We are investigating reports of service disruption.

  2. resolved Jan 14, 2026, 10:01 PM UTC

    The service has been fully restored.

Read the full incident report →

Major January 14, 2026 LeafLink Inventory Sync Service Disruption 6m Leaflink

Started Jan 14, 2026, 08:44 AM UTC· resolved Jan 14, 2026, 08:50 AM UTC

  1. investigating Jan 14, 2026, 08:44 AM UTC

    We are investigating an issue with LeafLink inventory sync. No successful syncs detected in the last monitoring window. (Minimum 1 required)

  2. resolved Jan 14, 2026, 08:50 AM UTC

    LeafLink inventory sync is now functioning normally. Detected 8771 successful syncs in the last monitoring window.

Read the full incident report →

Notice January 14, 2026 Flourish Service Disruption 57s Flourish Web

Started Jan 14, 2026, 04:35 AM UTC· resolved Jan 14, 2026, 04:36 AM UTC

  1. investigating Jan 14, 2026, 04:35 AM UTC

    We are investigating reports of service disruption.

  2. resolved Jan 14, 2026, 04:36 AM UTC

    The service has been fully restored.

Read the full incident report →

Notice January 9, 2026 Flourish Service Disruption 24m External API

Started Jan 09, 2026, 11:16 PM UTC· resolved Jan 09, 2026, 11:41 PM UTC

  1. investigating Jan 09, 2026, 11:16 PM UTC

    We are investigating reports of service disruption.

  2. resolved Jan 09, 2026, 11:17 PM UTC

    The service has been fully restored.

Read the full incident report →