Status Pages

Create public status pages to communicate system health, incidents, and scheduled maintenance to your users.

Public Status Page

Once published, your status page displays real-time system health to users:

What users see:

• Status Banner — Overall system health (All Systems Operational, Partial Outage, etc.)
• Components — Individual services with current status and 90-day uptime chart
• Past Incidents — Recent incident history grouped by date
• Subscribe Button — Subscribe to receive incident notifications

Incident Details

Users can click any incident to view the full timeline of updates:

Subscribing to Updates

Users can subscribe to receive notifications when incidents are created, updated, or resolved.

Email Subscription

1. Click Subscribe on the status page
2. Enter email address
3. Click Subscribe via Email
4. Check inbox for verification email
5. Click verification link to activate subscription

Slack Integration

Send incident notifications directly to a Slack channel:

1. Create a Slack app at api.slack.com/apps
2. Enable Incoming Webhooks
3. Add webhook to your workspace and select channel
4. Copy the webhook URL
5. Paste URL in the subscription dialog

Slack notifications include:

• Rich formatted messages
• Color-coded by incident impact
• Affected services and status updates
• Direct link to status page

Webhook Integration

For custom integrations, subscribe via webhook:

1. Select Webhook tab
2. Enter your webhook endpoint URL
3. Receive JSON payloads for all incident events

RSS Feed

Subscribe via RSS for feed readers and monitoring tools.

---

Managing Status Pages

Navigate to Communicate → Status Pages to view all your status pages.

Click Manage to access the management interface:

Creating a Status Page

1. Click Create Status Page
2. Enter:
   • Name — Internal identifier
   • Headline — Public title shown on the page
   • Description — Brief description for users
3. Click Create

Your page is created in draft mode. Configure components and settings before publishing.

Publishing

1. Add at least one component
2. Configure branding in Settings
3. Click Publish to make the page public
4. Share the URL with your users

---

Components

Components represent individual services or features on your status page.

Adding Components

1. Go to Components tab
2. Click Add Component
3. Enter:
   • Name — Service name (e.g., "API", "Website", "Database")
   • Description — Brief explanation
   • Status — Current operational status
   • Linked Monitors — Associate monitors for reference

Component Status Types

Linked Monitors

Associate monitors with components for reference. Linked monitors appear in the Overview tab and help you track which monitors relate to each service.

---

Incidents

Incidents communicate service disruptions to your users.

Creating an Incident

1. Go to Incidents tab
2. Click Create Incident
3. Enter:
   • Title — Brief description (e.g., "API Response Delays")
   • Message — Initial update for users
   • Status — Current investigation status
   • Impact — Severity level
   • Affected Components — Which services are impacted
4. Choose whether to notify subscribers
5. Click Create

Incident Status Workflow

Impact Levels

Incident Updates

Add updates to keep users informed:

1. Open an existing incident
2. Click Add Update
3. Write update message
4. Update status if changed
5. Choose whether to notify subscribers

Incident Templates

Create reusable templates for common incident types:

1. Go to Settings tab
2. Create templates with pre-filled title, message, and status
3. Use templates when creating new incidents for faster response

Scheduled Maintenance

Communicate planned maintenance in advance:

1. Create incident with Scheduled status
2. Set start and end times
3. Enable automatic status transitions
4. Configure reminder notifications (3, 6, 12, 24 hours before)

The system automatically updates status during the maintenance window.

Postmortems

After resolving an incident, create a postmortem to document:

• Root cause analysis
• Timeline of events
• Remediation steps taken
• Preventive measures

Postmortems can be published to subscribers for transparency.

---

Subscribers

Manage users who receive incident notifications.

Features:

• View all subscribers (email, webhook, Slack)
• See verification status
• Search and filter by email or URL
• Export to CSV
• Delete subscribers
• View statistics (total, verified, pending)

Notification Types

Subscribers receive notifications for:

• New incidents created
• Incident status updates
• Incident resolution
• Scheduled maintenance reminders

---

Settings

Configure branding and notification settings.

Branding

• Logo — Header logo for status page
• Favicon — Browser tab icon
• Status Colors — Customize colors for each status type
• Custom Domain — Use your own domain (e.g., status.yourcompany.com)

Notifications

• Subscriber Types — Enable/disable email, webhook, Slack subscriptions
• RSS Feed — Enable RSS feed for subscribers
• Email Footer — Custom text in notification emails

Custom Domains

Use your own domain for the status page:

1. Add CNAME record: status.yourdomain.com → supercheck.io
2. Configure custom domain in Settings
3. SSL certificate is automatically provisioned

---

Best Practices

Incident Communication:

• Be transparent — share what you know
• Update regularly — even if no progress
• Use clear language — avoid technical jargon
• Set expectations — provide estimated resolution times

Component Organization:

• Use clear, user-friendly names
• Keep the list focused (5-15 components)
• Add descriptions for context