Flourish Software incident

Application Service Interruption

Resolved after 5 minutes, affecting Flourish Web and Flourish POS, on January 26, 2026.

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

Started
Jan 26, 2026, 10:04 PM UTC
Resolved
Jan 26, 2026, 10:10 PM UTC
Duration
5m
Detected by Pingoru
Jan 26, 2026, 10:04 PM UTC

Affected components

Flourish WebFlourish POS

Update timeline

  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

Your product runs on more than Flourish Software

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →