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.io/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
| Field | Description | Example |
|---|---|---|
| Name | Display name shown at the top of the page | "Acme Corp Status" |
| Slug | URL-safe identifier (lowercase, hyphens only) | "acme-corp" |
| Public | Toggle to make the page publicly accessible | Enabled |
Your status page URL will be:
https://status.pingara.io/acme-corp
Step 3: Add Monitors
Select which monitors appear on your status page:
- Click Add Monitor
- Choose from your existing monitors
- Optionally set a Display Name (e.g., show "API" instead of "api-production-us-east")
- 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.
Grouping Monitors into Sections
Pages with many monitors read better when related services are grouped into named sections (for example API, Website, Background Jobs). In the Manage Monitors & Groups dialog:
- Under Groups, enter a name and click Add group
- Use the arrow buttons to reorder groups, the pencil to rename, and the trash icon to delete
- On each monitor you have added to the page, pick its group from the dropdown (or leave it Ungrouped)
On the public page, ungrouped monitors are listed first, followed by each group as a titled section. Every group header shows a rolled-up status, the worst status among its members, so visitors can scan sections at a glance.
Deleting a group never removes its monitors from the page; they simply become ungrouped again. Groups are available on all plans.
Step 4: Configure Incident History
| Option | Description |
|---|---|
| Show Incident History | Display past incidents on the status page |
| Incident History Days | How many days of history to show (e.g., 30, 60, 90) |
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:
| Option | Description |
|---|---|
| Header Text | Custom message at the top (e.g., "All systems operational") |
| Footer Text | Custom footer content (e.g., "Powered by Pingara") |
| Theme Color | Your brand color: a bar across the top of the page and a faint tint behind it |
| Logo | An image you upload, shown above the page name |
| Show logo only | Hides the page name visually so the logo stands alone |
Adding or Removing a Logo
Logo upload isn't part of creating a status page. You add one afterward, from an existing page's edit dialog.
- Go to Status Pages and open the status page you want to brand.
- Click the Edit status page button on that page's card.
- Under Logo, click Upload Logo and choose an image file. Pingara accepts JPEG, PNG, and WebP, up to 5MB. If the page already has a logo, the button reads Replace Logo instead.
- The logo saves immediately. Unlike the dialog's other fields, you don't need to click Save for it to take effect.
Uploading a new image replaces whatever logo was there before. To remove a logo entirely, click Remove; the removal also saves immediately.
By default, once a logo is set it appears above the status page name at the top of the public page. Visitors see both together, since the name heading stays beneath the logo rather than being replaced by it. In dark mode, the logo sits on a light rounded backing panel so logos drawn in dark ink stay visible; in light mode it sits directly on the page with no panel. The logo is size-bounded, so a wide wordmark and a square icon both display neatly. A logo that reads well on a light background works best, since that's what the backing panel is designed around.
Showing the Logo Only
If your logo already carries your company name, you can hide the page name so the logo stands on its own. In the same Edit status page dialog, turn on Show logo only. It is available only once a logo is set, and unlike the logo itself it saves with the dialog's Save Changes button.
The name is hidden visually, not removed: it stays in the page's heading for screen readers and search engines, so turning this on is a layout choice rather than a way to make a page anonymous. The page title in the browser tab, the social sharing card, and the accessible name all still carry it.
Owners, admins, and editors can upload or remove a logo, the same roles that can edit a status page's other settings.
Theme Color
Set your brand's primary color as a hex code:
#55AAE0 (Pingara blue)
#FF6B35 (Orange)
#2ECC71 (Green)
#8E44AD (Purple)
The theme color is applied to:
- A thin bar across the top of the page
- A faint tint of the same color behind the page
It doesn't recolor the status indicators. Operational, degraded and outage always show as green, amber and red, so visitors read the same signal on every status page.
Status Indicators
Your status page displays real-time status for each monitor:
| Status | Indicator | Meaning |
|---|---|---|
| Operational | 🟢 Green | All checks passing, performance normal |
| Degraded | 🟡 Amber | Service is up but performance is below threshold |
| Major Outage | 🔴 Red | Service is down (active incident) |
| Under Maintenance | 🔵 Blue | Planned maintenance in progress |
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: Up to 10 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:
| Monitor Name (Internal) | Display Name (Public) |
|---|---|
| prod-api-us-east-health | API |
| www-production-homepage | Website |
| mobile-bff-v2-prod | Mobile App |
| stripe-webhook-handler | Payments |
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.io/your-slug
Stale status displayed
Status pages update in real time, so a stale display usually points to something upstream of the page itself:
- Check that the monitor is actively running (not paused). A paused monitor stops producing new checks, so its status freezes at whatever it last reported
- Confirm the monitor is actually attached to this status page, not a different one
- Try a hard refresh of the page. A cached copy in your browser or a CDN in front of it can hold an old view briefly
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
Related Articles
Subscriber Notifications
Allow your users to subscribe to status page updates and receive email notifications when incidents occur or maintenance is scheduled.
Understanding Incidents
Learn how Pingara detects outages, creates incidents after consecutive failures, manages the full incident lifecycle, and resolves incidents automatically on recovery.
Maintenance windows: how suppression works
Maintenance windows suppress incidents and alerts for monitors attached to a status page. Learn how the status page link controls what gets suppressed, and how to set up maintenance for monitors you keep private.