Statflo Outage History

Statflo is up right now

Pingoru has recorded 40 incidents for Statflo: 2 in the last 12 months and 1 in the last 90 days.

Source: status.statflo.com

40incidents recorded
2last 12 months
1last 90 days
8 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Statflo in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202610 of 720 (0%)
October 202600 of 533 (0%)

Incidents, newest first

Notice September 21, 2026 The Statflo app is down for some users - Issue under investigation / L'application Statflo ne fonctionne pas pour certains utilisateurs - Investigation en cours –

Started Sep 21, 2026, 07:00 PM UTC· resolved Sep 21, 2026, 07:00 PM UTC

  1. resolved Sep 21, 2026, 07:11 PM UTC

    It has come to our attention that the Statflo app was down for some users. Our team has investigated and solved the incident. ----------------- Nous avons été informés que l'application Statflo était indisponible pour certains utilisateurs. Notre équipe a mené une enquête et résolu le problème.

Read the full incident report →

Major May 6, 2025 Most Customers cannot access Campaigns 7h Conversation Platform, Statflo Application

Started May 06, 2025, 12:47 PM UTC· resolved May 06, 2025, 07:47 PM UTC

  1. investigating May 06, 2025, 12:47 PM UTC

    We have identified an issue affecting most Customers, which is preventing them from accessing Campaigns.

  2. identified May 06, 2025, 12:48 PM UTC

    We have identified the cause of the issue, and are working on a solution to restore access to Campaigns.

  3. identified May 06, 2025, 01:49 PM UTC

    We are making progress towards restoring the full functionality of the app and expect Campaigns will be accessible again within 30 minutes.

  4. identified May 06, 2025, 02:25 PM UTC

    We are continuing to make progress toward full restoration. However, additional time is needed. We now expect Campaigns to be accessible again within the next 90 minutes. We appreciate your patience as we work to resolve this issue.

  5. identified May 06, 2025, 03:17 PM UTC

    We remain on track to restore access to Campaigns by noon ET. Once resolved, we’ll address downstream impacts, including updating reports. In the meantime, we recommend affected users wait until the issue is fully resolved before logging back in. Thank you for your continued patience and understanding.

  6. identified May 06, 2025, 03:45 PM UTC

    Good news: Campaigns are fully accessible, and all users are welcome to log in again. We've started to address downstream impacts, including updating reports.

  7. monitoring May 06, 2025, 04:08 PM UTC

    In-app reports are updating again. We are monitoring the situation and will tackle any downstream impact.

  8. resolved May 06, 2025, 07:47 PM UTC

    After monitoring the situation over the past four hours, we can confirm the incident was fully resolved as of our last update. Thank you for your patience and understanding throughout.

Read the full incident report →

Critical February 25, 2025 The Statflo app is down - Issue under investigation / Problème technique: App Statflo - Investigation en cours 1m Conversation Platform, Statflo Application

Started Feb 25, 2025, 04:12 PM UTC· resolved Feb 25, 2025, 04:13 PM UTC

  1. identified Feb 25, 2025, 04:12 PM UTC

    It has come to our attention that our app is down. Our team has identified the issue and will provide an update once we’ve identified a potential solution. ----------------- Nous avons appris que notre application était en panne. Notre équipe a identifié le problème et fournira une mise à jour dès que nous aurons trouvé une solution potentielle.

  2. resolved Feb 25, 2025, 04:13 PM UTC

    This incident has been resolved ----------------- Cet incident a été résolu

Read the full incident report →