Measured scope
The status surface checks only explicitly configured HTTP or HTTPS targets. Internal diagnostics and target addresses are not exposed to the browser.
A missing measurement point appears as not monitored and never automatically as available.
State model
Successful 2xx and 3xx responses are reachable. Unexpected 4xx responses appear degraded; 5xx responses, timeouts or unreachable targets appear as outages.
The overall state adopts the most severe observed state among components that are actually monitored.
Cadence and cache
The browser normally refreshes the view every 60 seconds. The server coalesces concurrent requests and briefly caches one result so the status surface does not become a load source itself.
What an origin check does not prove
A successful request confirms reachability and an HTTP response. It proves neither end-to-end delivery nor data integrity, realtime behaviour or the complete user journey.
Production additionally requires an independent monitor outside the primary VENTEX server. Historical availability is never backfilled without evidence.