What does StatusIntel monitor?
StatusIntel monitors websites, APIs, servers, and network services using HTTP, HTTPS, TCP, and ping-style checks.
Do I need a credit card to start?
No. The free plan can be used without a credit card.
Is a 5-minute check interval enough?
It is enough for many public pages and small business websites. Critical login, checkout, and API paths may need a shorter interval when available.
Can I monitor systems I do not own?
No. You should only monitor systems you own or are authorized to monitor.
Why should I monitor more than the homepage?
A homepage can be up while login, checkout, documentation, an API route, or a dependency is broken.
What should my first monitors be?
Start with your homepage, login or conversion path, API health endpoint, SSL-sensitive domain, and public status page. Add TCP checks for operational services only when the monitoring location is allowed to reach them.
What counts as downtime?
For users, downtime means the task cannot be completed. That may be a 500 error, a TLS failure, a timeout, a broken login route, or a page that returns 200 but no useful content. For that reason, status code checks should be paired with keyword or dependency-aware health checks where possible.
How do I reduce false alerts?
Use clear monitor targets, avoid checking routes that intentionally block automated requests, and tune escalation around repeated failures rather than single transient blips. Critical paths can use tighter intervals, while lower-impact pages can tolerate slower confirmation.