Uptime monitoring
When your site goes down,know before your customers do.
We check your site at regular intervals. If it stops responding, its IP changes, Cloudflare protection is removed or the certificate is about to expire, you get an email and a Slack message.
Sample view · fictional domains
| Site | Status | Response | In front | Certificate |
|---|---|---|---|---|
| kuzey-yazilim.example | Up | 212 ms | Cloudflare | 61 days |
| panel.kuzey-yazilim.example | Up | 148 ms | direct | 12 days |
| anadolu-lojistik.example | Unreachable · since 03:12 | — | Cloudflare | 203 days |
- anadolu-lojistik.example
Unreachable · 503 - anadolu-lojistik.example
Cloudflare proxy removed — origin IP exposed - anadolu-lojistik.example
Back up · ~14 min
We watch five things
01
Outage
If two checks in a row get no answer, we call it unreachable. A single hiccup never wakes you up.
02
Recovery
We also tell you when the site is back and how many minutes the outage lasted.
03
IP change
If your domain starts pointing to another server, you know: a planned move, or did someone touch your DNS?
04
Cloudflare protection removed
If the orange cloud is switched off, your real server IP is exposed. Don't let an attacker notice first.
05
Certificate expiry
We warn once when 14 days are left, so you renew before browsers say “not secure”.
We read sites behind Cloudflare correctly
Ordinary monitors don't understand Cloudflare: they raise false alarms on IP changes or mistake the security page for an outage. We read it with four rules.
- The visible IP is Cloudflare's
- So we don't report IP changes; your server didn't change.
- We report when protection is removed
- That is what matters: your real IP is now public.
- A challenge page is not an outage
- If a firewall stops us we say “blocked”, not “down”.
- 52x is a real outage
- When Cloudflare says it can't reach the server, visitors can't either; we alert you.
The same rules apply to Akamai, Imperva, CloudFront, Sucuri and Fastly.
How you hear about it
Outage, recovery and Cloudflare protection removal go instantly to your email and, if connected, your Slack, Teams or Discord channel. IP and certificate events land in notifications and the daily digest.
example.com · site unreachable
example.com did not respond in two consecutive checks (503). Check the server, DNS or certificate.
Open monitoring
How many sites, how often
| Plan | Sites | Check interval |
|---|---|---|
| Free | 1 | every 30 minutes |
| Pro | 10 | every 5 minutes |
| Team | 50 | every 5 minutes |
Outage emails are sent instantly on every plan.
What we don't do
- No port scanning or attack attempts; a check is a single page request.
- No browser impersonation; we identify ourselves as NoroxiMonitor.
- We don't store your page content; only status code, timing and headers.
- We don't monitor government domains.
Questions
- Does it load my server?
- No. One request per check: 2 an hour on Free, 12 an hour on Pro.
- Why wait for two checks?
- To avoid false alarms from momentary network hiccups. If the second check also fails, the alert goes out.
- Do I need to verify ownership?
- No. We send a single request to a public page, the same anyone can make.
- Is Slack required?
- No. Email is on for every account; add Slack, Teams or Discord under Settings → Notification channels.
Add your first site in two minutes
Create an account, type the domain. The first check runs immediately.