Components & status

Components are the individual services, systems, or infrastructure pieces displayed on your status page. Each component has a status that reflects its current health.

Adding components

1. Open your status page settings.
2. Navigate to the Components tab.
3. Click Add Component.
4. Enter a name (e.g., "API Gateway", "Database", "CDN").
5. Optionally group components into categories.

TIP

Group related components under a parent category. For example, group "PostgreSQL Primary", "PostgreSQL Replica", and "Redis Cache" under "Data Layer".

Status levels

Each component can have one of four status levels:

Status	Description	Color
Operational	The component is functioning normally	Green
Degraded	The component is partially affected, users may notice slower performance	Yellow
Partial Outage	The component is down for a subset of users	Orange
Major Outage	The component is completely unavailable	Red

Updating component status

Component status can be updated in three ways:

Manual update

1. Open the component in your status page settings.
2. Select the new status level.
3. Optionally add a message explaining the change.
4. Save.

Automatic update from incidents

When an incident is broadcast to a status page, Batida can automatically set affected components to the appropriate status. To enable this, link components to incidents when declaring them.

API update

PATCH /api/v1/status-pages/{page_id}/components/{component_id}
Authorization: Bearer <token>
Content-Type: application/json

{
  "status": "degraded",
  "message": "Elevated latency due to increased traffic"
}

Component groups

Component groups let you organize related services under a single heading. The group status is automatically derived from its children:

Children status	Group status
All operational	Operational
Some degraded, none down	Degraded
Some partial or major outage	Partial Outage
All in major outage	Major Outage

Best practices

• Keep the component list focused on user-facing services. Internal infrastructure that users cannot observe does not need to be on the status page.
• Update component status promptly when an incident begins and when it is resolved.
• Use descriptive messages to explain status changes. "Database query timeouts" is more useful than "Degraded."