User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Confirmation of Payee: elevated error rates
Source: the vendor's status page · We are not affiliated with Acquired.
Estimated fix: Not enough Acquired history yet; similar Money outages lasted 56 min (median, typically 29 min–2 h; 19 outages).
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.
Reachable from all 4 regions we check from.
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 24 min ago. Last stored result reached it in 132 ms.
Minor incident
Confirmation of Payee: elevated error rates Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 8 | 0 | 0.0 | 107 ms | 0 |
| Nov 8 | 0 | 0.0 | 192 ms | 0 |
| Nov 8 | 0 | 0.0 | 160 ms | 0 |
| Nov 8 | 0 | 0.0 | 70 ms | 0 |
| Nov 9 | 0 | 0.0 | 130 ms | 0 |
| Nov 9 | 0 | 0.0 | 107 ms | 0 |
| Nov 9 | 0 | 0.0 | 188 ms | 0 |
| Nov 9 | 0 | 0.0 | 191 ms | 0 |
| Nov 10 | 0 | 0.0 | 89 ms | 0 |
| Nov 10 | 0 | 0.0 | 105 ms | 0 |
| Nov 10 | 0 | 0.0 | 207 ms | 0 |
| Nov 10 | 0 | 0.0 | 215 ms | 0 |
| Nov 11 | 0 | 0.0 | 110 ms | 0 |
| Nov 11 | 0 | 0.0 | 210 ms | 0 |
| Nov 11 | 0 | 0.0 | 110 ms | 0 |
| Nov 11 | 0 | 0.0 | 149 ms | 0 |
| Nov 12 | 0 | 0.0 | 210 ms | 0 |
| Nov 12 | 0 | 0.0 | 194 ms | 0 |
| Nov 12 | 0 | 0.0 | 156 ms | 0 |
| Nov 12 | 0 | 0.0 | 182 ms | 0 |
| Nov 13 | 0 | 0.0 | 173 ms | 0 |
| Nov 13 | 0 | 0.0 | 72 ms | 0 |
| Nov 13 | 0 | 0.0 | 161 ms | 0 |
| Nov 13 | 0 | 0.0 | 198 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Acquired 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 Acquired goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Acquired alerts to Slack, Discord or a webhook — free.
Acquired is listed in our Money category and checked at acquired.com. Acquired helps businesses convert and retain customers by processing payments intelligently and optimising every aspect of the recurring payments lifecycle.
Acquired publishes an official status page at status.acquired.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 156 ms average, 56–289 ms range across 15 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Confirmation of Payee: elevated error rates
We have not recorded a public Acquired incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
156 ms on average over the last 24 hours (56–289 ms). Latest regional checks: US East 149 ms, US West 291 ms, Europe 121 ms, Asia-Pacific 121 ms.
Yes, at https://status.acquired.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 Acquired here at once, the problem is on Acquired'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 Acquired. 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.