Live / Flutterwave / Incident
Flutterwave: Service Alert: BIN Service Disruption – Impact on Card Transactions
Flutterwave · flutterwave.comMajor incidentResolved2026-11-05 20:46 UTC
Public — what happened
Summary
Flutterwave said a problem with its Bank Identification Number (BIN) service, which helps handle card payments, began at 18:15 UTC on 2026-11-05. The company told merchants that card payments might fail or be declined, which could lower the share of successful transactions. It said the matter had been escalated for investigation and that it was working to restore normal service. The incident is marked resolved as of 20:46, though the text provided does not state a cause.
Affected
Collections APIs
Timeline
- Started — 2026-11-05 18:15 UTC
- Identified — 2026-11-05 18:15 UTC
- Resolved — 2026-11-05 20:46 UTC · 2h 32m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Flutterwave against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Flutterwave: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Flutterwave report →
More from Flutterwave
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.