Uptime Checks
Uptime Checks monitor your websites and APIs from DanubeData's infrastructure in Falkenstein, Germany. Create a check in under 30 seconds from the Uptime section in your sidebar.
Overview
- Intervals: checks run every 1 or 5 minutes over HTTP/HTTPS (ports 80 and 443).
- Expected response: define what a healthy response looks like — an expected HTTP status code, a keyword that must appear in the response body, or both. A check counts as failed if the response doesn't match.
- Down detection: a check turns DOWN after N consecutive failures (configurable, default 2) and you receive an email immediately; the alert also appears in your in-app Notification Center, and another email confirms recovery. Each failed probe is retried once after 5 seconds before it counts.
- Probe source: requests originate from our platform egress IPs with User-Agent
DanubeData-Uptime/1.0. Allowlist this User-Agent if your endpoint sits behind a WAF or bot protection. - TLS monitoring: for HTTPS targets we track certificate expiry and warn you (default: 14 days before).
- History & availability: see your uptime percentage over the last 24 hours, 7 days, and 30 days, plus a full history chart of every probe with incidents shaded. Per-minute results are kept for 7 days; hourly availability history for 90 days.
- Limits: included on every plan; teams start with 5 checks and can contact support to raise the limit.
- Private targets: checks can only reach publicly routable addresses — private networks, cloud metadata endpoints, and DanubeData platform infrastructure are blocked.