Uptime Monitoring
Know when your endpoint goes down—and when it's back.
Setup
Open Sources → Uptime → Add uptime in appkeepr. Enter a name and public URL, pick a channel and optional project, then click Add uptime.
Checks run every 60 seconds with a 10-second timeout. HTTP 200–299 counts as healthy.
Messages
| Observation | Message |
|---|---|
| First failed scheduled check | None |
| Second consecutive failed scheduled check | Down |
| Successful check before Down is confirmed | None |
| First successful check after Down | Back online |
| Further failures while Down, or healthy checks | None |
After the first failure, the status shows Confirming failure while waiting for the next scheduled check. Any successful check clears that pending failure. This filters brief interruptions, such as a deployment that recovers before the next check.
Check now runs an extra check. Its failure does not advance the two scheduled failures needed for Down. A successful manual check clears a pending failure or sends Back online if the endpoint was already confirmed Down.
For a persistent failure, Down is normally confirmed about one to two minutes after the interruption begins, depending on when it starts between checks. Timeouts and queue delays can add time. Two failed checks report two observations; they do not prove that the endpoint was unreachable throughout the time between them.
Pausing and resuming, or changing the URL or check conditions, starts a fresh confirmation sequence. These actions do not send Back online by themselves.
Use the final URL
Redirects aren't followed. Point the check at a public HTTP URL on port 80 or HTTPS URL on port 443, without embedded credentials.