Skip to content

Outage tracker / Flutterwave

Is Flutterwave down?

Short linkrlup.io/down/flutterwave

I'm having a problem

Vendor lists an old incident, not shown as liveWhat Flutterwave reports

Flutterwave still lists an incident opened on 2026-10-30 with no update since 2026-10-30; we do not show it as live.

As of the last successful poll, 2026-11-05 14:03 UTC.

Flutterwave's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Flutterwave pass from all 4 regions we check.

As of Nov 5, 2026, 2:05 PM UTC, RealUptime's checks of Flutterwave passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:05 PM UTC
US-East617 msChecks passing
US-West967 msChecks passing
Europe924 msChecks passing
Asia-Pacific2792 msChecks passing
their status pagetheir claim, not our reading

Flutterwave reports: Minor incident (“Minor Service Outage”)

from Flutterwave's own status page, checked Nov 5, 2026, 1:06 PM UTC
Flutterwave's status page reports Minor Service Outage. Our checks of Flutterwave currently pass with normal latency. Our checks currently pass from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Flutterwave's own component breakdown, as they publish it

  • Bank Verification Number (BVN)Operational
  • Checkout JSOperational
  • Flutterwave Sign-upOperational
  • Flutterwave WebsiteOperational
  • Merchant StoresOperational
  • Payouts APIsOperational
  • Point of Sale - POSOperational
  • SendAppOperational
  • Windows Server GroupOperational
  • Agency AppOperational
  • Collections APIsOperational
  • Flutterwave APIOperational
  • OTP ServicesOperational
  • SwapOperational
  • DashboardPartial outage
  • SMS serviceOperational
  • TuitionOperational
  • Virtual Account NumbersOperational
  • ServmanOperational
  • USSD CollectionsOperational
  • Virtual CardsOperational
  • Integration TesterOperational
  • SettlementsOperational
  • ChargebacksOperational
  • Bill Payments (Airtime)Operational
  • Bill Payments (Cable TV)Operational

These are Flutterwave's components, named and scored by Flutterwave. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Flutterwave's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Flutterwave response time, by region

US-East
1.8sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.2sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Asia-Pacific
3.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 4.4s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5

Check your own site while you wait on Flutterwave

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Flutterwave. It cannot diagnose Flutterwave's own systems.

What we measured, function by function

Flutterwave answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region

Email me when Flutterwave reports an incident on its status page, and again when it reports it resolved.

Get an email when Flutterwave reports an incident

Email me when Flutterwave reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Flutterwave's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 617msstatus code: 401checked: Nov 5, 2026, 2:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Flutterwave normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 967msstatus code: 401checked: Nov 5, 2026, 2:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Flutterwave normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionFlutterwave is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionFlutterwave is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionFlutterwave is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 924msstatus code: 401checked: Nov 5, 2026, 1:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Flutterwave normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionFlutterwave is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2792msstatus code: 401checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Flutterwave normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionFlutterwave is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionFlutterwave is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Flutterwave, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Flutterwave yet, which is not evidence that nothing is wrong.

Recent probe events

[NGN] Service Restored: Delayed Transaction Notifications on 9PSB Bank PWBT, 10mdeclared on their status page2026-11-05
Service Restored: Email OTP Delivery Delays, 11mdeclared on their status page2026-11-05
Service Restored: Temporary Collections Disruption Across Selected Payment Rails, 1mdeclared on their status page2026-11-04
[KES] Service Restored: Temporary Interruption in Payout Processing, 31mdeclared on their status page2026-11-03
[NGN] Service Restored: Processing Delays on Card Payments, 1mdeclared on their status page2026-11-02
Service Restored: Temporary Interruption in Payment Processing, 1mdeclared on their status page2026-11-02
[KES] Service Restored: Temporary Interruption in Payouts, 24h 23mdeclared on their status page2026-11-02
[NGN] Service Restored: Temporary Interruption in Card Payment Processing, 39mdeclared on their status page2026-10-31

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Flutterwave since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Flutterwave covering any window you pick, with our check readings and Flutterwave's own claim at the time, side by side.

Full check history for Flutterwave: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Flutterwave uptime by RealUptime's checksLive, from this page's own readings.
[![Flutterwave uptime by RealUptime's checks](https://realuptime.io/outages/flutterwave/badge.svg?days=30)](https://realuptime.io/outages/flutterwave)
<a href="https://realuptime.io/outages/flutterwave"><img src="https://realuptime.io/outages/flutterwave/badge.svg?days=30" alt="Flutterwave uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Flutterwave down?", https://realuptime.io/outages/flutterwave. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.flutterwave.com/v3/transactions
secondary
https://flutterwave.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.flutterwave.com

RealUptime is not affiliated with Flutterwave; the name identifies what we checked, and nothing here speaks for Flutterwave's own team. We send a single web request to Flutterwave from 4 regions on our own schedule and time the response. We do not see inside Flutterwave's systems, do not use an account or real transaction, and are not the same signal Flutterwave's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Flutterwave is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Flutterwave operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 2438 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

ANZAbsa GroupAdyenAffirmAfterpay