Understand uptime status and history

Use the project Overview to understand the latest confirmed monitor state, investigate outages, and compare uptime over recent periods.

Read the current status

The Monitor Status card can show Off, Pending, Up, or Down. DeployMonitor requires two consecutive failed checks before changing a monitor to Down, which reduces alerts caused by one brief failure.

Understand skipped checks

DeployMonitor reads robots.txt before requesting an uptime URL and its redirects. When access is blocked or the policy is temporarily unavailable, Settings > Monitoring displays the reason.

Skipped checks do not create failed results, count as downtime, advance outage confirmation, or trigger outage alerts. Monitoring resumes automatically when the policy permits the URL. TLS certificate and Domain Health checks run separately.

Understand maintenance

Uptime checks and monitor status continue during active maintenance, but non-maintenance alerts are suppressed. A confirmed outage can change the card to Down without sending Monitor Down.

When primary Production maintenance ends, DeployMonitor sends Maintenance Ended. If the monitor is still Down, it can then send Monitor Down.

Review an outage

When the monitor is Down, the Overview displays how long it has been down, the recorded reason, and the latest check time in your profile timezone. Reasons can include connection or DNS errors, rejected responses, too many redirects, or an unsafe redirect destination.

Outside maintenance, one successful check returns a confirmed Down monitor to Up and can send a recovery alert.

Understand percentages and recent history

The Overview reports uptime for the last 24 hours, 7 days, and 30 days. No data means no observations exist for the period; it does not mean 0% uptime.

The recent history bar represents the last 24 hours in 48 half-hour buckets. Green is at least 99.5%, yellow at least 90%, orange above 0% but below 90%, red 0%, and gray means no check data was recorded.