Uptime and the status page

• Every five minutes PageHum sends GET https://your-checked-host/ with the user agent PageHumProbe/1.0 and waits up to 8 seconds.
• Any status below 400 counts as up, redirects included (they are not followed). 4xx, 5xx, a timeout, or no answer counts as a failed check.
• The checked host comes from the first public host that sends a beacon. Change it on the board, next to the site’s name, if the homepage lives elsewhere.
• Each successful check is timed to the first response headers. The board shows the p50 and p75 of the last 7 days, and Performance goes to watch when the p75 is at least twice last week’s and over 600 ms.

• Certificate: about daily, PageHum opens a TLS connection to the checked host the way a browser does and reads the certificate’s expiry, issuer, and whether it verifies. 21 days left is watch; 7 days left, an expired certificate, a name that doesn’t match, a self-signed certificate, or a missing intermediate is a problem.
• Redirects: also daily, it checks that http:// redirects to https://, that https:// reaches a page in at most one redirect, and that www and the bare domain don’t both serve pages. Each is a watch, not a problem.
• Registration: weekly, it reads the domain’s expiry from the registry’s public RDAP record. 30 days left is watch; 7 days left, or lapsed, is a problem. Some country registries publish no expiry date; then the board shows a dash.
• These make up the board’s Domain and certificate reading, which comes right after reachability when the board picks its one problem.

Reachability reads Down when the latest homepage check failed and no visitor has arrived in the last 10 minutes. If visitors are still arriving, the site is reachable for them, so the board says Up and notes the failed check. With no traffic and a good check it reads Quiet, which is not a problem. Before the first check it reads Waiting.

Under the board, Pages checked adds other pages on the same host: a login page, pricing, an /api/health endpoint. Free checks 1 page per site every 30 minutes, Starter 5 every 10, Pro 25 every 5.

• Each check passes when it returns the expected status (200 to 399 unless you set a range, or one exact status), and, if you set them, within a time limit, with a text the page must contain, and without one it must not.
• Requests use GET or HEAD with the user agent PageHumProbe/1.0 and a header X-PageHum-Check: path, an 8-second timeout, and redirects not followed: a failure says where a redirect went. You can add up to five headers, but never credentials; Authorization, cookies, tokens, and keys are refused.
• Two failures in a row make Reachability a problem that names the page, and alert you like an outage: a notification with an AI prompt to investigate, an email on Starter and Pro, and another when it passes again.
• Each page shows its last result, the last 24 hours, and 24-hour and 7-day uptime. Tick Show on the status page to list it there, as up or failing, without the details.

Uptime is the share of successful checks: the last 24 hours on the board, and 24 hours and 7 days on the status page. A run of failed checks becomes an incident with its start, end, and length, closed by the next good check. Uptime is rounded down, so a single failed check never shows as 100%.

• Calendar: one cell per day over the board’s range, up to 90 days, coloured by the share of checks that passed: all, 99% or more, 95 to 99%, or under 95%. Hover, tap, or use the arrow keys for the day’s figure and its outages; “Show every day” lists them all. Days are counted from October 11, 2026, plus the week of checks before it.
• Outages: a lane each for the homepage, any checked page, and any failing flow, with a bar for each outage across the range and a list beneath. Homepage incidents are kept 90 days.
• Server response time: the median and p95 of how long the homepage check waited for an answer, by day.

Every site has a status page at pagehum.com/status/your-site-key, on every plan and without a login. It shows the current state, 24-hour and 7-day uptime, recent incidents, and the last check. Share it from the board with Share status page. It shows honest intervals from five-minute checks, not a second-by-second promise, and carries no partner promotion. See the demo’s status page.

Tick Show this calendar on the public status page under Uptime over time on the board to add the last 90 days of homepage uptime to it, as far back as your plan keeps days.