Live  /  Flutterwave  /  Incident

Flutterwave: Service Alert: Processing Delays on Selected Payment Methods

Flutterwave · flutterwave.comMajor incidentResolved2026-10-29 05:53 UTC
Public — what happened

Summary

Flutterwave said that starting at 22:22 UTC on 28 October 2026, merchants collecting payments through certain channels could see failed or delayed transactions. The affected channels were mobile money and similar options in Ghana, Ivory Coast, Rwanda, Senegal, South Africa, Uganda and Zambia, plus Fawry Pay and OPay. The company said cards, bank transfers and other mobile money options were working normally, and that its engineers were investigating the cause. The incident is marked resolved as of 05:53 on 29 October, though the text provided does not state what caused it.

Affected

Collections APIs

As listed on Flutterwave’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 45, 2026, our weekly internet health report.

The full archive is on the Flutterwave status & history page.

Related: Flutterwave status & history. SquidGrid is not affiliated with Flutterwave.