User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
acats.com · AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 2174 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 2642 ms | 0 |
| 03:15 | 0 | 0.0 | 740 ms | 0 |
| 03:30 | 0 | 0.0 | 1524 ms | 0 |
| 03:45 | 0 | 0.0 | 514 ms | 1 |
| 04:00 | 0 | 0.0 | 1344 ms | 0 |
| 04:15 | 0 | 0.0 | 1527 ms | 0 |
| 04:30 | 0 | 0.0 | 675 ms | 0 |
| 04:45 | 0 | 0.0 | 1046 ms | 0 |
| 05:00 | 0 | 0.0 | 1970 ms | 0 |
| 05:15 | 0 | 0.0 | — | 0 |
| 05:30 | 0 | 0.0 | 2260 ms | 0 |
| 05:45 | 0 | 0.0 | 5288 ms | 0 |
| 06:00 | 0 | 0.0 | 1347 ms | 0 |
| 06:15 | 0 | 0.0 | 940 ms | 0 |
| 06:30 | 0 | 0.0 | 1906 ms | 0 |
| 06:45 | 0 | 0.0 | 1591 ms | 0 |
| 07:00 | 0 | 0.0 | 1552 ms | 0 |
| 07:15 | 0 | 0.0 | — | 0 |
| 07:30 | 0 | 0.0 | 1677 ms | 0 |
| 07:45 | 0 | 0.0 | 889 ms | 0 |
| 08:00 | 0 | 0.0 | — | 0 |
| 08:15 | 0 | 0.0 | 2178 ms | 0 |
| 08:30 | 0 | 0.0 | 757 ms | 0 |
| 08:45 | 0 | 0.0 | 1855 ms | 0 |
| 09:00 | 0 | 0.0 | 2933 ms | 0 |
| 09:15 | 0 | 0.0 | 1624 ms | 0 |
| 09:30 | 0 | 0.0 | — | 0 |
| 09:45 | 0 | 0.0 | 4229 ms | 1 |
| 10:00 | 0 | 0.0 | 784 ms | 0 |
| 10:15 | 0 | 0.0 | — | 1 |
| 10:30 | 0 | 0.0 | 2976 ms | 1 |
| 10:45 | 0 | 0.0 | 931 ms | 0 |
| 11:00 | 0 | 0.0 | — | 0 |
| 11:15 | 0 | 0.0 | 693 ms | 1 |
| 11:30 | 0 | 0.0 | 879 ms | 1 |
| 11:45 | 0 | 0.0 | 774 ms | 0 |
| 12:00 | 0 | 0.0 | 1201 ms | 0 |
| 12:15 | 0 | 0.0 | — | 2 |
| 12:30 | 0 | 0.0 | 4686 ms | 0 |
| 12:45 | 0 | 0.0 | 514 ms | 0 |
| 13:00 | 0 | 0.0 | 1503 ms | 0 |
| 13:15 | 0 | 0.0 | — | 1 |
| 13:30 | 0 | 0.0 | 2889 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for ComplianceAlpha 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 ComplianceAlpha goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ComplianceAlpha alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If ComplianceAlpha is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on ComplianceAlpha's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.