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 1 hr ago. Last stored result reached it in 152 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 140 ms | 0 |
| Mon 20 | 0 | 0.0 | 125 ms | 0 |
| Mon 22 | 0 | 0.0 | 60 ms | 0 |
| Tue 00 | 0 | 0.0 | 64 ms | 0 |
| Tue 02 | 0 | 0.0 | 119 ms | 0 |
| Tue 04 | 0 | 0.0 | 115 ms | 0 |
| Tue 06 | 0 | 0.0 | 145 ms | 0 |
| Tue 08 | 0 | 0.0 | 95 ms | 0 |
| Tue 10 | 0 | 0.0 | 136 ms | 0 |
| Tue 12 | 0 | 0.0 | 88 ms | 0 |
| Tue 15 | 0 | 0.0 | 51 ms | 0 |
| Tue 17 | 0 | 0.0 | 109 ms | 0 |
| Tue 19 | 0 | 0.0 | 140 ms | 0 |
| Tue 21 | 0 | 0.0 | 103 ms | 0 |
| Wed 00 | 0 | 0.0 | 163 ms | 0 |
| Wed 02 | 0 | 0.0 | 191 ms | 0 |
| Wed 04 | 0 | 0.0 | 87 ms | 0 |
| Wed 06 | 0 | 0.0 | 58 ms | 0 |
| Wed 08 | 0 | 0.0 | 133 ms | 0 |
| Wed 11 | 0 | 0.0 | 73 ms | 0 |
| Wed 13 | 0 | 0.0 | 95 ms | 0 |
| Wed 15 | 0 | 0.0 | 90 ms | 0 |
| Wed 17 | 0 | 0.0 | 75 ms | 0 |
| Wed 19 | 0 | 0.0 | 122 ms | 0 |
| Wed 21 | 0 | 0.0 | 179 ms | 0 |
| Thu 00 | 0 | 0.0 | 182 ms | 0 |
| Thu 02 | 0 | 0.0 | 63 ms | 0 |
| Thu 04 | 0 | 0.0 | 47 ms | 0 |
| Thu 06 | 0 | 0.0 | 181 ms | 0 |
| Thu 08 | 0 | 0.0 | 52 ms | 0 |
| Thu 10 | 0 | 0.0 | 105 ms | 0 |
| Thu 12 | 0 | 0.0 | 52 ms | 0 |
| Thu 14 | 0 | 0.0 | 137 ms | 0 |
| Thu 16 | 0 | 0.0 | 183 ms | 0 |
| Thu 18 | 0 | 0.0 | 136 ms | 0 |
| Thu 20 | 0 | 0.0 | 67 ms | 0 |
| Thu 22 | 0 | 0.0 | 92 ms | 0 |
| Fri 00 | 0 | 0.0 | 100 ms | 0 |
| Fri 02 | 0 | 0.0 | 110 ms | 0 |
| Fri 05 | 0 | 0.0 | 57 ms | 0 |
| Fri 07 | 0 | 0.0 | 144 ms | 0 |
| Fri 09 | 0 | 0.0 | 75 ms | 0 |
| Fri 10 | 0 | 0.0 | 64 ms | 0 |
| Fri 11 | 0 | 0.0 | 79 ms | 0 |
| Fri 12 | 0 | 0.0 | 82 ms | 0 |
| Fri 14 | 0 | 0.0 | 61 ms | 0 |
| Fri 16 | 0 | 0.0 | 65 ms | 0 |
| Fri 18 | 0 | 0.0 | 152 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for aplos 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 aplos goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send aplos alerts to Slack, Discord or a webhook — free.
We track aplos (aplos.com) as part of the Money group. Aplos fund accounting software for nonprofits and churches. Track funds and grants, create donor-ready reports, and stay compliant. Try Aplos free.
aplos publishes an official status page at status.aplos.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 89 ms average, 57–152 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 aplos incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
89 ms on average over the last 24 hours (57–152 ms).
Yes, at https://status.aplos.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 aplos here at once, the problem is on aplos'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 aplos. 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.