Solutions
Uptime your users can check themselves
- Web hosting 99.99% · 90 days
- E-mail 100% · 90 days
- DNS 100% · 90 days
- Client portal 99.97% · 90 days
The status page answers before your inbox does
A public status page cuts the 'is it just me?' tickets. Users check it themselves, subscribe to updates, and your support queue stays about your product — not your uptime.
Coverage for the typical stack
HTTP checks on your app and API, SSL expiry warnings before the browser scare, DNS monitoring that catches botched changes. The three failure modes that take small SaaS down, covered in minutes.
Incidents that open themselves
An automation watches your monitors: when something goes down, it opens the incident on the status page and fires your webhook. You find the incident already declared, not a Slack channel asking if the site is up.
A typical SaaS setup
HTTP monitor on the app and on the API health endpoint, SSL monitor on every customer-facing domain, DNS monitor on the apex — grouped into one stack, published as one status page, wired to one automation that opens incidents and posts to your webhook.
Questions
FAQ
How fast will I know about downtime?
The minimum interval is 60 seconds on Pro and 30 seconds on Business. Detection time also depends on where the failure falls between checks, the configured timeout and the incident rule.
Is the status page separate from my SaaS app?
Yes. Qualimonitor hosts it separately, so an outage in the SaaS application does not by itself take down the public status page.
Can incidents be opened automatically?
Yes. Automations react to monitor state: when a monitor goes down, they can open an incident, send e-mail and fire webhooks — no human in the loop at 3 a.m.