Status Page Components

Components represent the individual services or systems displayed on your status page. Configure statuses, link monitors, and group related components.

What are Components?

Components are the building blocks of your status page:

• API: REST API, GraphQL endpoint
• Website: Marketing site, dashboard
• Database: PostgreSQL, MongoDB
• CDN: Static assets, images
• Authentication: Login, OAuth

Component Statuses

Creating Components

Manual Component

1. Go to Status Pages → Select your page
2. Click Components tab
3. Click Add Component
4. Fill in:
   • Name: API
   • Description: REST API endpoints
   • Status: Operational
   • Monitor: (optional) Link to monitor
5. Click Create

Monitor-Linked Component

Link a component to a monitor for automatic status updates:

Monitor Status → Component Status:

Monitor Up           → Operational
Monitor Down (1-2x)  → Degraded Performance
Monitor Down (3+)    → Major Outage
Monitor Paused       → Under Maintenance

Component Groups

Organize related components into groups:

Application Services
  ├── API
  ├── Web Dashboard
  └── Mobile App

Infrastructure
  ├── Database
  ├── Redis Cache
  └── Message Queue

Third-Party
  ├── Stripe Payments
  ├── SendGrid Email
  └── AWS S3

Creating Groups

1. Click Add Group
2. Name: "Application Services"
3. Drag components into group
4. Reorder as needed

Automatic Status Updates

From Monitors

When a monitor fails, the linked component updates automatically:

10:30:00 - API monitor fails (1st failure)
Status: Operational → Degraded Performance
Message: "Experiencing higher than normal response times"

10:32:00 - API monitor fails (3rd consecutive)
Status: Degraded Performance → Major Outage
Message: "API is currently unavailable"

10:38:42 - API monitor recovers
Status: Major Outage → Operational
Message: "All systems operational"

Manual Overrides

Override automatic status for custom messaging:

1. Click component
2. Click Update Status
3. Select status (e.g., Under Maintenance)
4. Add custom message
5. Click Update

Component Configuration

Basic Settings

Monitor Linking

Link multiple monitors to a single component:

Component: API
Linked Monitors:
  - API Health Check (HTTP /health)
  - API Latency Monitor (response time)
  - Database Connection (TCP 5432)

Status Logic:
- All monitors up → Operational
- 1 monitor down → Degraded Performance
- 2+ monitors down → Major Outage

Uptime Percentage

Status page automatically calculates uptime:

Component: API

Today:      99.8%  (10 min downtime)
7 Days:     99.5%  (50 min downtime)
30 Days:    99.9%  (43 min downtime)
90 Days:    99.95% (108 min downtime)

Incident Impact

Show which components are affected by incidents:

Incident: Database Performance Issues

Affected Components:
  🔴 API (Major Outage)
  🟡 Web Dashboard (Degraded Performance)
  🟢 Mobile App (Operational - uses cache)

Not Affected:
  ✓ CDN
  ✓ Email Service

Best Practices

1. Use Clear Names

• Good: API, Web Dashboard, Payment Processing
• Bad: server-01, prod-db-master, thing

2. Group Logically

• User-facing services (API, Website, Mobile)
• Infrastructure (Database, Cache, Queue)
• Third-party (Stripe, AWS, SendGrid)

3. Link to Monitors

• Automate status updates
• Reduce manual work
• Faster incident detection

4. Keep it Simple

• 5-10 components is ideal
• Too many → overwhelming
• Too few → not useful

5. Update Maintenance Windows

Set status to "Under Maintenance" during planned work:

Scheduled Maintenance
Date: 2026-02-20 02:00-04:00 UTC
Components: Database, API
Impact: API will be unavailable
Status: Under Maintenance

Component History

View past status changes:

Component: API

Feb 13, 2026
10:38:42 - Operational
10:32:00 - Major Outage (6m 42s)
10:30:00 - Degraded Performance (2m)

Feb 12, 2026
All day - Operational

Feb 11, 2026
15:00:00 - Operational
14:45:00 - Under Maintenance (15m)

Next Steps

• Branding: Customize logo and colors
• Subscriptions: Email notifications
• Status Pages Overview: Full guide
• Status Pages API: Programmatic control