Uptime monitoring

Know when your website stops being available.

Run scheduled website checks, track response time and keep incident history so downtime is visible as an operational event, not just a failed request.

Free check · No signup required

Scheduled HTTP checksIncident and recovery historyPlan-aware monitoring cadence

Why it matters

Uptime is more useful when it has context.

A website can fail completely, return the wrong HTTP status or become unreliable enough that users experience a problem before anyone on the team notices. Continuous uptime monitoring gives you a repeatable view of availability instead of relying on manual checks.

SiteState records scheduled checks and turns repeated failures and recoveries into website state and incident history. That history matters because the useful question is not only whether a site is down now, but when the issue started, how long it lasted and whether the service recovered cleanly.

What SiteState monitors

Continuous availability monitoring without unnecessary complexity

HTTP availability checks

Monitor HTTP or HTTPS endpoints on a schedule and verify the status codes you expect.

Keyword validation

Optionally confirm required page content is present or detect forbidden content even when the server still returns a successful status code.

Health JSON checks

Validate a JSON health endpoint and compare a configured key with the expected value.

Response-time tracking

Keep TTFB and response timing alongside availability so slow service does not disappear behind a green HTTP status.

Incident lifecycle

Track repeated failures, outage state and recovery so operational history remains understandable after the incident is over.

Status-page publishing

Share current availability and recent incident history through an organization page or a dedicated single-site status page.

Built for real workflows

Uptime monitoring for websites that somebody is responsible for

Client websites

Agencies can monitor production sites continuously and give each client a simple public status URL.

Revenue and lead-generation sites

Keep a history of availability for websites where downtime can interrupt bookings, ecommerce or inbound leads.

APIs and health endpoints

Use HTTP or Health JSON checks for services where a valid response matters as much as basic reachability.

State, not metrics

Uptime is the beginning of website state, not the end.

A site returning HTTP 200 can still be in poor shape. SiteState connects availability with response time, browser performance and regression data so a website can be recognized as degraded before it becomes a complete outage.

That means the same product can answer both operational questions: is the site available, and is the experience getting worse?

Run a real website check

FAQ

Questions people ask before choosing a monitoring tool

How does website uptime monitoring work?

SiteState schedules HTTP checks against configured website targets. It records the outcome, response timing and website state and builds incident history when failures repeat.

Can SiteState verify more than an HTTP 200 response?

Yes. HTTP monitors can use expected status codes and keyword checks, and Health JSON monitors can validate a configured JSON key and expected value.

How often does SiteState check a website?

Monitoring cadence depends on the active SiteState plan and available capacity. The app only offers cadences allowed by the organization's current commercial configuration.