Uptimus documentation
Keep every service observable and every response clear.
Practical guides for monitoring, alert delivery, incident response and the integrations that connect your team.
Explore the docs
MonitoringUptime settingsFrequency, timeout, redirects and monitoring basics.RequestsRequest settingsHTTP method, headers, payload and cache-safe requests.ValidationResponse settingsStatus codes, text, headers and JSON body assertions.Incident responsePagerDuty integrationRoute Uptimus incidents to PagerDuty services in US or EU.
A reliable starting point
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.