Automatic incident detection, response notes, status updates, and reports so clients see what happened and how fast you reacted.
No card required · 50 monitors free · No time limit
What broke, why, when it started, and how long it took to recover.
Detected15:14:47
Connection timeout after 5000 ms — no HTTP response
Alert sent15:14:49
Slack #client-alerts, Discord ops-room, 3 e-mail recipients
Still down 4 checks15:15:17 — 15:16:47
Retried from the monitoring origin, same result each time
Escalation sent15:19:49
No recovery after 5 minutes — escalated to the on-call rota
Recovered15:22:31
HTTP 200 in 268 ms — the incident closed itself and a recovery alert went out on every channel
Incidents open and resolve themselves from your monitor checks — no setup, no manual bookkeeping. Only reachability failures become incidents; failed keyword and API checks stay separate.
Each feature earns its place by making the client relationship easier to protect: fewer surprises, clearer proof, and faster explanations when something changes.
When a monitor goes down, an incident is automatically created with all relevant context and timestamps.
Each incident opens on the cause — DNS resolution failed, 403 Forbidden, keyword not found — with a plain-language explanation of what that usually means, the timeline in order, and room for notes.
Communicate incidents automatically to your public status page. Keep your users informed without extra effort.
Review the complete timeline after resolution. Analyze response times, downtime duration, and recovery patterns.
Current status, the average over 24 hours, the last check, and seven days of response-time history on one screen. Rebuilt here in markup rather than photographed — the trace draws itself as you scroll it. The workspace is invented; the layout is the one the app draws.
HTTP monitor · checked every 30s
Current status
OPERATIONAL
HTTP 200
Avg. response (24h)
29ms
Fast
Last check
36ms
AVG 24H 29 ms · 2026-08-10 15:23:30
Speed pulse
Last 7 days
Auto-scaled to 145ms · 2488 checks
Concrete moments from the feature: setup, the signal that matters, and the client-facing proof that makes maintenance feel easy and valuable.
Detection · example data
Three consecutive timeouts open an incident with the monitor, the reason and the clock.
Open incidents
1
Trigger
Unreachablecheckout.acmecorp.com
Connection timeout on 3 consecutive checks
Opened
02:41 UTC, on the first failed check of the streak
Public status page
The open incident appears on status.acmecorp.com
Incident detail · example data
Detection, delivery and what a human found, on the same page while it is still happening.
Open for
9 min
Updates
402:41 UTC
Monitor recorded a connection timeout
02:42 UTC
Telegram and e-mail alerts delivered
02:46 UTC
Note: upstream payment provider returning 502
Resolution · example data
The incident closes on recovery with a downtime figure you can defend line by line.
Time to recover
9 min
Incident
Resolved02:50 UTC
checkout.acmecorp.com answered HTTP 200 again
Downtime counted
Reachability failure only, 02:41 to 02:50
Failed checks excluded
Keyword and API policy failures never inflate this number
Add the signal once, then let alerts, history, and reports build automatically.
Once you've set up your monitors, incident management is active.
On downtime, an incident is automatically created.
The cause is the headline. Read the timeline, add a note.
On recovery, the incident is automatically closed with a complete report.
Yes — as soon as a monitor stops being reachable, an incident is opened with the first event, and it closes itself on recovery. A failed check on a site that still answers (a missing keyword, a rejected API response, a certificate warning) shows as an Issue and alerts, but does not open a downtime incident.
Currently, incidents are created automatically based on monitor status. Manual incidents are on our roadmap.
Yes, open incidents are automatically shown on your public status page, keeping your users informed.
Combine uptime, SSL, domains, incidents, alerts, teams, and reports into one maintenance workspace.
An API monitor calls one endpoint with the method, headers, JSON body and auth y…
Push-based heartbeat monitoring for backups, syncs, exports, and scheduled tasks…
A DNS monitor asks a resolver for one record type — A, AAAA, CNAME, MX or TXT — …
A blacklist monitor asks the public DNS blocklists whether an IP address has bee…
Track every client domain expiry date and receive timely warnings before a renew…
A keyword monitor loads one URL and searches the HTML the server returned for a …
Monitor SSL certificates and receive warnings well before they expire, so client…
Give maintenance clients transparency with a professional, automatically updated…
Invite your team, assign roles, and collaborate on monitoring, alerts, and repor…
Fifteen channels: chat, mobile push, on-call paging, or your own webhook. Mainte…
Start with incident management and build client trust with real data. Free, no credit card required.
Create free accountNo card required · 50 monitors free · No time limit