You add a target, pick how often it may be checked, and choose where a confirmed incident should go. The fastest interval depends on your plan.
How do you add a check?
Create a workspace and pick a plan. Free allows five monitors and a check every five minutes.
Add an HTTP monitor with the URL, the status codes that count as success, and a timeout.
Add a TLS monitor on the same host if certificate expiry should warn you on its own.
Add a heartbeat monitor for a job. Call the token URL from the job. You can rotate the token; the old hash stops working.
Attach an email, Slack, Discord, or signed webhook so a confirmed incident has somewhere to go.
What does each state mean?
Monitor states
State
Meaning
pending
No confirmed observation yet. A new or resumed monitor starts here.
up
The latest confirmed observation succeeded.
suspect
One failure. Not an incident yet.
down
A second check confirmed the failure. The incident is open.
recovering
Successes have started. It is not up until enough of them arrive.
degraded
Partial trouble: a certificate nearing expiry, or an HTTP check that succeeded but was slower than the threshold you set. A slow response does not open an incident.
maintenance
A maintenance window is active. Probes wait, and this time is left out of uptime.
paused
You paused it. Checks stop until you resume, which returns the monitor to pending.
unknown
No fresh result. UPKira will not call this up.
When does an alert send?
When the incident opens, when it recovers, and when a TLS warning is due. A rule can mute any of those. Quiet hours hold the message until the window ends. The same incident is not sent twice to the same channel: each delivery has a dedupe key.