Stack Pulse Docs
StackPulse

StackPulse Docs

Website Uptime Check

Monitor a public website with a simple GET check and expected 200 response.

A website uptime check verifies that a public page responds quickly with the expected HTTP status.

Basic GET check

Use a stable URL that represents whether the site is available.

text
Name: Marketing site
Method: GET
URL: https://example.com
Expected status: 200
Timeout: 5000 ms

For most websites, GET is the right method because it exercises routing, TLS, edge caching, and origin behavior.

Expected status 200

Use 200 when the page should load normally.

Avoid monitoring pages that commonly redirect, require cookies, or vary by geography unless that behavior is intentional and stable.

Timeout guidance

Start with a timeout between 3000 ms and 5000 ms.

Use a shorter timeout for latency-sensitive production surfaces. Use a longer timeout only when a provider or region is known to have slower cold starts.

Good targets

  • /
  • /status
  • /health
  • A lightweight landing page

Targets to avoid

  • Admin pages.
  • Checkout flows.
  • Pages that require a user session.
  • Pages that make expensive downstream calls on every request.

If a homepage is too heavy, create a small /health endpoint and monitor that instead.