Monitoring that explains what happened
Uptime monitor for websites and public services
Choose the check that answers your question: can visitors load the page, can a host respond, or is a certificate still valid? Keep those signals in one workspace.
Choose what “up” means
A successful TCP connection does not prove that checkout works. Use HTTP status and content checks for websites, API assertions for structured responses, and Ping for public host reachability.
From failed check to clear incident
The default confirmation requires two failures before an outage incident. Inspect check results and timestamps, follow alert delivery, and see when a successful check resolves the incident.
Measure what was observed
The dashboard shows recorded-check uptime for 24 hours, seven days and 30 days. Gaps are not counted as successful checks; a short outage between checks may not be observed.
Common questions
Does a monitor guarantee availability?
No. Monitoring observes configured checks from the service location. It cannot prevent outages or see every visitor’s experience.
Can I start with one website?
Yes. Choose Website and enter its public URL. Advanced assertions and notification settings can follow after the first result.