Is Flutterwave down in the US?
Vendor reports an incidentWhat Flutterwave reports
Flutterwave reports an incident on its status page: [NGN] Service Alert: Intermittent Name Enquiry Failures.
Impact: major. Since 2026-11-05 14:09 UTC.
Latest update, 2026-11-05 14:09 UTC: Dear Valued Merchant, We are experiencing intermittent Name Enquiry failures affecting Nuvion Pay With Bank Transfer (PWBT) transactions. This may prevent some customers from successfully completing bank transfer payments, potentially disrupting your payment collection operations. Our team is actively working to resolve the issue and restore normal service. We will provide updates as progress is made. We apologize for the disruption to your operations and appreciate your patience and understanding.
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 passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Flutterwave at Nov 5, 2026, 2:26 PM UTC.
Over the last 24 hours we completed 253 checks from Ashburn and San Jose and 253 answered cleanly, 100.00% availability.
Of the 2 other regions we check Flutterwave from, all 2 read checks passing right now.
Email me when Flutterwave reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 2:26 PM UTC.
Flutterwave from Ashburn and San Jose over the last 30 days
Over the last 30 days, Flutterwave answered our Ashburn probe in 1,012 ms on average, and 1 check in 20 took longer than 1,732 ms.
Over the last 30 days, Flutterwave answered our San Jose probe in 1,306 ms on average, and 1 check in 20 took longer than 2,016 ms.
Ranked by average response time across the 4 cities we check Flutterwave from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 803 ms and Tokyo slowest at 1,934 ms.
From Ashburn and San Jose we ran 746 checks of Flutterwave in 4 days, and 741 answered cleanly: 99.32% availability.
2 of the 4 days had at least one failed check. The weakest was Nov 2 (UTC), at 96.19% across 105 checks.
In Ashburn local time (EST), Flutterwave was slowest around 3 PM, at 1,429 ms on average over the last 14 days, and quickest around 5 PM, at 751 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 148 | 100.00% | 1,076 ms |
| Wed, Nov 4 | 248 | 100.00% | 962 ms |
| Tue, Nov 3 | 245 | 99.59% | 1,235 ms |
| Mon, Nov 2 | 105 | 96.19% | 1,423 ms |
Flutterwave outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Flutterwave outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Flutterwave from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 98 checks |
| Tokyo | Checks passing | 98.36% of 61 checks |
Other countries we check Flutterwave from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Flutterwave's public endpoints. They are not user reports, and they are not Flutterwave's own status page.
See Flutterwave's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Flutterwave has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
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 serversRun 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