Status Pages Overview

Status pages let you communicate service status to your customers with a branded, public page.

Features

• Automatic Updates: Status reflects your test results in real-time
• Custom Branding: Your logo, colors, and company name
• Component Grouping: Organize services into logical groups
• Incident History: Show past incidents and resolutions
• Subscriber Notifications: Email and webhook notifications for status changes

Creating a Status Page

1. Go to Status Pages in the sidebar
2. Click Create Status Page
3. Configure basic settings:
   • Slug: URL path (e.g., status.yourcompany.com/acme)
   • Company Name: Displayed in the header
   • Brand Color: Primary color for the page
4. Add components (linked to your tests)
5. Click Publish when ready

Components

Components are the services shown on your status page. Each component is linked to a test:

Component Setting	Description
Display Name	Name shown to customers (e.g., "API")
Description	Optional description
Test	The Pingward test that determines status
Display Order	Position on the page

Component Status

Status is determined automatically based on test results:

Status	Meaning
Operational	Test is passing
Degraded Performance	Slow responses (if configured)
Partial Outage	Intermittent failures
Major Outage	Test is failing
Maintenance	Manually set for planned work

Page Settings

Display Options

Option	Description
Show Uptime Percentage	Display uptime % for each component
Show Response Time	Display average response time
Show Incident History	Display past incidents
Incident History Days	How many days of history to show

Subscription Options

Option	Description
Allow Email Subscriptions	Visitors can subscribe via email
Allow Webhook Subscriptions	Visitors can subscribe via webhook

Publishing

Status pages have two states:

• Draft: Only you can view it
• Published: Publicly accessible

Click Publish to make the page public. Click Unpublish to return to draft.

Custom Domain

By default, status pages are at:

status.pingward.com/your-slug

Contact support to configure a custom domain:

status.yourcompany.com

Best Practices

Name Components Clearly

Use customer-facing names:

• ✅ "API" not "prod-api-us-east-1"
• ✅ "Web Application" not "nginx-frontend"
• ✅ "Payment Processing" not "stripe-webhook-handler"

Group Related Services

Create logical groupings that make sense to customers:

• Core Services: API, Web App
• Integrations: GitHub, Slack
• Infrastructure: CDN, DNS

Communicate Proactively

Use status pages for:

• Planned maintenance
• Known issues
• Resolution updates

Next Steps

• Components - Managing status page components
• Subscriptions - Customer notifications