Flow XO Outage History

Flow XO is up right now

Flow XO had 3 outages in the last 2 years totaling 6h 39m of downtime — averaging 0.1 incidents per month.

There were 3 Flow XO outages since November 18, 2025 totaling 6h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.flowxo.com

Major June 6, 2026

Scheduled Database Upgrade

Detected by Pingoru
Jun 06, 2026, 11:07 PM UTC
Resolved
Jun 07, 2026, 12:24 AM UTC
Duration
1h 17m
Affected: ApplicationMessaging ServersWeb Chat ServersSlack ServersFacebook Messenger
Timeline · 2 updates
  1. scheduled Jun 06, 2026, 11:07 PM UTC

    We will be performing a scheduled database upgrade to improve platform performance and reliability. Flow XO services will be unavailable for the duration of this maintenance window (approximately 2 hours). We will post updates here as work progresses and when services are restored. We apologize for any inconvenience.

  2. in progress Jun 06, 2026, 11:55 PM UTC

    Scheduled database upgrade is now in progress. Flow XO services are offline while we upgrade the production database. We will post updates as work progresses.

Read the full incident report →

Major November 18, 2025

Major Outage

Detected by Pingoru
Nov 18, 2025, 12:19 PM UTC
Resolved
Nov 18, 2025, 02:44 PM UTC
Duration
2h 25m
Affected: ApplicationMessaging ServersWeb Chat ServersSlack ServersFacebook MessengerPublic Website
Timeline · 5 updates
  1. investigating Nov 18, 2025, 12:19 PM UTC

    Our host, Cloudflare, is currently experiencing a major outage and this is causing major downtime for our platform. We will monitor the situation and provide updates as we get them. You can also follow along here (https://www.cloudflarestatus.com/).

  2. investigating Nov 18, 2025, 12:19 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 18, 2025, 01:15 PM UTC

    Identified - The issue has been identified and a fix is being implemented. Nov 18, 2025 - 13:09 UTC

  4. identified Nov 18, 2025, 01:15 PM UTC

    The issue has been identified and a fix is being implemented.

  5. resolved Nov 18, 2025, 02:44 PM UTC

    "Monitoring - A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors"

Read the full incident report →