There is no status dashboard yet.
A status page that is not driven by real monitoring is theatre. This one says what is actually true instead.
No automated uptime reporting. Not built yet There is no public health endpoint, no incident history and no subscribe-to-updates. Publishing a green tick that nothing verifies would be worse than publishing nothing.
How to tell whether scanning is working
Submit a scan. The system is built so that failure is explicit rather than silent, if the engine is unavailable you get an error saying so, not a fabricated grade. That property is the actual status check.
- "The scanner is offline right now": the engine is unavailable. Nothing was crawled and nothing was scored.
- "Taking longer than expected": the scan was accepted but has not finished inside the polling window. It may still complete.
- A 429. you are rate limited, which is working as designed rather than an outage.
- A result appears: the whole path is healthy, because a result cannot be produced without a crawl behind it.
What is not an outage
- A repeated scan returning yesterday's result. That is the 24-hour domain cooldown.
- Lower coverage than last time. Usually the target site changed, blocked the crawler, or was slower to respond.
- An expired share link. Shared scorecards last 30 days by design.
Reporting a problem
Tell us what you submitted, roughly when, and what came back. If you have the requestId from a
response envelope, include it. Every response carries one and it is the fastest way to find the request in
our logs.