Sign in →

Uptime Monitor

Monitor your API endpoints, services, and infrastructure with configurable health checks, alerting, and a public status page.

Updated 2026-06-15Suggest edits

Uptime Monitor

Uptime Monitor tracks the availability and performance of your services, API endpoints, and dependencies. It powers your public status page and feeds incident detection.

Monitor Types

TypeWhat It ChecksUse Case
HTTPHTTP response code and bodyAPI endpoints, web services
TCPPort reachabilityDatabases, message queues
DNSDNS resolutionDomain health
CERTTLS certificate validity and expiryHTTPS services

Check Results

Each check produces one of three statuses:

  • UP — Response within threshold, status code as expected
  • DEGRADED — Response time above threshold or partial error rate
  • DOWN — No response or error response received

Configuring a Monitor

  1. Go to Operations → Uptime Monitor
  2. Click + New Monitor
  3. Select type, enter endpoint URL, configure:
    • Check interval — 30s, 60s, 5min, 15min
    • Timeout — max wait before marking DOWN
    • Expected status code — e.g. 200
    • Custom headers — for authenticated endpoints

Linking to Products

For API-level monitoring, link a monitor to a specific product and endpoint path. This enables the Public API Status page to show per-product health.

Alerting

Create alert rules that trigger notifications when a monitor changes state:

ChannelConfig
EmailEmail address
SlackIncoming webhook URL
WebhookCustom HTTPS endpoint (HMAC-SHA256 signed)

Set an escalation delay to avoid noisy alerts for transient failures. A monitor must be DOWN for N minutes before the alert fires.

Streak Tracking

Each monitor tracks:

  • Current streak — consecutive UP or DOWN checks
  • Last status — UP / DEGRADED / DOWN
  • 90-day uptime percentage

Daily Summaries

Aforo computes daily summaries:

  • Uptime percentage for the day
  • Average and P95 response time
  • Total checks and failed check count

These feed the 90-day calendar heatmap and monthly SLA reports.

Degradation Detection

The DegradationDetector runs every 60 seconds. It marks a service as DEGRADED when:

  • Error rate exceeds threshold for 3+ consecutive minutes
  • P95 response time exceeds threshold for 3+ consecutive minutes

Degradation triggers the same alert channels as DOWN events but with lower severity.

Public Status Page

Your uptime monitors feed your /status page — a public-facing view showing:

  • Overall platform health banner (All Systems Operational / Degraded / Major Outage)
  • Per-service status with 90-day uptime bars
  • Active incidents
  • Maintenance windows

Customers can subscribe to status updates by email or webhook.