Getting started with PageLantern
Create your first monitor and get alerted when your website or API goes down — in about two minutes.

Documentation
Guides for every monitor type, every alert channel, the REST API, and the operational states you will see in the product — plus a plain-language glossary.
Create your first monitor and get alerted when your website or API goes down — in about two minutes.
HTTP uptime checks: status codes, content assertions, latency, and how PageLantern identifies itself.
Single and multi-step API checks with JSONPath assertions, variable extraction, and HAR export.
Dead-man’s-switch monitoring for cron jobs and background workers: ping a URL, get alerted when the ping stops.
Catch certificate expiry, hostname mismatches, broken chains, and domain renewal deadlines before a browser warning does it for you.
Verify that records resolve to the values you expect and that public ports are reachable — so routing failures are not mistaken for application failures.
Run a real browser against the flows that matter — login, checkout, search — and keep screenshots, traces and console output as evidence when they break.
Set up every alert channel PageLantern supports, route alerts per monitor, and tune thresholds so the alerts you get are the ones you act on.
The JSON PageLantern posts to your endpoint, the signature header that proves it came from us, and how to verify it.
How incidents open and close automatically, what the lifecycle states mean, and how to run the workflow through to a postmortem.
Hosted public status pages: publishing incidents, maintenance windows, and subscriber updates.
Components, branding, maintenance windows and subscribers — everything beyond publishing the page itself.
What each role can do, how invitations work, and how to give someone access without giving them everything.
Create, scope, rotate and revoke the keys that authenticate programmatic access.
How plan changes are prorated, what a credit balance is, how to cancel, and what happens to your data when you downgrade.
Authentication, conventions, rate limits, and the endpoints for monitors, incidents, status pages and results.
What "Not measured" means, how second-region confirmation works, and how to allowlist our probe.
Plain definitions of uptime monitoring, synthetic monitoring, status pages, heartbeats, SSL expiry, SLA/SLO, error budgets, and related terms.