Skip to content
Developer Tool

Uptime Monitor

Auto-monitor website uptime. Custom check intervals, Discord notifications on status changes, and real-time status tracking.

Monitors

No monitors yet. Add one to get started!

Overview

Add monitors to see the overview

Introduction

Downtime is expensive. For an e-commerce site doing $10,000 an hour in revenue, a 15-minute outage costs $2,500 — and that is before you count the customers who never come back. Yet most teams discover outages from a tweet or a Slack message from a frustrated user, not from their own monitoring. An uptime monitor watches your endpoints continuously and alerts you the moment something goes wrong, turning "we found out from a customer" into "we were already investigating when the first ticket came in."

What Is Uptime Monitor?

Uptime Monitor periodically sends HTTP requests to your website or API endpoints from multiple geographic locations and records the response status, latency, and content integrity. You configure the URLs to monitor, the check interval (every minute, every five minutes, or custom), and the conditions that constitute a failure — a non-2xx status code, a response time exceeding a threshold, or a required keyword missing from the response body. When a check fails from multiple regions simultaneously, the tool triggers an alert through your configured channel.

The tool distinguishes between a genuine outage and a transient blip by requiring configurable confirmation thresholds. A single failed check from one region might be a network hiccup; three consecutive failures from three continents is a real problem. It tracks response time percentiles (p50, p95, p99) over rolling windows so you can spot performance degradation before it crosses into full outage territory. Historical data is retained in charts that show uptime percentage, average latency, and incident count over days, weeks, and months — the kind of data you need for SLA reporting.

Monitoring configuration and alert endpoints are stored securely and encrypted at rest. The tool does not execute any JavaScript on your pages — it performs lightweight HEAD or GET requests that check availability without loading your analytics tags or firing side effects. Your internal URLs and API paths are never exposed publicly.

Uptime Monitor Examples

InputOutput
Monitor https://api.shop.com/health every 60s, alert if status != 200Uptime: 99.94% over 30 days, average response: 142ms, last incident: Feb 12 (3-minute outage, 503 from upstream proxy), current status: healthy
Monitor https://app.saas.io/login every 5 min, check body contains "Sign in"Degraded performance detected: p95 latency rose from 210ms to 1,840ms over the last 2 hours while status remains 200 — likely a database bottleneck
Monitor https://cdn.assets.net/main.js every 2 min, alert if response time > 500msIncident opened: 4 consecutive checks exceeded 500ms from US-East and EU-West regions (980ms avg), auto-resolved after 7 minutes when CDN cache repopulated

Key Features of Uptime Monitor

  • Multi-region monitoring that confirms outages from separate geographic locations before triggering alerts
  • Configurable check intervals from 30 seconds to 30 minutes with custom HTTP methods and headers
  • Response body keyword validation to catch "soft failures" where the status is 200 but the page is broken
  • Latency percentile tracking (p50, p95, p99) with rolling window charts for performance trend analysis
  • Alert routing to email, Slack, PagerDuty, and webhook endpoints with escalation timers
  • SLA uptime reporting with monthly and yearly percentages downloadable as PDF for client reviews
  • Maintenance window scheduling that pauses alerts during planned deployments without affecting uptime calculations

How It Works

1

Register Your Endpoint URL

Add the full URL of the web page, API endpoint, or service you want to monitor. The uptime monitor periodically sends HTTP requests to that URL from multiple locations and records whether the endpoint responds successfully within an acceptable timeframe.

2

Continuous Availability Checks

The monitor pings your endpoint at regular intervals — typically every few minutes — and logs the response status, latency, and any error codes. If an endpoint fails to respond or returns a server error, the tool records the incident and starts tracking the outage duration.

3

Alerts and Uptime History

When downtime is detected, the monitor sends you an alert so you can investigate immediately. The dashboard shows your overall uptime percentage, a timeline of incidents, and average response times so you can spot degradation trends before they become full outages.

Who Uses This

SaaS Founders

monitoring the availability of their product's API and web application around the clock so they can respond to outages before customers notice and report them

Site Reliability Engineers

tracking uptime metrics across multiple production services and correlating incidents with deployment timelines to identify which recent releases introduced instability

Agency Developers

monitoring client websites after project handoff to ensure third-party hosting, plugins, and DNS configurations remain stable without requiring manual checking

Frequently Asked Questions

How often does the monitor check my endpoint?
The default check interval is every five minutes, which balances timely outage detection with reasonable resource usage. More frequent intervals are available for critical endpoints where every minute of downtime counts.
What counts as downtime?
Any response with a status code of 500 or above, a connection timeout, or a DNS resolution failure counts as downtime. Redirects (3xx codes) and client errors (4xx codes) do not count as downtime since they indicate the server is responding.
How are alerts delivered?
Alerts can be sent via email, webhook, or both. Webhook alerts integrate with Slack, Discord, Microsoft Teams, and PagerDuty so your on-call team receives downtime notifications in the same channel where they already collaborate.