Uptime
Monitoring

Xitoring supports HTTP, HTTPS, Ping (ICMP), DNS, TCP, UDP, FTP, SMTP, IMAP, and POP3. You can monitor virtually any internet-facing service from a single dashboard.

With 1-minute check intervals, you can be alerted quickly after an outage is detected. Confirmation checks from multiple nodes eliminate false positives before alerting.

Xitoring operates 15+ monitoring nodes across North America, Europe, Asia-Pacific, South America, and the Middle East. Each check runs from multiple locations simultaneously.

Uptime monitoring is designed for publicly accessible services. For internal services, use our Server Monitoring agent or Heartbeat Monitoring for services behind firewalls.

You can configure maintenance windows to suppress alerts during planned downtime. Your uptime percentage is adjusted to exclude these periods from SLA calculations.

Yes. Xitoring offers one-click migration from Pingdom, Uptime.com, and BetterStack. All your check configurations, alert settings, and contacts are imported automatically.

Industry-standard uptime monitoring runs at one-minute intervals from at least three geographic regions to distinguish real outages from local network blips. Reaching 99.99% annual uptime allows under 53 minutes of downtime per year; 99.999% allows just over five minutes. Effective uptime monitoring goes beyond simple ping checks to validate that responses contain expected content, complete within acceptable latency, and present valid TLS certificates — catching the partial outages and degraded states that simple availability checks miss.

The protocol mix matters as much as the check interval. HTTP and HTTPS checks are the workhorse for any web-facing endpoint, with content-match assertions to catch the "page returns 200 but is actually broken" failure mode. TCP port checks cover non-HTTP services like SSH, MySQL, or custom application ports. DNS checks confirm that records resolve correctly from the resolvers your users actually use, catching the slow-failing cases where a single resolver returns NXDOMAIN while everything else looks fine. Mail-protocol checks (SMTP, IMAP, POP3) keep transactional email flowing. A serious uptime monitoring setup uses the right check type per service layer, not HTTP for everything.

Multi-region probing is the single most important configuration choice. A monitor running from one location confuses a local network blip with a real outage, and the alerts are indistinguishable — within a week the on-call team has trained themselves to ignore pages. Confirmation checks from at least two additional regions before alerting eliminate the vast majority of false positives without losing detection speed. Xitoring runs every check from 15+ probing nodes across North America, Europe, Asia-Pacific, South America, and the Middle East, and an alert only fires once multiple regions agree the service is down.

On-call routing is what separates a monitoring tool from an alerting tool. The signal a check produces is only as useful as the path it takes to the engineer who can fix it. Effective uptime monitoring routes alerts through tiered severity (info → warn → critical → page-everyone), respects the on-call rotation so the right person is woken at 3am, supports acknowledgement and escalation when the primary doesn't respond, and silences cleanly when the incident is resolved. Multi-channel notifications across SMS, push, Slack, Microsoft Teams, PagerDuty, OpsGenie, and webhooks ensure no alert path is a single point of failure.

Public status pages turn uptime monitoring data into a customer-facing trust artifact. Pulling the status page directly from the same monitoring data that drives internal alerting guarantees the two never disagree — your customers see what your on-call sees. Hosting the status page on a separate domain or subdomain keeps it reachable even when the main service is down, and a 12-month rolling uptime history is increasingly expected by enterprise procurement teams. Xitoring publishes both branded public status pages for customer communication and password-gated private status pages for internal SLA tracking from the same uptime data, with no additional configuration.

Uptime monitoring is one layer of a complete observability stack, not a substitute for the others. Uptime watches from outside the perimeter — does the public endpoint respond. Server monitoring watches from inside the OS — what's the CPU, memory, disk, and process state of the host serving that endpoint. Most production teams need both layers running together: uptime tells you when a service is broken; server tells you why, before users notice. Xitoring runs both layers in the same product with a unified alerting engine, so a database failure and a missed HTTP check route through the same notification rules and end up in the same incident timeline.