Transport fails
The page cannot be reached or returns a status outside the expected range.
DownStatus, content, regions
Website monitoring for pages that can be up and still be broken.
PageLantern checks public HTTP and HTTPS pages from the locations you choose, verifies status, redirects, content, and latency, then keeps the regional evidence attached to incidents and recovery.
Expected content missing
The response arrives, but the words or selector that prove the page works are absent.
BrokenOne location disagrees
A selected region records a different result while the other checks remain healthy.
Regional signalHTTP contract and location evidence
Check the page customers receive, from the places you choose.
PageLantern combines a practical HTTP contract with scheduled checks from selected locations, so a failure carries both page evidence and geographic context.
Page contract
Define what a useful response means.
- HTTP and HTTPS status expectations
- Redirect, body contains, and body-not-contains checks
- CSS and XPath assertions on paid plans
Monitoring locations
Run the same check from more than one vantage point.
- Up to 12 customer-selected locations
- Independent result and latency per location
- Requested and actual location recorded on fallback
Slot model: Every selected location runs each interval and consumes one monitor slot. The first location drives the monitor summary; the remaining results provide regional evidence. Infrastructure fallback never turns a target failure into a healthy result.
Example result
The page answered, but one region saw the break.
Illustrative values show the HTTP contract and regional evidence without collapsing them into one vague uptime number.
- Target
- shop.example.com
- Locations
- 3
- Expected status
- 200–399
- Content check
- Passed
- Slowest result
- 1,842 ms
- Outcome
- 1 regional failure
Next step
Define the page, choose the locations, keep the proof.
FAQ
Frequently asked questions
Does PageLantern check more than whether my site returns a 200?
Yes. Website monitoring tracks status codes, redirects, response latency, and expected page content, so a 200 response that hides a blank page, a bad deploy, or a broken redirect is still caught.
How am I notified when a page goes down?
A failed check can open an incident and route alerts to email, Slack, Teams, Discord, webhooks, or PagerDuty, and a recovery notice is sent when the page returns to healthy.
Can I monitor a website from more than one location?
Yes. Choose up to 12 locations for an HTTP website monitor. Every selected location runs each interval, records its own result and latency, and consumes one monitor slot.