Everything between
a signal and a fix.

Checks & regions

Probe from eight places, agree before you page.

Every check runs from each compatible region you selected, exactly once per cycle. You set how many regions must fail before it counts as down, so one bad network path stays a footnote instead of an incident. Region choices adapt to the check type.

• HTTP and HTTPS checks with status, redirect, and content-match rules
• DNS A, AAAA, CNAME, MX, NS, and TXT expected-value assertions from all eight regions
• Raw TCP-port checks from Finland and four Google Cloud regions, with an optional passive bounded banner rule
• ICMP ping checks from Finland for hosts that do not speak HTTP
• Per-check interval and per-check failure threshold
• Response times kept per region, so slowdowns show up before failures

DNS and TCP checks are included with Complete and Ultimate.

Incidents

One incident per outage, opened and closed for you.

When the failure threshold is met, an incident opens on that cycle — not the next one. It carries the regions involved, the response history leading up to it, and who acknowledged it. When the service recovers, it closes itself.

• Opens on the cycle the threshold is met, resolves automatically on recovery
• Acknowledge to tell the rest of the team you have it
• Notes on the incident for handover between shifts
• No duplicate incidents when a service flaps

Domains & SSL

Certificates you never have to remember.

Add a domain and GeeksUptime checks its certificate daily. You hear about an approaching expiry with weeks to spare, and you hear about a fingerprint change the day it happens — which is often the first sign something was reconfigured without you.

• Daily expiry checks with advance notice
• Certificate change detection with a full history per domain
• Issuer and validity window visible at a glance
• Routed through the same notification groups as uptime

Maintenance windows

Planned work should not look like an outage.

Schedule a window for a whole workspace or just the checks you are touching, in your own timezone. Monitoring keeps recording results the entire time, so you still get the data — you just do not get woken up by your own deploy.

• Scope a window to a workspace or to specific checks
• Set it in your timezone; stored and evaluated in UTC
• Results keep recording while incidents and alerts stay suppressed
• Everything returns to normal automatically when the window ends