Oh Dear opens your site every minute. If it does not answer, a second location checks again. Only then do you get an alert.
99.99%
uptime in the last 30 days
One outage of 4 minutes, confirmed from a second location.
Oh Dear calls your endpoint every minute. It checks the status code, the body and the response time. So it catches an API that is broken but still answers 200.
{ "database": "ok", "queue": "ok" }
Oh Dear pings your server every minute. You see whether it answers and how long the answer takes.
14 ms
average round trip
No packets lost.
Oh Dear connects to the ports you name, every minute. You hear when a service such as mail or a database stops accepting connections.
Your app reports its own health on one protected address. Oh Dear reads it every minute. It tells you which part is failing.
Your scheduled job pings Oh Dear each time it runs. When a ping does not arrive on time, you get an alert.
Oh Dear measures how long your page takes to load, on every uptime check. You hear when it gets slower than usual.
Oh Dear runs a Lighthouse report every day. You see when a score drops. You keep six months of reports.
92
Performance
100
Accessibility
96
Best practices
98
SEO
Oh Dear reads your sitemap every day. It checks that the file is valid and that every address in it still works.
410 of 412 addresses work. The file is valid XML.
Oh Dear checks your certificate every 30 minutes. You hear well before it expires. You also hear when the chain your server sends is broken.
23 days
until the certificate expires
Oh Dear crawls your whole site once a day. It lists every page that links to something that no longer works.
Found in a crawl of 412 pages.
Oh Dear reads your DNS records every two hours, from every authoritative nameserver. You see what changed and what it was before.
Oh Dear watches the date your domain expires. It checks more often as that date gets closer. So you never miss the renewal.
41 days
until the domain expires
Oh Dear checks whether your server address is on a blocklist. Being listed means your mail or your site can be blocked.
Oh Dear scans all 65,535 TCP ports of your server once a day. You hear when a port is open that you did not expect.
Expected open
Also open
You describe in plain English what should work. An AI checks it in a real browser. Then it tells you what it found.
“Add a product to the cart. The cart should then show 1 item.”
You decide who hears about a problem and where. Each alert goes to the right people, on the channel they read.
12 channels, including Teams, PagerDuty and webhooks.
A status page shows your visitors what is working right now. It updates itself from your checks. You can also post an update yourself.
Some checkouts are slow. We are looking into it.
Your client gets a report every month. It shows uptime, speed and incidents. Your client can read it without asking you.
Uptime
212 ms
Average response
1
Incident
Past reports stay available.
Your team signs in to Oh Dear through your own identity provider. When someone leaves your company, you remove them once at your provider. That also ends their access to Oh Dear.
Works with Okta, Microsoft Entra ID, Google Workspace and any other SAML 2.0 provider. On every plan.
Oh Dear is a Belgian company. Your monitoring data is stored in Belgium. Every customer can sign a data processing agreement.
Which client site broke, and does the client know?
Did the campaign page stay fast and easy to find?
Is it our network, or the customer's site?
Are the ports, DNS records and certificates still as I left them?
Did the queue and the scheduler actually run?
Can people still check out?
Do customers know we are working on it?
Tell us what you need to monitor. We will say honestly whether Oh Dear fits.
A security update broke There There's network. Nothing on the server could see it. Oh Dear's check from outside told the team in Slack within two minutes.
2 min
to the Slack alert
43 min
until it was fixed
0
customers noticed
Healthy inside. Unreachable outside.
Real outages at real companies. What broke, how Oh Dear spotted it, and how fast the team knew.
“Oh Dear noticed the server was down and told us in Slack within a few minutes, before any customer noticed.”
A list of every check Oh Dear runs, with a page for each one.
Use the API to manage monitors and read results from your own code.
$ curl https://ohdear.app/api/monitors \ -H "Authorization: Bearer $OHDEAR_TOKEN"
Libraries, AI tools and integrations, so you do not have to write the API calls yourself.
$ composer require ohdearapp/ohdear-php-sdk
How to send each alert to the people who need it, on the channel they use.
How to set up a status page and keep your visitors informed during an incident.
Short answers to the questions people ask most often.
Services and tools, built by others, that work with Oh Dear.
Companies and projects that monitor their sites with Oh Dear.
What real outage data says about how often sites go down, and for how long.
Every product update and fix we ship.
How Oh Dear protects your data, from encryption to the servers it runs on.
Email addresses for support, billing and sales.
Earn money by recommending Oh Dear to your audience.
The Oh Dear logo, ready to download for articles and listings.
Availability
Performance & SEO
Site integrity
Incidents and your account
Who it is for
Case studies
Documentation
About Oh Dear
This shouldn't happen - you found a missing page!
We use analytics cookies to understand how our site and app are used. Privacy details.