Services

Service Status

Status Types

Every service in Alert24 has a status that reflects its current health. These statuses are displayed on your status pages and used to communicate service health to your customers.

Operational

The service is working normally. All monitoring checks are passing. This is the default status for new services.

Degraded Performance

The service is available but experiencing issues — slow response times, intermittent errors, or reduced throughput. Customers can still use the service but may notice problems.

Partial Outage

Some functionality of the service is unavailable. For example, an API might be responding to GET requests but failing on POST requests, or a service might be down in one region but working in others.

Major Outage

The service is completely unavailable. Monitoring checks are failing consistently and the service is not responding.

Under Maintenance

Planned maintenance is in progress. This status is typically set manually before maintenance begins and cleared when maintenance is complete.

Automatic Status Updates

When monitoring checks are linked to a service, Alert24 can automatically update the service status based on check results.

How It Works

  1. A monitoring check runs at its configured interval
  2. If the check fails, Alert24 evaluates the failure against the configured threshold
  3. If the failure threshold is met (e.g., 3 consecutive failures), the service status is automatically updated
  4. When the check starts passing again, the service status is restored to Operational

Failure Thresholds

You can configure how many consecutive failures are required before the status changes. This prevents false alarms from transient network issues:

  • 1 failure — Immediate status change (sensitive)
  • 3 failures — Status changes after 3 consecutive failures (balanced, recommended)
  • 5 failures — Status changes after 5 consecutive failures (conservative)

Status Mapping

The severity of the automatic status update depends on the nature of the failure:

  • Complete failure (timeout, connection refused, 5xx errors) → Major Outage
  • Partial failure (slow response, unexpected status code) → Degraded Performance

Manual Status Updates

You can always override the automatic status by manually setting a service's status:

  1. Go to the service detail page
  2. Click the status indicator
  3. Select the new status
  4. Optionally add a note explaining the change

Manual status updates take precedence over automatic updates. This is useful when:

  • You're aware of an issue before monitoring detects it
  • You want to set a maintenance status before planned work
  • You need to override an automatic status change

Status History

Alert24 tracks status changes over time, giving you:

  • Uptime percentage — How much of the time the service was operational
  • Status timeline — A visual history of status changes
  • Incident correlation — Status changes linked to incidents

This history appears on your status pages and helps you track service reliability over time.

Best Practices

  • Use automatic updates for services with monitoring checks — let Alert24 handle routine status changes
  • Reserve manual updates for situations where you have information monitoring can't detect
  • Set maintenance status proactively before planned work begins, so customers see it on the status page
  • Configure appropriate thresholds — too sensitive and you'll get false alarms, too conservative and you'll miss real issues
← Creating ServicesHTTP Checks →