Website monitoring that checks the answer, not just the status code
Request any URL as often as every 30 seconds. Decide what healthy means: a status code, a response time, a string in the body. When the check fails enough times in a row, you hear about it and your status page changes.
Free for one monitor. No card needed.
What HTTPS monitoring is, in plain terms
An HTTPS monitor is a request we send to one of your URLs on a schedule. If the response comes back the way you said it should, the check passes. If not, it fails, and after enough failures in a row we treat the site as down: your team is alerted and, if you have linked the monitor to a status page component, the page reflects it.
Most tools stop at the status code. A 200 that takes nine seconds, or a 200 that says “maintenance mode” in the body, is still a bad experience for your customers. Status Bee lets you check those too, and shows you where the time went so you can tell a slow database from a slow network.
Say what healthy means
Three assertions cover most of what goes wrong. Combine them per monitor. Without any, a 2xx or 3xx response counts as healthy.
- Status code: exactly 200, or whatever your endpoint should return
- Response time: fail if it takes longer than a limit you set, in milliseconds
- Body contains: a word or JSON fragment that only a working page prints
Alerts that fail twice before they wake anyone
Pick how many consecutive failures count as down, and how many passes count as recovered. Then decide what a failure does: mark a component Degraded, draft an incident, or publish one and notify subscribers straight away.
- Team alerts to Slack, Discord, Telegram, Teams, email, SMS or a webhook
- Incidents opened by a rule use the template you chose, so the words are right
- Recovery moves the incident to Monitoring rather than closing it behind your back
Every URL in one list
Marketing site, API health endpoint, webhook receiver, docs. Give each its own interval and assertions, then pause, edit or open an incident without leaving the screen.
- Intervals from 30 seconds to 24 hours, per monitor
- Targets are checked for private addresses, so a monitor can never probe your internal network by mistake
- Redirects followed, bodies capped at 5 MB, one honest user agent
Setting one up
Paste the URL
Anything that starts with http:// or https://. Add a port or a path if you need to.
Choose an interval
Every 30 seconds for the checkout, every 5 minutes for the docs. The plan sets the floor.
Add assertions and a rule
Say what a good response looks like, then link the monitor to a component and decide what a failure should do.
The other checks
HTTPS monitoring questions
Add your first URL. It takes a minute.
One HTTPS monitor and a status page, free. No card needed.