Detection
The monitor records the failure.
Oh Dear's uptime monitoring watches the site from outside your stack and records the incident. Other checks stay separate from the status page.
- Bitmovin
- HBO Nordic
- Obsidian
- Laravel
- Fathom Analytics
- PHP 8
- Stanford University
- Takeaway.com
- IGN
- VRT NWS
- spatie
Monitoring and communication
The monitor finds the problem. The status page explains it.
A status page is not a check and not an SLA. It turns selected monitor results and your own updates into a public record people can read while your team fixes the incident.
Communication
The page publishes what you choose to share.
Automatic updates report the monitor state. Your own messages add the cause, the recovery work and when the next update will come.
Automatic evidence, human context
Choose what posts automatically and what needs a human.
By default, Oh Dear posts when a connected uptime monitor goes down and when it recovers, with a message you configure. Turn that off if your team wants to approve every post. Publish updates from the dashboard or the API, use saved templates, and mark incidents resolved.
Incident timeline
Illustrative
-
Website appears to be down.
Posted from the connected uptime monitor.
Automatic -
Hosting issue confirmed
We found a problem at our hosting provider. The team is moving traffic and will post another update in 20 minutes.
Manual update -
Service restored
Traffic is back to normal. We are watching the site for further errors.
Resolved
It took me 5 minutes to set up a status page for @FilmmusicDB and it just works.
Marcus Stöhr, Senior software developer
The first update can post itself while your team works out the cause.
Built for a client roster
Give every client a page. Keep one portfolio view for your team.
Create as many status pages as you need. Put one monitored site on a page, group related sites, or show the whole portfolio on an internal dashboard.
Your status pages
Client One
1 monitor
Client Two
3 monitors
Agency dashboard
All monitors
Make each page belong to the client.
Use a custom domain, logo, favicon and colors. Turn on more than one language when the audience needs translated incident updates.
- Domain. status.example.com
- Languages. English and Dutch, or any of 25 languages
- Uptime history. 60 days per monitor
- Access. Public, or behind a secret URL
Choose the failure boundary
Put the status page on a domain that still works during the outage.
A status subdomain is quick to set up, but it shares the main domain's DNS. Use a separate domain when the status page should keep working if that DNS fails.
Two valid domain choices
Illustrative domains
Status subdomain
Example
status.client.example
Setup
CNAME to status.ssl.ohdear.app
Dependency
Shares the DNS of the main domain
Separate status domain
Example
status.clientstatus.example
Setup
CNAME to status.ssl.ohdear.app, at a separate DNS provider
Dependency
Keeps working when the main domain's DNS fails
Oh Dear issues the certificate for either one. Read the custom domain guide.
Updates without refreshing
Let people follow the incident where they already look.
Visitors can subscribe by email, Slack or RSS. The same status data is available as JSON and XML for systems that need it.
Email confirmations and updates
Slack channel updates
RSS feed
JSON and XML output
A team can have 500 confirmed email subscribers by default. Contact support when you need more.
No feature tiers
Every check.
Every plan.
Status pages are on every Oh Dear plan. You pay for the number of sites you monitor, not for the tools you use to talk to customers.
Start with everything on.
Create the pages you need and connect the monitors you choose.
- Unlimited status pages
- Custom domains and branding
- Automatic and manual updates
- Every monitoring feature included
10-day free trial. No credit card.
Before you publish
Questions about public status pages.
What the page shows, how updates work, and which choices stay yours.
What is a public status page?
A public status page gives customers and clients one place to see the state of your services and read incident updates. Oh Dear hosts the page separately from the monitored site, and you choose which monitors appear on it.
Does an Oh Dear status page update automatically?
Yes. Automatic updates are on by default: when a connected uptime monitor goes down or recovers, Oh Dear posts the message you configured. Turn them off if you want to approve every post, and publish updates yourself from the dashboard or through the API.
How many status pages can I create?
As many as you need. An agency can create one page per client, group selected monitors on a page, or use one page as a portfolio dashboard.
Can I use my own domain?
Yes. Point a CNAME record for your status domain to status.ssl.ohdear.app, and Oh Dear issues the certificate. A status subdomain can share the main domain's DNS failure, so a domain with separate DNS is safer when that matters. Read the custom domain guide.
Can I match the page to my brand and language?
Yes. Add your logo and favicon, choose the colors for light and dark mode, and turn on more than one language. With several languages active, visitors pick one and your team translates each update.
Can I keep a status page private?
Status pages are public by default. You can add a secret that must be in the page URL, but that secret is not a login and not per-user access control.
How can people subscribe to updates?
Visitors can subscribe by email, Slack or RSS, and systems can read the page as JSON or XML. A team can have 500 confirmed email subscribers by default, and support can raise that limit.
How much uptime history does the page show?
60 days per monitor by default. You can turn the history off, or change the thresholds that make a day green, orange or red.
Are status pages included on every plan?
Yes. Status pages are on every Oh Dear plan. There is no separate status page subscription to buy.
Get started
Start monitoring the sites your clients ask about.
Set up a branded status page and connect the monitors you choose. Every feature on. No credit card.
