Back to features
Website monitoring
Know your site is down before customers do.
OnlineOrNot checks the important parts of your website every 30 seconds from multiple regions, retries failures before alerting, and tells the right people when something needs attention.
- Feature
- Check every 30 seconds
- Feature
- Verify failures from multiple regions
- Feature
- Verify status codes, SSL, redirects, and page content
- Feature
- Send alerts to chat, on-call, SMS, email, or webhooks
- Monitor more than the homepage.
- A homepage can be fine while checkout, signup, docs, or billing is broken. Put checks on the pages and endpoints that matter to your business.
- Expected status codes
- Keyword checks
- SSL expiry checks
- Reduce false alarms.
- Single-region monitoring can confuse local network trouble for real downtime. OnlineOrNot verifies failures before notifying your team, so alerts are more likely to be worth attention.
- Multi-region checks
- Failure confirmation
- Recovery notifications
- Route failures to the right place.
- Website downtime is not useful as a dashboard badge. It needs to reach the person who can fix it, in the tool they already watch.
- Slack and Discord
- PagerDuty and Opsgenie
- SMS, email, and webhooks
- Grow into deeper monitoring.
- Start with an uptime check, then add API assertions, browser checks, cron monitoring, and a status page when your production workflow needs them.
- API checks
- Browser checks
- Status pages
Frequently asked questions
The short version. The docs have the details when you need them.
- Can I monitor pages behind authentication?
- Yes. You can add headers and request settings for authenticated endpoints, or use browser checks for flows that require a real browser session.
- Can alerts go to Slack or PagerDuty?
- Yes. OnlineOrNot supports chat, SMS, email, on-call tools, and webhooks.
- What should I monitor first?
- Start with your homepage and the paths that affect revenue or signups. Common examples are checkout, login, pricing, docs, billing, and important API health endpoints.
- Does website monitoring replace browser checks?
- No. Use website monitoring for fast HTTP checks. Use browser checks when JavaScript needs to run or a user flow needs to be exercised in Chrome.
Start with website monitoring.
Start with the URL customers notice first, then add deeper checks for the flows that keep your business running.