User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 32 min ago. Last stored result reached it in 1848 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 982 ms | 0 |
| Tue 02 | 0 | 0.0 | 2092 ms | 0 |
| Tue 04 | 0 | 0.0 | 1342 ms | 0 |
| Tue 06 | 0 | 0.0 | 1307 ms | 0 |
| Tue 08 | 0 | 0.0 | 1850 ms | 0 |
| Tue 10 | 0 | 0.0 | 1026 ms | 0 |
| Tue 12 | 0 | 0.0 | 1529 ms | 0 |
| Tue 14 | 0 | 0.0 | 1474 ms | 0 |
| Tue 17 | 0 | 0.0 | 1382 ms | 0 |
| Tue 19 | 0 | 0.0 | 1671 ms | 0 |
| Tue 21 | 0 | 0.0 | 1656 ms | 0 |
| Wed 00 | 0 | 0.0 | 2047 ms | 0 |
| Wed 02 | 0 | 0.0 | 1348 ms | 0 |
| Wed 04 | 0 | 0.0 | 1823 ms | 0 |
| Wed 06 | 0 | 0.0 | 1890 ms | 0 |
| Wed 08 | 0 | 0.0 | 1328 ms | 0 |
| Wed 11 | 0 | 0.0 | 1172 ms | 0 |
| Wed 13 | 0 | 0.0 | 1806 ms | 0 |
| Wed 15 | 0 | 0.0 | 1338 ms | 0 |
| Wed 17 | 0 | 0.0 | 1598 ms | 0 |
| Wed 19 | 0 | 0.0 | 2108 ms | 0 |
| Wed 21 | 0 | 0.0 | 1728 ms | 0 |
| Thu 00 | 0 | 0.0 | 1760 ms | 0 |
| Thu 02 | 0 | 0.0 | 1216 ms | 0 |
| Thu 04 | 0 | 0.0 | 1988 ms | 0 |
| Thu 06 | 0 | 0.0 | 1412 ms | 0 |
| Thu 08 | 0 | 0.0 | 1449 ms | 0 |
| Thu 10 | 0 | 0.0 | 1166 ms | 0 |
| Thu 12 | 0 | 0.0 | 1712 ms | 0 |
| Thu 14 | 0 | 0.0 | 1609 ms | 0 |
| Thu 16 | 0 | 0.0 | 1461 ms | 0 |
| Thu 18 | 0 | 0.0 | 1338 ms | 0 |
| Thu 20 | 0 | 0.0 | 1963 ms | 0 |
| Thu 22 | 0 | 0.0 | 2420 ms | 0 |
| Fri 00 | 0 | 0.0 | 1996 ms | 0 |
| Fri 02 | 0 | 0.0 | 2143 ms | 0 |
| Fri 05 | 0 | 0.0 | 1335 ms | 0 |
| Fri 07 | 0 | 0.0 | 1228 ms | 0 |
| Fri 09 | 0 | 0.0 | 1600 ms | 0 |
| Fri 10 | 0 | 0.0 | 1387 ms | 0 |
| Fri 11 | 0 | 0.0 | 1187 ms | 0 |
| Fri 14 | 0 | 0.0 | 1265 ms | 0 |
| Fri 15 | 0 | 0.0 | 1295 ms | 0 |
| Fri 17 | 0 | 0.0 | 1986 ms | 0 |
| Fri 19 | 0 | 0.0 | 2009 ms | 0 |
| Fri 20 | 0 | 0.0 | 1237 ms | 0 |
| Fri 22 | 0 | 0.0 | 1840 ms | 0 |
| Sat 00 | 0 | 0.0 | 1848 ms | 0 |
98.73% 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for ClearFacts 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 ClearFacts goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ClearFacts alerts to Slack, Discord or a webhook — free.
We track ClearFacts (clearfacts.be) as part of the AI group. CCH Clearfacts: pre-accounting voor accountants en kmo's. AI-boekingsvoorstellen, documenten delen en Peppol-facturatie.
ClearFacts publishes an official status page at status.clearfacts.be; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 98.73% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 1569 ms average, 1187–2143 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ClearFacts incident since monitoring began 7 days ago.
From our own checks: 98.73% over 7 days of checks.
1569 ms on average over the last 24 hours (1187–2143 ms).
Yes, at https://status.clearfacts.be.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report ClearFacts here at once, the problem is on ClearFacts'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 ClearFacts. 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.