Skip to content
Back to FlutterwaveIncident Postmortem
Flutterwave logo

Flutterwave

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Flutterwave: vendor-reported major incident on September 25 (tracked 15h 20m)

Sep 25, 03:25 PM → Sep 26, 06:46 AM · 15h 20m · high

Flutterwave reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 15h 20m, from Fri, 25 Sep 2026 15:25:18 GMT to Sat, 26 Sep 2026 06:46:10 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
15h 20m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 25, 03:25 PM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 25, 03:25 PM

    Status updated: possible issue

  3. Sep 25, 03:26 PM

    Status updated: major issue

  4. Sep 25, 07:51 PM

    Status updated: possible issue

  5. Sep 25, 07:56 PM

    Status updated: major issue

  6. Sep 25, 10:51 PM

    Status updated: possible issue

  7. Sep 25, 10:56 PM

    Status updated: major issue

  8. Sep 26, 06:46 AM

    PulseWatch closed the incident

Official updates

  1. Sep 25, 03:25 PM

    Flutterwave reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: fallback