Reading an alert
Every alert opens with one plain sentence and the first thing to try. The technical details come after that, for you or whoever looks after your website. Here is exactly what one looks like. The website and time are examples; everything else is the real wording.
A problem alert
Subject: PageNora: problem confirmed on example-clinic.com/book
From: PageNora alerts (sent from mail.pagenora.net)
PageNora — Website monitoring
This page returned an error instead of loading.
What to try first: Check this page and its hosting.
Technical details (for you or your web developer)
Website: https://example-clinic.com/book
Issue: Page returned an HTTP error
Status: open
Severity: HIGH
Expected: HTTP < 400
Observed: 404
Suggested action: Check this page and its hosting.
Confirmed at: Oct 20, 2026, 5:00 PM EDT (UTC: 2026-10-20 21:00)
How it was checked: an HTTP request (no browser was used).
Verification: confirmed by two separate checks.
Impact: this may affect visitors; lost revenue has not been measured.
Scope: public-page checks only; forms and checkout were not submitted.
Why is there only one email? PageNora only emails you after a second check has agreed with the first. This is the first and only message about this problem until it is fixed. You will not get a “first warning” before it.
The technical details, line by line
- Website: the exact page that was checked.
- Issue: the kind of problem, in plain words. Every issue type and how to fix it is listed.
- Status: open means the problem is happening; resolved means it is confirmed gone.
- Severity: HIGH means visitors may not be able to use the page or reach you. MEDIUM means something you approved has changed or is getting close to a limit. INFO is used for recovery messages.
- Expected / Observed: what you approved against what PageNora actually saw. These two lines are your evidence: copy them to whoever fixes the site.
- Suggested action: a first thing to try. It is a starting point, not a diagnosis.
- Confirmed at: the time of the second, confirming check, in the time zone saved for your account, with the UTC time (the world time standard) in brackets. If no time zone is saved, it is shown in UTC alone. You can set yours under Settings › Time zone for alert emails.
- How it was checked: “an HTTP request” means PageNora asked the server for the page; “the page HTML” means it read the page’s code. No browser check is used.
- Impact and Scope: these lines are deliberately modest. PageNora cannot see your sales, so it does not claim to know what a problem cost you, and it never submits your forms or tests checkout.
A recovery alert
Subject: PageNora: recovery confirmed on example-clinic.com/book
PageNora — Website monitoring
Good news: PageNora confirmed this problem is fixed.
It was: this page returned an error instead of loading.
Technical details (for you or your web developer)
Website: https://example-clinic.com/book
Issue: Page returned an HTTP error
Status: resolved
Severity: INFO
Expected: Previously reported issue absent on two checks
Observed: Recovery reconfirmed
Suggested action: Review the recovery and incident history.
Confirmed at: Oct 20, 2026, 9:30 PM EDT (UTC: 2026-10-21 01:30)
How it was checked: an HTTP request (no browser was used).
Verification: confirmed by two separate checks.
Scope: public-page checks only; forms and checkout were not submitted.
A recovery message means two healthy checks in a row. While a problem is open PageNora looks again every 5 minutes for the first half hour, then every 15 minutes, then hourly. So if you fix the page soon after the alert, expect the recovery email within about 10 to 20 minutes; if the problem has been open for many hours, it can take up to an hour or two.
What you will not get
- No emails about one-off blips. A problem has to show up twice.
- No repeat emails while a problem stays open. One message when it opens and one when it closes.
- No alerts when PageNora itself cannot tell. Those are marked “unknown” and are explained in Troubleshooting.
If an alert does not match what you see on your site, see Troubleshooting or use the contact form with the alert pasted in.