Built to reduce alert noise.
Group checks by project. One incident per outage. Three alert types, no more.
One alert per incident, not one per failing check
SolidUptime waits until consecutive failures reach your threshold before opening an incident, so transient blips never wake you up. When multiple checks inside a project fail together, they become one incident with one alert.
Scope incidents to what actually broke
Staging noise never hits your production channel. Group checks by service, client, or environment - each project keeps its own alert channels and incident history completely separate.
Three incident alert types. That's the whole list.
Incident started (on by default), escalated (opt-in), resolved (opt-in). Nothing else triggers a notification, ever.
Wake up once per outage, not per state change
Your service recovers at 2:47am. Most monitors send a resolved alert and wake you up a second time. SolidUptime waits 30 minutes of sustained health before resolving - and if it fails again during that window, the clock resets.
Verify your alerts before you need them
Trigger a manual check run and send a test alert from the dashboard. Confirm everything is wired up correctly - without waiting for a real failure to find out it wasn't.
Zero-config TLS expiry tracking
Every HTTPS check automatically captures your cert's expiry date. No separate TLS monitor, no calendar reminder, no manual setup. You'll get one alert at 7 days remaining - early enough to act, not so early it becomes noise.
Webhook alerts - pipe incidents anywhere
SolidUptime POSTs a structured JSON payload to any URL when an incident opens, escalates, or resolves. Works out of the box with Slack, Discord, PagerDuty, or any custom handler. Requests are signed with HMAC-SHA256 so you can verify they're genuine.
Full timeline. Every incident.
Every incident leaves a record: what failed, when, and for how long. Failures are classified - you'll see dns, tls_cert, http_status, body_match, not just "check failed." Average latency is tracked per check so you can spot degradation before it becomes a real problem.
A status page your users can trust
One alert, one place to check. Share a public link so your users can see what's up before they file a support ticket - no login required, always current.
What SolidUptime doesn't do right now
Checks run from a single region. There are no SMS alerts and no multi-region redundancy. If those are hard requirements for you, SolidUptime may not be the right fit yet.
If they're on your wishlist, send an email - what users ask for shapes what gets built next.