Flutterwave: SLA evidence report
Flutterwave: SLA evidence report
We only started checking Flutterwave on 2026-11-02, so the window starts there.
We hold no probe record for Flutterwave: we read its status page, so the only incident record here is what Flutterwave declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Flutterwave declared
- 5
- On its own status page, in this window.
- Window
- 2026-11-02 to 2026-11-05
- UTC, 3 days.
Nov 2, 2026, 6:32 AM UTC to Nov 3, 2026, 6:55 AM UTC
[KES] Service Restored: Temporary Interruption in Payouts, impact major
This incident started before the report window shown above.
Nov 3, 2026, 11:23 AM UTC to Nov 3, 2026, 11:54 AM UTC
[KES] Service Restored: Temporary Interruption in Payout Processing, impact major
Nov 5, 2026, 7:56 AM UTC to Nov 5, 2026, 8:07 AM UTC
Service Restored: Email OTP Delivery Delays, impact major
Nov 5, 2026, 1:25 PM UTC to Nov 5, 2026, 1:35 PM UTC
[NGN] Service Restored: Delayed Transaction Notifications on 9PSB Bank PWBT, impact major
Nov 5, 2026, 2:09 PM UTC to still listed as live
[NGN] Service Alert: Intermittent Name Enquiry Failures, impact major
Methodology
These incidents come from Flutterwave's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Flutterwave owes, if any, is decided under its own SLA.