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 lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
Estimated fix: Not enough Class 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 36 min ago. Last stored result reached it in 1523 ms.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 18:45 | 0 | 0.0 | 1166 ms | 0 |
| 20:45 | 0 | 0.0 | 1110 ms | 0 |
| 22:45 | 0 | 0.0 | 1436 ms | 0 |
| 23:45 | 0 | 0.0 | 1201 ms | 0 |
| 02:00 | 0 | 0.0 | 1463 ms | 0 |
| 04:00 | 0 | 0.0 | 1173 ms | 0 |
| 06:15 | 0 | 0.0 | 1534 ms | 0 |
| 08:15 | 0 | 0.0 | 1298 ms | 0 |
| 10:30 | 0 | 0.0 | 1515 ms | 0 |
| 11:00 | 0 | 0.0 | 1049 ms | 0 |
| 12:30 | 0 | 0.0 | 1229 ms | 0 |
| 14:30 | 0 | 0.0 | 1242 ms | 0 |
| 14:45 | 0 | 0.0 | 1388 ms | 0 |
| 16:45 | 0 | 0.0 | 1351 ms | 0 |
| 17:00 | 0 | 0.0 | 1523 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 Class 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 Class goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Class alerts to Slack, Discord or a webhook — free.
We track Class (class.com.au) as part of the Money group. Leading wealth accounting solutions for Accountants & Advisers. Increase profitability & deliver better client services. Request a demo today.
Class publishes an official status page at status.class.com.au; 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: 1312 ms average, 1049–1534 ms range across 15 successful checks.
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
We have not recorded a public Class incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1312 ms on average over the last 24 hours (1049–1534 ms). Latest regional checks: US East 1245 ms, US West 1289 ms, Europe 87 ms, Asia-Pacific 310 ms.
Yes, at https://status.class.com.au.
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 Class here at once, the problem is on Class'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 Class. 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.