Uptime Monitoring
Uptime Monitoring Without Compromises
Detect outages in under 60 seconds from 12 global probe locations. HTTP/HTTPS status checks, TLS validation, and intelligent false-positive filtering — so you only get alerted when it truly matters.
Check Intervals & Global Probe Network
Every monitored endpoint is polled at configurable intervals — from 60 seconds on the Performance plan to 300 seconds on the Essentials tier. Each check originates from a distributed pool of probe servers, ensuring geographic redundancy and accurate latency measurement.
60-Second Minimum Interval
The fastest polling cadence available. A check fires every 60 seconds from each probe region, giving you up to 12 data points per hour per location. Ideal for production APIs, payment gateways, and customer-facing portals where seconds of downtime cost revenue.
12 Global Probe Locations
Checks run from Frankfurt (DE), Ashburn (US), Singapore (SG), Tokyo (JP), São Paulo (BR), Sydney (AU), London (UK), Mumbai (IN), Seoul (KR), Paris (FR), Montreal (CA), and Dubai (AE). Each probe performs an independent HTTP/HTTPS request, so a single-region failure never masquerades as a global outage.
Multi-Region Consensus Engine
A site is marked DOWN only when at least 4 out of 12 probes return non-2xx responses within the same polling window. Transient blips — a dropped packet in Ashburn, a brief DNS cache miss in Tokyo — are logged but do not trigger alerts. This consensus logic eliminates the false positives that plague single-probe monitors.
DNS & TLS Handshake Verification
Beyond the HTTP status code, each probe resolves the domain via DNS, measures the A/AAAA record response time, performs a full TLS handshake, and validates the certificate chain. If DNS resolves but the TLS handshake fails, you get a specific "SSL/TLS Error" alert — not a generic "Unreachable" notification. Certificate expiry warnings fire at 30, 14, 7, and 3 days before expiration.
What You Get
StatusPool's uptime checker is built for teams that need signal, not noise. Every feature is designed to reduce alert fatigue while increasing detection accuracy.
HTTP/HTTPS Status Code Tracking
Every response code is recorded — 200, 301, 302, 403, 404, 500, 502, 503, 504. You can set custom rules: treat 301 as OK, alert on any 5xx, or flag a 200 response that returns an unexpected HTML body. Historical status code charts let you correlate outages with deployment windows.
Response Time Baselines
Each endpoint builds a rolling 30-day response time baseline. If your API normally responds in 120 ms and suddenly spikes to 2,400 ms, you get a "Degraded Performance" alert before the service actually fails. Baselines are calculated per probe region, so latency from São Paulo doesn't skew the Frankfurt benchmark.
Uptime SLA & Monthly Reports
Automated SLA calculation against your target — 99.9%, 99.95%, or 99.99%. Monthly PDF reports include total checks performed, minutes of downtime, mean time to detection (MTTD), mean time to recovery (MTTR), and a per-region uptime breakdown. Export to CSV or push to your incident management tool via webhook.
Smart Alert Routing
Route alerts by severity: critical outages go to PagerDuty or Opsgenie, performance degradation lands in Slack, and SSL expiry warnings email your DevOps lead. Alert cooldowns prevent storm flooding — once an alert fires for a given endpoint, no duplicate fires for 15 minutes unless the condition changes state.
Body & Header Content Assertions
Go beyond status codes. Assert that your response body contains a specific JSON field (e.g., "status": "healthy"), that a header like X-Frame-Options is present, or that the response size stays within expected bounds. This catches silent failures where the server returns 200 but the application is actually broken.
Incident Timeline & Root-Cause Context
Every outage generates a timestamped timeline: first detection, consensus confirmation, alert dispatch, and recovery. The timeline includes the exact HTTP response body captured at the moment of failure, DNS resolution results from each probe, and TLS handshake details — giving your on-call engineer everything needed for root-cause analysis without digging through logs.
Frequently Asked Questions
How does StatusPool distinguish a real outage from a single-probe glitch?
We use a 4-out-of-12 consensus rule. If only one or two probes report a failure while the remaining ten return healthy responses, the event is logged as a "transient anomaly" and no alert is sent. This filters out localized network hiccups, ISP routing changes, and probe-specific DNS cache issues. A DOWN state is only declared when a majority of geographically distributed probes agree.
Can I monitor internal endpoints or services behind a firewall?
StatusPool probes are public-facing, so they can only reach services accessible from the internet. For internal endpoints, you can deploy a lightweight StatusPool agent on a server within your network. The agent forwards check results to our platform, giving you the same dashboard, alerting, and SLA reporting for private infrastructure.
What happens if my site returns a 200 status but displays an error page?
Use body content assertions. Configure a check to verify that the response body contains a known-good string (e.g., your site's main navigation element or a JSON health-check token). If the server returns 200 but the expected content is missing, StatusPool flags it as a "Content Mismatch" failure and alerts accordingly. This catches framework-level crashes that still serve a default 200 response.
How quickly will I be notified of an outage?
With 60-second polling and our consensus engine, most outages are detected and alerted within 90–120 seconds. The first probe may register the failure at second 60, but consensus across four regions takes one additional polling cycle. Alert delivery via webhook or PagerDuty adds under 5 seconds. Total mean time to detection (MTTD) averages 105 seconds across our customer base.
Do you monitor SSL certificate expiration?
Yes. Every HTTPS check validates the full certificate chain. You receive automated warnings at 30, 14, 7, and 3 days before expiration. If a certificate expires, the endpoint is marked DOWN immediately with a "Certificate Expired" failure reason. Wildcard certificates, chain intermediates, and OCSP stapling status are all tracked and reported.
Is there a limit on how many URLs I can monitor?
The Essentials plan includes up to 10 monitored endpoints, Professional supports up to 100, and Enterprise has no hard limit. Each endpoint can have multiple check configurations — for example, you can monitor both https://api.example.com/health and https://app.example.com/ as separate checks under the same endpoint. Contact sales for custom capacity planning.