Uptimus Documentation
Uptimus helps teams verify that websites, APIs and public services are reachable, fast enough and returning the right response.
Start here when you want to understand how a monitor behaves, why a check failed, or how to tune alerts without creating noise.
Popular guides
Uptime settingsFrequency, timeout, redirects and monitoring basics.Request settingsHTTP method, headers, payload and cache-safe requests.Response settingsStatus codes, text, headers and JSON body assertions.NotificationsControl when downtime and performance alerts are sent.
Good defaults
For most production websites:
- Check every 5 minutes or faster if your plan allows it.
- Use
GETunless the endpoint is specifically built for another method. - Accept
2*status codes for normal websites. - Add text or JSON assertions only when the response content matters.
- Use a downtime delay for noisy websites and stricter alerts for critical APIs.