User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 48 min ago. Last stored result reached it in 96 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 182 ms | 0 |
| Mon 22 | 0 | 0.0 | 119 ms | 0 |
| Tue 00 | 0 | 0.0 | 110 ms | 0 |
| Tue 02 | 0 | 0.0 | 155 ms | 0 |
| Tue 04 | 0 | 0.0 | 108 ms | 0 |
| Tue 06 | 0 | 0.0 | 185 ms | 0 |
| Tue 08 | 0 | 0.0 | 125 ms | 0 |
| Tue 10 | 0 | 0.0 | 150 ms | 0 |
| Tue 13 | 0 | 0.0 | 115 ms | 0 |
| Tue 15 | 0 | 0.0 | 104 ms | 0 |
| Tue 17 | 0 | 0.0 | 82 ms | 0 |
| Tue 19 | 0 | 0.0 | 186 ms | 0 |
| Tue 22 | 0 | 0.0 | 86 ms | 0 |
| Wed 00 | 0 | 0.0 | 147 ms | 0 |
| Wed 02 | 0 | 0.0 | 110 ms | 0 |
| Wed 04 | 0 | 0.0 | 193 ms | 0 |
| Wed 06 | 0 | 0.0 | 160 ms | 0 |
| Wed 09 | 0 | 0.0 | 68 ms | 0 |
| Wed 11 | 0 | 0.0 | 183 ms | 0 |
| Wed 13 | 0 | 0.0 | 149 ms | 0 |
| Wed 15 | 0 | 0.0 | 108 ms | 0 |
| Wed 17 | 0 | 0.0 | 107 ms | 0 |
| Wed 20 | 0 | 0.0 | 218 ms | 0 |
| Wed 22 | 0 | 0.0 | 141 ms | 0 |
| Thu 00 | 0 | 0.0 | 95 ms | 0 |
| Thu 02 | 0 | 0.0 | 169 ms | 0 |
| Thu 04 | 0 | 0.0 | 342 ms | 0 |
| Thu 06 | 0 | 0.0 | 142 ms | 0 |
| Thu 08 | 0 | 0.0 | 88 ms | 0 |
| Thu 10 | 0 | 0.0 | 117 ms | 0 |
| Thu 12 | 0 | 0.0 | 101 ms | 0 |
| Thu 14 | 0 | 0.0 | 77 ms | 0 |
| Thu 16 | 0 | 0.0 | 102 ms | 0 |
| Thu 19 | 0 | 0.0 | 151 ms | 0 |
| Thu 21 | 0 | 0.0 | 133 ms | 0 |
| Thu 23 | 0 | 0.0 | 95 ms | 0 |
| Fri 01 | 0 | 0.0 | 99 ms | 0 |
| Fri 03 | 0 | 0.0 | 104 ms | 0 |
| Fri 05 | 0 | 0.0 | 180 ms | 0 |
| Fri 07 | 0 | 0.0 | 131 ms | 0 |
| Fri 09 | 0 | 0.0 | 239 ms | 0 |
| Fri 11 | 0 | 0.0 | 206 ms | 0 |
| Fri 13 | 0 | 0.0 | 145 ms | 0 |
| Fri 15 | 0 | 0.0 | 53 ms | 0 |
| Fri 17 | 0 | 0.0 | 114 ms | 0 |
| Fri 19 | 0 | 0.0 | 122 ms | 0 |
| Fri 20 | 0 | 0.0 | 94 ms | 0 |
| Fri 22 | 0 | 0.0 | 96 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Fluid Pay yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Fluid Pay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fluid Pay alerts to Slack, Discord or a webhook — free.
Fluid Pay, at fluidpay.com, is one of the Money services we monitor. A payment gateway built for ISOs, ISVs and agent groups. Card-present, ecommerce and recurring on one API. Partner-only since 2017, and we have never boarded a merchant ourselves.
Fluid Pay publishes an official status page at status.fluidpay.com; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 126 ms average, 53–239 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Fluid Pay incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
126 ms on average over the last 24 hours (53–239 ms).
Yes, at https://status.fluidpay.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Fluid Pay here at once, the problem is on Fluid Pay's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Fluid Pay. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.