Topolo Status
Public overview of the Topolo status page and production health monitoring surface.
What It Is
Topolo Status is the public status page for Topolo production surface health.
Architecture
The Status Worker serves the public page, exposes read-only health data, runs scheduled production probes, records status history in D1, and alerts operators when repeated probe failures cross the configured threshold.
Runtime Surfaces
See /systems/topolo-status for the current host, Worker, and service metadata.
API Reference
The public Status API is read-only and centered on status-page rendering and the /api/health healthcheck.
Auth and Permissions
The status surface is public and read-only. Operational changes are made through source control and CloudControl-managed deployment credentials, not through a user workspace session.
Data Ownership
Topolo Status owns status incidents, probe history, and aggregate production-health telemetry. It does not own the downstream product data for the services it monitors.
Deployments
Topolo Status deploys as the production topolo-status Worker serving https://status.topolo.app.
Failure Modes
- monitored endpoint outage, DNS failure, or false positive
- D1 write failure for probe history
- alert webhook delivery failure
- route or Worker deployment drift
Debugging
Start with /systems/topolo-status, then check https://status.topolo.app/api/health, Worker logs, and recent status-history rows for the affected probe target.
Change Log / Verification
- Added public application coverage on 2026-06-28 so the public Status system no longer relies only on internal handbook coverage.
- Centralized Status app identity metadata on 2026-05-13 so runtime and CloudControl config no longer carry concrete app ids.
- Added canonical system coverage on 2026-05-02 from the CloudControl manifest and package metadata so the Docs registry covers the public status and monitoring Worker.