User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Acquired down?
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.
What to try while Acquired is having problems
Estimated fix: Not enough Acquired history yet; similar Money outages lasted 56 min (median, typically 29 min–2 h; 19 outages).
- Avoid repeating payments or trades; check your history first. Cards and ATMs often still work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → acquired.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 198 ms.
Official status
Minor incident
Confirmation of Payee: elevated error rates Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 218 ms | 0 |
| Mon 20 | 0 | 0.0 | 88 ms | 0 |
| Mon 22 | 0 | 0.0 | 293 ms | 0 |
| Tue 00 | 0 | 0.0 | 89 ms | 0 |
| Tue 02 | 0 | 0.0 | 105 ms | 0 |
| Tue 04 | 0 | 0.0 | 88 ms | 0 |
| Tue 06 | 0 | 0.0 | 105 ms | 0 |
| Tue 08 | 0 | 0.0 | 101 ms | 0 |
| Tue 10 | 0 | 0.0 | 329 ms | 0 |
| Tue 12 | 0 | 0.0 | 238 ms | 0 |
| Tue 15 | 0 | 0.0 | 97 ms | 0 |
| Tue 17 | 0 | 0.0 | 207 ms | 0 |
| Tue 19 | 0 | 0.0 | 302 ms | 0 |
| Tue 21 | 0 | 0.0 | 128 ms | 0 |
| Wed 00 | 0 | 0.0 | 109 ms | 0 |
| Wed 02 | 0 | 0.0 | 265 ms | 0 |
| Wed 04 | 0 | 0.0 | 110 ms | 0 |
| Wed 05 | 0 | 0.0 | 152 ms | 0 |
| Wed 07 | 0 | 0.0 | 126 ms | 0 |
| Wed 09 | 0 | 0.0 | 293 ms | 0 |
| Wed 12 | 0 | 0.0 | 73 ms | 0 |
| Wed 14 | 0 | 0.0 | 235 ms | 0 |
| Wed 16 | 0 | 0.0 | 110 ms | 0 |
| Wed 18 | 0 | 0.0 | 80 ms | 0 |
| Wed 20 | 0 | 0.0 | 344 ms | 0 |
| Wed 22 | 0 | 0.0 | 211 ms | 0 |
| Thu 01 | 0 | 0.0 | 204 ms | 0 |
| Thu 03 | 0 | 0.0 | 210 ms | 0 |
| Thu 05 | 0 | 0.0 | 253 ms | 0 |
| Thu 07 | 0 | 0.0 | 158 ms | 0 |
| Thu 09 | 0 | 0.0 | 194 ms | 0 |
| Thu 11 | 0 | 0.0 | 342 ms | 0 |
| Thu 13 | 0 | 0.0 | 154 ms | 0 |
| Thu 15 | 0 | 0.0 | 157 ms | 0 |
| Thu 17 | 0 | 0.0 | 133 ms | 0 |
| Thu 19 | 0 | 0.0 | 202 ms | 0 |
| Thu 20 | 0 | 0.0 | 182 ms | 0 |
| Thu 22 | 0 | 0.0 | 98 ms | 0 |
| Fri 00 | 0 | 0.0 | 130 ms | 0 |
| Fri 02 | 0 | 0.0 | 161 ms | 0 |
| Fri 04 | 0 | 0.0 | 194 ms | 0 |
| Fri 06 | 0 | 0.0 | 173 ms | 0 |
| Fri 08 | 0 | 0.0 | 68 ms | 0 |
| Fri 10 | 0 | 0.0 | 75 ms | 0 |
| Fri 12 | 0 | 0.0 | 235 ms | 0 |
| Fri 14 | 0 | 0.0 | 161 ms | 0 |
| Fri 16 | 0 | 0.0 | 161 ms | 0 |
| Fri 18 | 0 | 0.0 | 198 ms | 0 |
Reliability
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.
Embed this status: free live Acquired badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Acquired yet. Outages of 10 minutes or more get their own page here.
Having trouble with Acquired?
One report per service every 10 minutes from this network. No account.
Follow Acquired
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.
About Acquired
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: 150 ms average, 56–289 ms range across 13 successful checks.
Questions
Is Acquired down right now?
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
When was Acquired last down?
We have not recorded a public Acquired incident since monitoring began 6 days ago.
What is Acquired's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Acquired respond?
150 ms on average over the last 24 hours (56–289 ms).
Does Acquired have an official status page?
Yes, at https://status.acquired.com.
Acquired not working for me but the status is fine. What now?
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.