Real boundary checks
Health and readiness endpoints, identity authorities, the public site, and unauthenticated request rejection are checked directly. A running process alone does not count as proof.
Production status
Evidence from the outside in.
Independent checks test the public site, APIs, sign-in redirects, and request gateway that customers use. The status does not depend on a person marking the service healthy.
Gateway APIAwaiting evidence
IdentityAwaiting evidence
Operations APIAwaiting evidence
Public websiteAwaiting evidence
Request boundaryAwaiting evidence
Durable alerting
Repeated slowdowns, failed monitors, missing heartbeats, and exhausted retries raise separate alarms. Recovery sends another notice.
Safe public evidence
The public artifact contains component state, observation time, and latency only. It excludes URLs, provider responses, tenant data, request bodies, and internal identifiers.
Scope and assurance
Availability is one layer of reliability.
These checks complement application alarms and release tests. Customer agreements define uptime, support targets, data location, and any special deployment terms.