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 20 (tracked 3d 0h)

Sep 20, 06:21 PM → Sep 23, 06:26 PM · 3d 0h · 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 3d 0h, from Sun, 20 Sep 2026 18:21:01 GMT to Wed, 23 Sep 2026 18:26:46 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3d 0h
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 20, 06:21 PM

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

  2. Sep 22, 03:21 AM

    Status updated: major issue

  3. Sep 22, 06:21 AM

    Status updated: possible issue

  4. Sep 22, 06:26 AM

    Status updated: major issue

  5. Sep 22, 09:21 AM

    Status updated: possible issue

  6. Sep 22, 09:26 AM

    Status updated: major issue

  7. Sep 22, 01:51 PM

    Status updated: possible issue

  8. Sep 22, 01:56 PM

    Status updated: major issue

  9. Sep 22, 06:21 PM

    Status updated: possible issue

  10. Sep 22, 06:26 PM

    Status updated: major issue

  11. Sep 23, 01:56 PM

    Status updated: possible issue

  12. Sep 23, 02:23 PM

    Status updated: major issue

  13. Sep 23, 03:21 PM

    Status updated: possible issue

  14. Sep 23, 03:26 PM

    Status updated: major issue

  15. Sep 23, 06:26 PM

    PulseWatch closed the incident

Official updates

  1. Sep 20, 06:21 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