Sign in →

Service Status

Monitor your services and endpoints with configurable HTTP, TCP, DNS, and certificate checks, state-change alerting, and a public status page.

Updated 2026-07-29Suggest edits

Service Status

Service Status tracks the availability and performance of your services and dependencies. It powers your public status page and feeds incident detection. (Formerly "Uptime Monitor" — renamed 2026-06-18; the URL is unchanged.)

It has tabs for the Service Grid (live per-service status), Uptime History (90-day bars), Monitor Config (create and edit monitors), and Alert Rules.

Monitor types

TypeWhat it checksUse case
HTTPHTTP response code and bodyAPI endpoints, web services
TCPPort reachabilityDatabases, message queues
DNSDNS resolutionDomain health
CERT_EXPIRYTLS certificate validity and expiryHTTPS services

To watch a specific API endpoint, create an HTTP monitor pointing at its URL and set the expected status code — there is no separate per-endpoint monitor type.

Check results

Each check produces one of three statuses:

  • UP — Response within threshold, status code as expected
  • DEGRADED — Response time above the degraded threshold (2,000 ms)
  • DOWN — No response, or an error response

Configuring a monitor

  1. Go to Operations → Service Status → Monitor Config.
  2. Click + New Monitor.
  3. Select a type, enter the endpoint URL, and configure:
    • Check interval — how often the monitor runs
    • Timeout — max wait before marking DOWN
    • Expected status code — e.g. 200
    • Custom headers — for authenticated endpoints

The check scheduler runs every 60 seconds and evaluates each monitor's response. A response slower than the degraded threshold marks the monitor DEGRADED; a failure or timeout marks it DOWN. Flapping is suppressed with a hold-down window so a single blip doesn't trigger a state change.

Alerting

Create alert rules that fire 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 stay DOWN for N minutes before the alert fires.

Daily summaries and history

Each monitor tracks its last status and its 90-day uptime percentage. Aforo also computes a daily summary — uptime percentage, average response time, and total vs. failed check counts — which feeds the 90-day calendar heatmap and monthly SLA reports.

Public status page

Your 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.