What does UptimeMatrix monitor?

UptimeMatrix monitors websites, APIs, servers, SSL certificates, domain expiry, ports, blacklists, and more. We provide comprehensive infrastructure monitoring from 60+ global locations with instant alerts via email, SMS, Slack, and webhooks.

Is UptimeMatrix free?

Yes! UptimeMatrix offers a Free Forever plan with 5 monitors, 5-minute check intervals, and 30-day data retention. No credit card required. Paid plans start at $7/month (annual billing) for faster intervals and higher capacity.

How often does it check uptime?

Free plans check every 5 minutes. Paid plans support 1-minute check intervals. You can customize check intervals from 1 minute to 24 hours based on your plan and monitoring needs.

What alert channels are supported?

UptimeMatrix supports email, SMS, phone calls, Slack, Discord, Microsoft Teams, PagerDuty, webhooks, and custom integrations. All notification channels are available on every plan—no artificial limitations.

Does it support server monitoring?

Yes! UptimeMatrix monitors server health including CPU, memory, disk space, network performance, and processes. We support Linux, Windows, and cloud servers with real-time metrics and alerts.

Do you provide public status pages?

Yes! Create beautiful, customizable public status pages to communicate incidents, maintenance, and uptime to your customers. White-label options available for enterprise plans.

Where are monitoring nodes located?

UptimeMatrix operates 60+ monitoring locations worldwide across North America, Europe, Asia, and Australia. This ensures accurate regional performance insights and helps detect location-specific issues.

Yes! UptimeMatrix supports comprehensive API monitoring including REST APIs, GraphQL, custom headers, authentication, request body validation, response time tracking, and JSON schema validation.

Wiki

What Is Website Monitoring?

Updated 2026-04-05 · Published 2026-04-01

Direct answer

Website monitoring is automated checking that a site responds correctly from outside your infrastructure—typically over HTTP/HTTPS—on a schedule. A probe requests your URL (and may validate status codes, response time, or page content), records the result, and triggers alerts when checks fail or breach thresholds.

Key points

External perspective: Checks run from third-party networks, so they reflect what users see through DNS, TLS, and routing—not only what looks healthy inside your LAN.
Signals: Common outputs include uptime percentage, incident timelines, response times, and SSL or redirect behavior.
Scope: Can be as simple as “200 OK on /” or as detailed as keyword checks, multi-step flows, and regional probes.

How it fits operations

Teams use website monitoring to catch outages before customers do, validate releases, and support SLAs. It complements logging and APM: those tools explain application behavior; monitoring proves availability and reachability from the public internet.

Limitations

Monitoring proves reachability and correctness of what you configure—it does not replace code profiling, deep security audits, or user-session replay. False positives can occur when probes are blocked, rate-limited, or when DNS differs by region.

Frequently asked questions

How often should checks run?

Interval depends on risk: production homepages often use 1–5 minute intervals; lower-traffic properties may use longer intervals to reduce noise and cost.

Does monitoring fix downtime?

No—it detects and alerts. Remediation still requires your runbooks, hosting changes, or deployments.

What is a good first check?

Start with HTTPS GET to your primary URL, assert 2xx/3xx as appropriate, and alert after consecutive failures from more than one location if possible.