Flume Outage History

Flume is up right now

Flume had 9 outages in the last 2 years totaling 244h 34m of downtime — averaging 0.4 incidents per month.

There were 9 Flume outages since June 26, 2024 totaling 244h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.flumehealth.com

Minor February 12, 2026

Transaction processing

Detected by Pingoru
Feb 12, 2026, 05:53 PM UTC
Resolved
Feb 12, 2026, 06:40 PM UTC
Duration
47m
Affected: Console & Platform
Timeline · 3 updates
  1. investigating Feb 12, 2026, 05:53 PM UTC

    We are currently investigating an issue causing degraded performance.

  2. investigating Feb 12, 2026, 06:40 PM UTC

    All systems returned to normal operation

  3. resolved Feb 12, 2026, 06:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 30, 2025

Transactions not running

Detected by Pingoru
Oct 30, 2025, 10:33 PM UTC
Resolved
Oct 30, 2025, 10:37 PM UTC
Duration
3m
Affected: Console & Platform
Timeline · 3 updates
  1. identified Oct 30, 2025, 10:33 PM UTC

    Our monitoring systems detected a disruption affecting transaction processing. We’ve identified the issue and deployed a fix, which should be fully restored shortly.

  2. monitoring Oct 30, 2025, 10:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 30, 2025, 10:37 PM UTC

    The incident has been resolved. All systems have returned to normal operation and all transactions will resume processing.

Read the full incident report →

Critical June 12, 2025

Issues accessing the Flume Console & Platform

Detected by Pingoru
Jun 12, 2025, 06:22 PM UTC
Resolved
Jun 12, 2025, 09:25 PM UTC
Duration
3h 2m
Affected: Console & Platform
Timeline · 4 updates
  1. investigating Jun 12, 2025, 06:22 PM UTC

    We're observing issues with application access. We're investigating the cause. Initial indicators suggest that a large degradation of service or outage is impacting many services that run on Google Cloud, AWS, and Cloudflare.

  2. identified Jun 12, 2025, 08:17 PM UTC

    Google Cloud has identified the issue and is rolling out fixes for service recovery.

  3. monitoring Jun 12, 2025, 09:02 PM UTC

    We've observed service recovery but are monitoring errors.

  4. resolved Jun 12, 2025, 09:25 PM UTC

    The recovery is complete and all systems are working as expected.

Read the full incident report →

Minor May 2, 2025

Elevated Transaction Failures

Detected by Pingoru
May 02, 2025, 09:30 PM UTC
Resolved
May 12, 2025, 05:35 PM UTC
Duration
9d 20h
Affected: Console & Platform
Timeline · 3 updates
  1. investigating May 12, 2025, 05:32 PM UTC

    We're experiencing an elevated level of scheduled transaction failures and are currently looking into the issue.

  2. investigating May 12, 2025, 05:33 PM UTC

    We are continuing to investigate this issue.

  3. resolved May 12, 2025, 05:35 PM UTC

    Earlier today we discovered that a subset of scheduled background jobs did not run successfully between early Friday evening and Monday morning. The disruption did not affect application availability or user data. The underlying issue has been corrected and all queued transactions are being re-processed. We are monitoring the system closely and do not expect further impact. Thank you for your patience.

Read the full incident report →

Critical April 4, 2025

Flume Application Down

Detected by Pingoru
Apr 04, 2025, 07:37 PM UTC
Resolved
Apr 04, 2025, 07:58 PM UTC
Duration
20m
Affected: Console & Platform
Timeline · 5 updates
  1. investigating Apr 04, 2025, 07:37 PM UTC

    We are currently investigating the issue.

  2. investigating Apr 04, 2025, 07:37 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 04, 2025, 07:50 PM UTC

    Users are able to log in. Transaction running is currently under review.

  4. investigating Apr 04, 2025, 07:56 PM UTC

    Issue resolved, all services are operating as expected.

  5. resolved Apr 04, 2025, 07:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 20, 2024

Transaction Processing Degraded

Detected by Pingoru
Sep 20, 2024, 11:01 PM UTC
Resolved
Sep 21, 2024, 01:40 AM UTC
Duration
2h 39m
Affected: Console & Platform
Timeline · 3 updates
  1. identified Sep 20, 2024, 11:01 PM UTC

    We are aware of an issue preventing some transactions from processing.

  2. identified Sep 21, 2024, 12:03 AM UTC

    We are in the process of deploying a fix for the issue.

  3. resolved Sep 21, 2024, 01:40 AM UTC

    We’ve observed recovery of the issue.

Read the full incident report →

Minor September 20, 2024

Transactions Halted

Detected by Pingoru
Sep 20, 2024, 07:03 PM UTC
Resolved
Sep 20, 2024, 07:11 PM UTC
Duration
8m
Affected: Console & Platform
Timeline · 2 updates
  1. investigating Sep 20, 2024, 07:03 PM UTC

    We are aware of the issue and it's cause and are working to restore services.

  2. resolved Sep 20, 2024, 07:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 23, 2024

NOT REAL - GCP Iowa Region Down - NOT REAL - BUSINESS CONTINUITY TEST

Detected by Pingoru
Aug 23, 2024, 02:27 PM UTC
Resolved
Aug 23, 2024, 03:38 PM UTC
Duration
1h 11m
Timeline · 4 updates
  1. investigating Aug 23, 2024, 02:27 PM UTC

    We are currently implementing continuity procedures.

  2. investigating Aug 23, 2024, 02:36 PM UTC

    Continuity procedures are ongoing.

  3. investigating Aug 23, 2024, 03:38 PM UTC

    Systems are now operating as normal.

  4. resolved Aug 23, 2024, 03:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 26, 2024

Degrade transaction completion performance

Detected by Pingoru
Jun 26, 2024, 04:55 PM UTC
Resolved
Jun 26, 2024, 05:11 PM UTC
Duration
16m
Affected: Console & Platform
Timeline · 2 updates
  1. monitoring Jun 26, 2024, 04:55 PM UTC

    A fix has been implemented and we are monitoring the results.

  2. resolved Jun 26, 2024, 05:11 PM UTC

    This incident has been resolved.

Read the full incident report →