Status Pages
Status Pages let you share real-time health information with customers. Use them to reduce support load and keep everyone informed during incidents.
Why Status Pages?
Section titled “Why Status Pages?”- Transparency — Customers see what’s happening without calling support
- Reduce noise — Stop answering “Is your service down?” emails
- Build trust — Show you take reliability seriously
- Compliance — Document outages for SLAs and audits
Public vs. Private
Section titled “Public vs. Private”Public Status Pages
Section titled “Public Status Pages”Anyone with the link can view:
- Real-time status of all checks
- Incident history (past 90 days)
- Average uptime % for each service
Use case: Share status.yourapp.com in your footer or on your website.
Private Status Pages
Section titled “Private Status Pages”Only invited subscribers can view. Subscribers sign up via email to get:
- Real-time status updates
- Email notifications when checks fail or recover
- Incident history
Use case: For enterprise customers or internal teams.
Create a Status Page
Section titled “Create a Status Page”- Go to Health Checks in the dashboard
- Click Create Status Page
- Choose name (e.g., “API Status”, “Uptime Dashboard”)
- Select which checks to display
- Choose public or private
- (Optional) Add logo, colors, and custom message
- Share the link with customers
Customization
Section titled “Customization”- Logo — Upload your company logo
- Colors — Match your brand (header, accent color)
- Message — Add a headline or custom text
- Domain — Custom domain support (e.g., status.example.com)
- Incidents — Add manual incident reports
- Timezone — Display times in your region
Example Status Page Components
Section titled “Example Status Page Components”A public status page shows:
🟢 API (healthy) Last check: 30 seconds ago Uptime: 99.98% this month
🟡 Payment Service (degraded) Last check: 45 seconds ago Uptime: 99.50% this month Incident: Payment processing slower than usual
📋 Recent Incidents May 15, 10:00 AM — Payment Service outage (25 min) May 10, 3:45 PM — Brief API latency spike (5 min)Best Practices
Section titled “Best Practices”- Keep it simple — Show only customer-facing services
- Use clear language — “Payment processing” not “POST /api/v2/transactions”
- Update manually — Add details during ongoing incidents
- Communicate early — Announce status page in release notes
- Monitor yourself — Don’t let a bad check fool customers
Questions? See Health Checks or email hello@fluxpulse.app.