Monitors
Check settings
Intervals, thresholds, timeouts, headers, and how status is decided.
- Check interval
- How often the check runs: 30 seconds to 1 hour, down to your plan's minimum.
- Expected status
- The HTTP status code that counts as up (default
200). Anything else fails the check. Website and API monitors only. - Degraded threshold
- Responses slower than this (default
1500ms) count as slow. The monitor turns degraded only after two consecutive slow checks, so a single network blip never flips the status. - Timeout
- How long to wait before giving up, 1 to 120 seconds (default 30). A timeout counts as a failed check.
- Down after
- A monitor goes down after two consecutive failed checks, not one, which filters out one-off network noise.
- Request headers
- Up to 10 custom headers sent with every check (website, API, and keyword monitors), one per line as
Name: value. Handy for API keys or bypassing maintenance gates.
Raw check history is kept for 90 days. Monitors can be paused and resumed anytime without losing history, and the detail page shows response-time charts, uptime over 24 hours to 30 days, recent checks, and the event timeline.