Creating Status Pages

Status pages give your users a transparent view of your service health. Instead of fielding "is it down?" support tickets, point users to a branded status page that updates in real time.

What Is a Status Page?

A status page is a public-facing web page that displays:

• Current status of each monitored service
• Incident history with timeline and resolution details
• Uptime percentage over recent periods
• Planned maintenance announcements

Pingara hosts your status page at a public URL based on your chosen slug:

https://status.pingara.com/your-company-slug

Creating Your First Status Page

Step 1: Navigate to Status Pages

Go to Status Pages in the sidebar and click Create Status Page.

Step 2: Basic Configuration

Your status page URL will be:

https://status.pingara.com/acme-corp

Step 3: Add Monitors

Select which monitors appear on your status page:

1. Click Add Monitor
2. Choose from your existing monitors
3. Optionally set a Display Name (e.g., show "API" instead of "api-production-us-east")
4. Set the Display Order (drag to reorder)

Tip: Only add customer-facing services to your public status page. Internal tools and staging monitors should be excluded.

Step 4: Configure Incident History

Incident history helps build trust by showing your track record and how quickly you resolve issues.

Step 5: Save and Preview

Click Save and then Preview to see how your status page looks to visitors.

Customization Options

Branding

Customize the look and feel to match your brand:

Theme Color

Set your brand's primary color as a hex code:

#29ABE2  (Pingara blue)
#FF6B35  (Orange)
#2ECC71  (Green)
#8E44AD  (Purple)

The theme color is applied to:

• Status indicators
• Header accent
• Links and buttons

Custom Domain (Pro)

Point your own domain to your Pingara status page:

1. Add a CNAME record: status.yourcompany.com → status.pingara.com
2. Enter your custom domain in the status page settings
3. Pingara handles SSL certificate provisioning automatically

Status Indicators

Your status page displays real-time status for each monitor:

Status updates automatically based on your monitor results — no manual intervention needed.

Incident Display

When an active incident exists, your status page shows:

• Incident title — Auto-generated from monitor name and error type
• Current status — Investigating, Identified, Monitoring, or Resolved
• Timeline — Chronological updates as the incident progresses
• Affected services — Which monitors are impacted
• Duration — How long the incident has been ongoing

Resolved Incidents

Past incidents appear in the history section with:

• Start and resolution timestamps
• Total duration
• Root cause summary (if available)
• Affected regions

Managing Multiple Status Pages

You can create separate status pages for different audiences:

Example setup:

Public Status Page (acme-status)
  ├── Website
  ├── API
  └── Mobile Backend

Internal Status Page (acme-internal)
  ├── Admin Dashboard
  ├── CI/CD Pipeline
  ├── Staging Environment
  └── Database Cluster

Free Plan Limits

• Free: 1 status page
• Pro: Unlimited status pages

Best Practices

Choose Meaningful Service Names

Don't expose internal monitor names to customers. Use display names that make sense to your users:

Keep It Simple

Don't add every monitor to your public status page. Focus on:

• Customer-facing services
• APIs that developers integrate with
• Critical infrastructure that affects end users

Enable Incident History

Showing incident history builds trust. Users can see:

• How often issues occur
• How quickly you resolve them
• Your overall track record

Update During Incidents

While Pingara auto-detects and auto-resolves incidents, consider adding manual notes during major outages to keep users informed about investigation progress.

Troubleshooting

Status page shows "No monitors"

Ensure you've added at least one monitor to the status page configuration.

Status page not accessible

• Verify the Public toggle is enabled
• Check that the slug is valid (lowercase letters, numbers, and hyphens only)
• Try accessing directly: https://status.pingara.com/your-slug

Stale status displayed

Status updates are real-time via Convex subscriptions. If data appears stale:

• Check that your monitors are actively running (not paused)
• Verify the Convex connection in your browser console

Next Steps

• Subscriber Notifications — Let users subscribe to updates
• Understanding Incidents — How incidents appear on status pages
• HTTP/HTTPS Monitoring — Configure the monitors behind your status page