Status Pages - StatusStack Documentation

Overview

Every Stack in StatusStack automatically gets a public status page where you can share real-time status information with customers, clients, and stakeholders.

Accessing Your Status Page

Each Stack has a unique URL:

https://statusstack.com/status/[your-stack-slug]

Example:

Stack Name: Production Infrastructure
Stack Slug: production-infrastructure
Status Page: https://statusstack.com/status/production-infrastructure

Status Page Features

Real-Time Status

Live component status updates every 1-5 minutes

Incident History

Display past incidents and resolution timelines

Email Subscriptions

Let visitors subscribe to status updates

Custom Branding

Logo, colors, and custom domain (Pro/Enterprise)

Maintenance Windows

Schedule and display planned maintenance

Uptime Statistics

Show 7-day, 30-day, and 90-day uptime percentages

Customizing Your Status Page

Open Stack Settings

Navigate to your Stack and click ⚙️ Settings

Go to Status Page Tab

Click “Status Page” in the settings menu

Configure Basic Settings

Customize page information:

Page Title: Production Services Status
Description: Real-time status of our production infrastructure
Support URL: https://support.yourcompany.com
Support Email: support@yourcompany.com

Upload Logo (Pro/Enterprise)

Add your company logo:

Recommended size: 200x50px (transparent PNG)
Maximum size: 2MB
Formats: PNG, SVG preferred

Choose Color Scheme

Set primary brand color:

Primary Color: #FF5D5C (your brand color)
Status Colors:
  - Operational: #10b981 (green)
  - Degraded: #f59e0b (yellow)
  - Critical: #ef4444 (red)
  - Maintenance: #3b82f6 (blue)

Configure Visibility

Set page visibility:

Public
Private
Password Protected

Anyone with the link can view
Indexed by search engines (optional)
Best for customer-facing pages

Save Changes

Click “Save Status Page Settings”

Status Page Layout

Default Layout

┌─────────────────────────────────────────────┐
│  [Logo]        Production Services Status   │
│                                             │
│  🟢 All Systems Operational                 │
│                                             │
├─────────────────────────────────────────────┤
│                                             │
│  📊 Current Status                          │
│                                             │
│  🟢 Production API          ↑ 99.9%         │
│  🟢 Database               ↑ 100%          │
│  🟢 CDN                    ↑ 99.8%         │
│  🟢 Payment Processing     ↑ 99.7%         │
│                                             │
├─────────────────────────────────────────────┤
│                                             │
│  📅 Scheduled Maintenance                   │
│                                             │
│  Jan 25, 2025 2:00-4:00 AM UTC             │
│  Database migration and upgrades            │
│                                             │
├─────────────────────────────────────────────┤
│                                             │
│  📜 Incident History                        │
│                                             │
│  ✅ Resolved - Jan 15, 2025                │
│     Brief API outage (15 minutes)           │
│                                             │
│  ✅ Resolved - Jan 10, 2025                │
│     Scheduled maintenance completed         │
│                                             │
├─────────────────────────────────────────────┤
│                                             │
│  ✉️  Subscribe to Updates                   │
│                                             │
│  [email@example.com] [Subscribe]            │
│                                             │
└─────────────────────────────────────────────┘

Grouped Components Layout

Organize components into collapsible groups:

┌─────────────────────────────────────────────┐
│  🟢 All Systems Operational                 │
├─────────────────────────────────────────────┤
│                                             │
│  🔧 Core Services             [Collapse ▼]  │
│    🟢 Production API          ↑ 99.9%       │
│    🟢 Database               ↑ 100%        │
│    🟢 Cache Layer            ↑ 99.8%       │
│                                             │
│  🌐 Infrastructure           [Expand ▶]     │
│                                             │
│  💳 Payment Processing       [Expand ▶]     │
│                                             │
└─────────────────────────────────────────────┘

Component Display Options

Showing Component Details

Configure what information to display for each component:

Status Indicator

Color-coded status badges:

🟢 Operational - Green
🟡 Degraded - Yellow
🔴 Critical - Red
🔵 Maintenance - Blue
⚪ Unknown - Gray

Uptime Percentage

Show uptime stats:

Component Name    ↑ 99.9% (7d)

Options:

Last 7 days
Last 30 days
Last 90 days
Hide uptime

Response Time

Display performance metrics:

Production API    125ms avg

Shows:

Average response time
Updated in real-time
Custom monitors only

Last Updated

Timestamp of last check:

Updated 2 minutes ago

Component Ordering

Customize the order components appear:

Manual ordering - Drag and drop in settings
Alphabetical - A-Z by component name
By status - Critical → Degraded → Operational
By importance - Set priority weights

Recommended: Manual ordering with most critical first

Incident Management

Creating Incidents

Manually create incidents for transparency:

Open Stack

Navigate to your Stack dashboard

Click Create Incident

Click “Create Incident” button

Fill Incident Details

Title: API Performance Degradation
Status: Investigating
Impact: Degraded Performance
Affected Components:
  - Production API
  - Database
Message: |
  We are currently investigating reports of
  slower than normal API response times.
  Our team is actively working on this issue.

Post Incident

Click “Create Incident” - appears on status page immediately

Incident Lifecycle

Track incidents through their lifecycle:

1. 🔵 Investigating
   └─ Initial detection, gathering information

2. 🟡 Identified
   └─ Root cause found, planning fix

3. 🔧 Monitoring
   └─ Fix deployed, monitoring stability

4. ✅ Resolved
   └─ Issue fully resolved, post-mortem complete

Posting Incident Updates

Keep stakeholders informed:

Open Incident

Click on the active incident

Add Update

Click “Post Update”

Write Update

Status: Identified
Message: |
  We have identified the cause as a database
  connection pool exhaustion. Our team is
  deploying a fix now. ETA: 10 minutes.

Publish

Update appears on status page Email sent to subscribers

Best practices:

Update every 15-30 minutes during active incidents
Be transparent about root cause
Provide ETAs when possible
Notify when resolved

Email Subscriptions

Allow visitors to subscribe to updates:

Enabling Subscriptions

Open Status Page Settings

Stack → Settings → Status Page

Enable Subscriptions

Toggle “Allow Email Subscriptions” to ON

Configure Options

Require Confirmation: Yes (recommended)
Send Welcome Email: Yes
Unsubscribe Link: Included in all emails

Save Settings

Subscription form appears on status page

What Subscribers Receive

Subscribers get emails for:

Incident Created - New outage or issue
Incident Updated - Progress updates
Incident Resolved - Issue fixed
Maintenance Scheduled - Upcoming maintenance (optional)
Component Status Change - Major status changes (optional)

Example subscription email:

Subject: [STATUS UPDATE] Production API - Investigating

StatusStack - Production Services
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔵 INVESTIGATING

API Performance Degradation

We are currently investigating reports of slower
than normal API response times. Our team is
actively working on this issue.

Affected Services:
- Production API
- Database

Updates will be posted as we learn more.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

View full status page:
https://statusstack.com/status/production

Manage subscription:
https://statusstack.com/unsubscribe/token123

Managing Subscribers

View and manage your subscribers:

Navigate to Stack → Settings → “Subscribers”
See total subscriber count
Export subscriber list (CSV)
Remove specific subscribers
View subscription analytics

Scheduled Maintenance

Communicate planned downtime:

Open Stack

Navigate to your Stack

Click Schedule Maintenance

Click “Schedule Maintenance” button

Configure Maintenance

Title: Database Migration
Start: January 25, 2025 at 2:00 AM UTC
End: January 25, 2025 at 4:00 AM UTC
Description: |
  We will be performing a database migration
  to improve performance. Services may be
  unavailable during this window.
Affected Components:
  - Production API
  - Database
Notify Subscribers: Yes (7 days before)

Save Maintenance

Appears on status page immediately Notification sent to subscribers

Maintenance Display

Maintenance windows appear prominently:

┌─────────────────────────────────────────────┐
│  🔵 Scheduled Maintenance                   │
│                                             │
│  📅 January 25, 2025                        │
│  🕐 2:00 AM - 4:00 AM UTC                   │
│                                             │
│  Database Migration                         │
│                                             │
│  We will be performing a database migration │
│  to improve performance. Services may be    │
│  unavailable during this window.            │
│                                             │
│  Affected:                                  │
│  - Production API                           │
│  - Database                                 │
│                                             │
└─────────────────────────────────────────────┘

Custom Domains (Pro/Enterprise)

Use your own domain for status pages:

Setting Up Custom Domain

Choose Subdomain

Decide on subdomain:

status.yourcompany.com
health.yourcompany.com
monitoring.yourcompany.com

Add DNS Record

In your DNS provider, add CNAME record:

Type: CNAME
Name: status
Value: custom.statusstack.com
TTL: 3600

Configure in StatusStack

Stack → Settings → Status Page → “Custom Domain”

Custom Domain: status.yourcompany.com

Click “Verify Domain”

Wait for SSL

StatusStack automatically provisions SSL certificateTakes 5-60 minutes for DNS propagation

Verify

Visit https://status.yourcompany.com

DNS Providers

Cloudflare
AWS Route 53
Google Domains
Namecheap

Type: CNAME
Name: status
Target: custom.statusstack.com
Proxy Status: DNS Only (not proxied)
TTL: Auto

Type: CNAME
Name: status.yourcompany.com
Value: custom.statusstack.com
TTL: 300

Type: CNAME
Host: status
Points to: custom.statusstack.com
TTL: 1h

Type: CNAME Record
Host: status
Value: custom.statusstack.com
TTL: Automatic

Embedding Status Widgets

Embed live status on your website:

Option 1: Status Badge

Inline status indicator:

<script src="https://statusstack.com/embed.js"></script>
<div data-statusstack-badge="production-infrastructure"></div>

Displays:

🟢 All Systems Operational

Option 2: Component List

Show all components:

<script src="https://statusstack.com/embed.js"></script>
<div
  data-statusstack-components="production-infrastructure"
  data-theme="light"
></div>

Displays:

Current Status
🟢 Production API       99.9%
🟢 Database            100%
🟢 CDN                 99.8%

Option 3: Incident Feed

Show recent incidents:

<script src="https://statusstack.com/embed.js"></script>
<div
  data-statusstack-incidents="production-infrastructure"
  data-limit="5"
></div>

Customization Options

<div
  data-statusstack-components="your-stack-slug"
  data-theme="dark"              <!-- light|dark -->
  data-show-uptime="true"        <!-- true|false -->
  data-show-history="false"      <!-- true|false -->
  data-max-height="400px"
></div>

See Embed Guide for full documentation.

Status Page Analytics

Track status page usage (Enterprise):

Pageviews

Daily/weekly/monthly traffic to status page

Subscriber Growth

New subscribers over time

Incident Engagement

How many people viewed each incident

Traffic Sources

Referrers to your status page

Best Practices

Keep It Simple

Don’t overwhelm visitors✅ Show 5-10 critical services ✅ Group related components ✅ Hide internal services❌ List every microservice ❌ Show development environments ❌ Include redundant components

Be Transparent During Incidents

Communicate openly✅ Post incident within 5 minutes ✅ Update every 15-30 minutes ✅ Explain root cause ✅ Provide ETAs when possible❌ Hide incidents ❌ Go silent during outages ❌ Be vague about issues

Maintain Regularly

Keep status page currentMonthly:

Review component list
Update descriptions
Check branding
Verify contact information

Quarterly:

Review incident response process
Update maintenance schedules
Audit subscriber list

Use Custom Domain

Build trust with branded URL❌ statusstack.com/status/company-123 ✅ status.yourcompany.comBenefits:

Professional appearance
Easier to remember
Better for marketing
SEO benefits

Troubleshooting

Custom Domain Not Working

Check:

DNS CNAME record is correct
DNS has propagated (use dig or nslookup)
Not using Cloudflare proxy (should be DNS only)
Waited 5-60 minutes for SSL provisioning

Subscribers Not Receiving Emails

Verify:

Email subscriptions are enabled
Emails not in spam folder
Subscriber confirmed email address
Notification events are configured

Status Page Showing as Private

Check:

Stack visibility setting is “Public”
No password protection enabled
Stack is not archived

Next Steps

Embed Status Widgets

Add status widgets to your website

Incident Response

Learn best practices for incident management

Custom Branding

Advanced branding options (MSP)

Email Integrations

Configure email delivery settings

​Overview

​Accessing Your Status Page

​Status Page Features

Real-Time Status

Incident History

Email Subscriptions

Custom Branding

Maintenance Windows

Uptime Statistics

​Customizing Your Status Page

​Status Page Layout

​Default Layout

​Grouped Components Layout

​Component Display Options

​Showing Component Details

​Component Ordering

​Incident Management

​Creating Incidents

​Incident Lifecycle

​Posting Incident Updates

​Email Subscriptions

​Enabling Subscriptions

​What Subscribers Receive

​Managing Subscribers

​Scheduled Maintenance

​Maintenance Display

​Custom Domains (Pro/Enterprise)

​Setting Up Custom Domain

​DNS Providers

​Embedding Status Widgets

​Option 1: Status Badge

​Option 2: Component List

​Option 3: Incident Feed

​Customization Options

​Status Page Analytics

Pageviews

Subscriber Growth

Incident Engagement

Traffic Sources

​Best Practices

​Troubleshooting

​Custom Domain Not Working

​Subscribers Not Receiving Emails

​Status Page Showing as Private

​Next Steps

Embed Status Widgets

Incident Response

Custom Branding

Email Integrations

Overview

Accessing Your Status Page

Status Page Features

Customizing Your Status Page

Status Page Layout

Default Layout

Grouped Components Layout

Component Display Options

Showing Component Details

Component Ordering

Incident Management

Creating Incidents

Incident Lifecycle

Posting Incident Updates

Email Subscriptions

Enabling Subscriptions

What Subscribers Receive

Managing Subscribers

Scheduled Maintenance

Maintenance Display

Custom Domains (Pro/Enterprise)

Setting Up Custom Domain

DNS Providers

Embedding Status Widgets

Option 1: Status Badge

Option 2: Component List

Option 3: Incident Feed

Customization Options

Status Page Analytics

Best Practices

Troubleshooting

Custom Domain Not Working

Subscribers Not Receiving Emails

Status Page Showing as Private

Next Steps