Uptime Monitoring

Uptime monitoring pings your HTTP and HTTPS endpoints on a schedule and records whether they responded correctly. It’s the simplest way to get data into numbrs — no scripts, no credentials beyond your account.

Adding a monitor

1. Click Uptime Monitoring in the sidebar
2. Click Add Monitor
3. Enter the URL to check — any HTTP or HTTPS endpoint
4. Give it a name
5. Choose a check interval
6. Click Save

numbrs will start pinging the URL immediately.

Check intervals

Interval	When to use
1 minute	Critical services where fast detection matters
5 minutes	Default — good for most things
15 minutes	Low-priority endpoints, external services you depend on but don’t control

What counts as down

A check fails when:

• The connection times out (10-second timeout)
• The server returns a 5xx response
• The connection is refused
• DNS resolution fails
• The TLS handshake fails

A 4xx response also counts as down by default, unless you configure a specific expected status code. If your endpoint normally returns 401 or 403 (authenticated endpoint you’re just checking for liveness), you can set the expected code to match.

Incident history

When a monitor fails, numbrs opens an incident. You’ll see:

• When the outage started
• When it was resolved (or “ongoing” if it’s still down)
• Duration
• Error type

Incidents are shown on the monitor detail page. They’re retained indefinitely — your historical record of every outage.

Response time tracking

Even when an endpoint is healthy, numbrs records how long each response took. Chart this over time to catch degradation before it becomes a real outage.

Alerts

Configure alerts to get notified when a monitor goes down. See Alerts for configuration options.

A common setup: alert immediately on first failure, then send a reminder if it’s still down after 15 minutes.

Next steps

• Alerts — configure downtime notifications
• Relay Monitoring — monitor Nostr relays specifically
• Dashboard Builder — build response time charts