Flume Outage History

Flume is up right now

Flume had 3 outages in the last 2 years totaling 3h 53m of downtime — averaging 0.1 incidents per month.

There were 3 Flume outages since June 12, 2025 totaling 3h 53m 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 →