How monitoring works
Current operation
The free checker performs one-time public DNS queries and bounded website requests. The owner uptime preview uses a cloud task configured once per hour, independently of an open browser. Faster automated intervals are not supported by the current preview scheduler.
Status and incidents
Successful conclusive checks count toward measured uptime. Unknown results and unmeasured periods are excluded. Two consecutive failures open an incident; a successful check resolves it. HTTP 403 and 429 remain inconclusive. Redirect destinations are not visited.
Storage
Uptime measurements are retained for 90 days and closed incidents for 365 days. Archives preserve existing monitor history. The public domain checker caches successful results briefly; the detailed method is shown with every report.
Limitations
Scheduling is best-effort and each measurement uses one probe. This is not a multi-region SLA. Email notifications, certificate-expiry monitoring and DNS change alerts are not connected. The administrator can inspect the last runner heartbeat and delayed checks.