Source
Features page (uptime monitoring) — Oh Dear
Checked for Oh Dear on 1 Nov 2026
- Page
- https://ohdear.app/features/website-uptime-monitoring
- Checked
- 1 Nov 2026, 10:38 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:2fdc49d30b1ffd934dd9e895382e5d0f8ece83f08ed2970ad809d05233913fd1
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Trial Report an error
“10-DAY FREE TRIAL · NO CREDIT CARD REQUIRED”
-
Model Report an error
“You pay for the number of sites you monitor, not for which checks you switch on.”
-
All plans Report an error
“Uptime monitoring is included on every plan, along with the rest of the website-health toolkit.”
-
Check frequency Report an error
“Cadence. Every minute by default, settable per site from one to sixty minutes.”
-
Failing recheck Report an error
“A monitor that is currently failing is dispatched every minute regardless of that setting.”
-
Locations Report an error
“33 checker servers across 16 cities on six continents.”
-
Verification Report an error
“A failure at the primary location is re-checked from the alternative before anything is raised. Both have to report down for an incident.”
-
Warning state Report an error
“Primary down plus secondary up is a warning, which is recorded but is not downtime and does not affect your uptime percentage.”
-
Down default Report an error
“What counts as down. By default any response outside 2xx, which makes a 204 a success and a 503 an outage.”
-
Redirects Report an error
“Redirects are followed, up to five by default, and the final response is judged.”
-
Timeout Report an error
“Timeout. Five seconds by default, settable from one to ten.”
-
Alert threshold Report an error
“Two minutes of downtime by default, settable from one to twenty.”
-
Content checks Report an error
“Content checks. A required string, a forbidden string, and JSON response assertions.”
-
Http methods Report an error
“The request. GET, POST, PUT or PATCH, with form or raw JSON payloads and your own request headers”
-
History Report an error
“Uptime percentage over the past 7 days and the past 12 months, plus an all-time figure once a monitor is older than a year.”
-
Incident record Report an error
“Each incident keeps its start, end and duration, and each run keeps the response code and the location that saw it.”
-
Notifications Report an error
“Send the outage to the person who owns the fix.”
-
Status page Report an error
“The same checks can feed a status page that updates itself, on your own domain”
-
Status page custom domain Report an error
“Status page custom domain included”
-
Other checks Report an error
“Uptime, performance, certificates, DNS, broken pages and the rest sit on the same site and the same bill.”
Scores citing this record
- The Agency Developer Checks, locations & failure confirmation
- The Customer Support Lead Checks, locations & failure confirmation
- The Customer Support Lead Status pages & incident communication
- The Customer Support Lead Uptime reports, data & the vendor's own reliability
- The E-Commerce Operations Manager Checks, locations & failure confirmation
- The E-Commerce Operations Manager Uptime reports, data & the vendor's own reliability
- The SaaS Platform Engineer Checks, locations & failure confirmation
- The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
- The Information Security Officer Checks, locations & failure confirmation
- The Information Security Officer Uptime reports, data & the vendor's own reliability
- The Skeptic Checks, locations & failure confirmation
- The Skeptic Uptime reports, data & the vendor's own reliability