We started checking Flutterwave on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Flutterwave reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Flutterwave's own status page declared. Below it, any public chatter we saw about Flutterwave and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Flutterwave's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Flutterwave in the last 24 hours, which is not evidence that nothing is wrong.
Flutterwave's status page
[XAF] Service Alert: Orange Cameroon Collections and Payouts Disruption: partial outageService Alert: Multi-Currency Onboarding Unavailable: partial outageService Restored: BIN Service Disruption – Impact on Card Transactions: partial outage[NGN, GHS] Service Alert: Pending Payouts on Flutterwave for Business (F4B): partial outage[NGN] Service Restored: Intermittent Card Transaction Failures: partial outage
[XAF] Service Alert: Orange Cameroon Collections and Payouts Disruption: partial outage, from before this window to now, still open per their page.
Service Alert: Multi-Currency Onboarding Unavailable: partial outage, from before this window to now, still open per their page.
Service Restored: BIN Service Disruption – Impact on Card Transactions: partial outage, from 18:15 UTC to 21:00 UTC.
[NGN, GHS] Service Alert: Pending Payouts on Flutterwave for Business (F4B): partial outage, from 22:15 UTC to now, still open per their page.
[NGN] Service Restored: Intermittent Card Transaction Failures: partial outage, from 06:45 UTC to 07:30 UTC.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Flutterwave's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Flutterwave next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
Confirmation probe13:11 UTC, US-West: our own first failed reading prompted an extra probe. Result: Flutterwave answered normally.
Confirmation probe07:03 UTC, Asia-Pacific: a new incident on their status page prompted an extra probe. Result: Flutterwave answered normally.
Confirmation probe07:03 UTC, US-West: a new incident on their status page prompted an extra probe. Result: Flutterwave answered normally.
Confirmation probe07:02 UTC, US-East: a new incident on their status page prompted an extra probe. Result: Flutterwave answered normally.
Confirmation probe07:02 UTC, Europe: a new incident on their status page prompted an extra probe. Result: Flutterwave answered normally.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.49%
588
US-West
99.11%
447
Europe
100.00%
405
Asia-Pacific
99.60%
248
Their declared record
Flutterwave's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Service Alert: Temporary Disruption to PDF Balance Statement DownloadsOngoing, all systems operational
Nov 6, 2026, 2:16 PM UTC, open for 3h 34m so farinvestigating
their latest update (Nov 6, 2026, 2:16 PM UTC): Dear Valued Merchant,
You may currently be unable to download balance statements in PDF format. This may affect your ability to access or retrieve PDF copies of your account statements. As an alternative, CSV statement downloads remain fully available.
Our technical teams are a…
[NGN] Service Restored: Intermittent Card Transaction FailuresPartial outage
Nov 6, 2026, 6:56 AM UTC to Nov 6, 2026, 7:23 AM UTC (27 min)resolved
their latest update (Nov 6, 2026, 7:23 AM UTC): We are pleased to inform you that the issue with Interswitch impacting card transactions has been successfully resolved.
Thank you for your patience and understanding.
[NGN, GHS] Service Alert: Pending Payouts on Flutterwave for Business (F4B)Ongoing, partial outage
Nov 5, 2026, 10:19 PM UTC, open for 19h 30m so faridentified
their latest update (Nov 6, 2026, 7:09 AM UTC): We are also aware that some GHS transactions are in pending status. Work is in progress to clear the pending payouts.
Service Restored: BIN Service Disruption – Impact on Card TransactionsPartial outage
Nov 5, 2026, 6:15 PM UTC to Nov 5, 2026, 8:46 PM UTC (2h 32m)resolved
their latest update (Nov 5, 2026, 8:46 PM UTC): We are pleased to inform you that the issue with BIN Service (Card Services) and related no traffic on the other rails has been successfully resolved. We can observe traffic on the rails now.
Thank you for your patience and understanding.
[NGN] Service Restored: Intermittent Name Enquiry FailuresPartial outage
Nov 5, 2026, 2:09 PM UTC to Nov 5, 2026, 4:01 PM UTC (1h 52m)resolved
their latest update (Nov 5, 2026, 4:01 PM UTC): The delay in transaction notifications affecting Nuvion Pay With Bank Transfer (PWBT) has been resolved. You can now receive transaction notifications as expected.
We apologize for the disruption to your business operations and appreciate your patience and understanding.
[NGN] Service Restored: Delayed Transaction Notifications on 9PSB Bank PWBTPartial outage
Nov 5, 2026, 1:25 PM UTC to Nov 5, 2026, 1:35 PM UTC (10 min)resolved
their latest update (Nov 5, 2026, 1:35 PM UTC): The delay in transaction notifications affecting 9PSB Bank PayWithBankTransfer (PWBT) has been resolved. You can now receive transaction notifications as expected.
We apologize for the disruption to your business operations and appreciate your patience and understanding.
Service Restored: Email OTP Delivery DelaysPartial outage
Nov 5, 2026, 7:56 AM UTC to Nov 5, 2026, 8:07 AM UTC (11 min)resolved
their latest update (Nov 5, 2026, 8:07 AM UTC): Please note that the issue causing delays in receiving login verification codes (OTPs) via email has been resolved. We are currently monitoring the service to ensure stability.
We apologise for the inconvenience and appreciate your patience and understanding.
Service Restored: Temporary Collections Disruption Across Selected Payment RailsAll systems operational
Nov 4, 2026, 7:57 AM UTC to Nov 4, 2026, 7:57 AM UTC (0 min)resolved
their latest update (Nov 4, 2026, 7:57 AM UTC): Dear Valued Merchant,
Earlier today, you may have experienced temporary disruptions with collections across selected payment rails due to an internal issue. The affected services have since been fully restored, and all impacted collections rails are now operational.
We apologiz…
[KES] Service Restored: Temporary Interruption in Payout ProcessingPartial outage
Nov 3, 2026, 11:23 AM UTC to Nov 3, 2026, 11:54 AM UTC (31 min)resolved
their latest update (Nov 3, 2026, 11:54 AM UTC): We are pleased to confirm that KES payouts are now processing normally following the earlier service disruption.
Our team will continue to monitor closely to ensure payouts remain stable.
We apologize for any inconvenience caused and thank you for your patience and understandin…
[NGN] Service Restored: Processing Delays on Card PaymentsAll systems operational
Nov 2, 2026, 9:42 PM UTC to Nov 2, 2026, 9:42 PM UTC (0 min)resolved
their latest update (Nov 2, 2026, 9:42 PM UTC): Dear Valued Merchant,
You may have experienced delays with some card payments earlier today, with certain transactions remaining pending. Normal card processing has since resumed.
Our team is continuing to monitor the service closely to ensure it remains stable.
We apologize f…
Showing the 10 most recent of 61 incidents Flutterwave has declared in the history we hold.
These entries are Flutterwave's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Flutterwave's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.