Status Pages

Status pages provide a public view of your service health, keeping users informed during outages and building trust through transparency. PixoMonitor status pages are fully customizable and can be hosted on your own domain.

Overview

Your status page displays:

Overall system status — Aggregate health across all components
Component status — Individual service health (API, Website, Database, etc.)
Active incidents — Ongoing issues and updates
Recent incidents — Past 30 days of incident history
Uptime charts — Visual uptime history for each component

Creating Components

Components organize your monitors into logical groups on your status page. For example, you might have components for "API", "Website", "Database", and "CDN".

Add a Component

Navigate to components

Go to Status Page → Components.

Create a new component

Click Add Component and enter:

Name — Display name (e.g., "API")
Description — Optional description
Position — Display order on the status page

Assign monitors

Edit your monitors and set the Component field to assign them to the component.

Component Groups

For complex systems, organize components into groups:

Create a Component Group (e.g., "Core Infrastructure")
Assign components to the group
Groups appear as collapsible sections on the status page

Only monitors assigned to components appear on the public status page. Use this to hide internal monitors from public view.

Status Page Settings

Customize the appearance and behavior of your status page.

Basic Settings

Setting	Description
Title	Status page title (e.g., "Acme Status")
Homepage URL	Link to your main website
Logo URL	Custom logo image URL

Display Options

Option	Description	Default
Show Bar Charts	Display uptime history bars	On
Show Uptime Percentage	Show uptime % for each component	On
Show Overall Percentage	Show aggregate uptime	On
Show Outage Details	Show error messages publicly	On
Show Monitor URL	Display monitored URLs	Off
Enable Details Page	Link to detailed monitor views	On
Hide Paused Monitors	Exclude paused monitors	Off
Show Footer Branding	Show "Powered by PixoMonitor"	On

Layout Options

Option	Values	Description
Layout Density	Wide / Compact	Amount of whitespace
Layout Alignment	Left / Center	Content alignment

Theme Options

Option	Values	Description
Theme	Light / Dark / Auto	Color scheme
Accent Color	Any hex color	Brand accent color

Custom Domains

PixoMonitor's default hosted status surface is available at https://pixomonitor.com/status. Paid plans can associate an account-specific status page with a verified custom domain such as status.yourcompany.com.

Prerequisites

Access to your DNS settings
A subdomain such as status.yourcompany.com
A paid PixoMonitor plan with custom-domain access

Setup

Add the CNAME record

In your DNS provider, create a CNAME record for the subdomain and point it to pixomonitor.com.

Type	Name (Host)	Value (Target)
CNAME	status	pixomonitor.com

Wait for DNS propagation

Wait until a public DNS lookup for your complete hostname returns the CNAME. DNS propagation time depends on your provider and the record's TTL.

Verify in PixoMonitor

Go to Status Page → Settings → Custom Domain, enter the complete hostname without https://, and choose Verify Domain. PixoMonitor verifies that the CNAME resolves to pixomonitor.com and records the hostname for your account.

Test the public hostname

Open https://status.yourcompany.com and confirm that it serves your status page. DNS verification records the account association; if HTTPS or routing does not become available, contact PixoMonitor support with the verified hostname.

Troubleshooting

CNAME record not found — Wait for propagation and confirm that you created a CNAME, not an A record.
CNAME points elsewhere — Update the target to pixomonitor.com. If Cloudflare proxying hides the CNAME during verification, temporarily use DNS-only mode.
Domain already in use — Remove it from the other PixoMonitor account or use another subdomain.
Verified but not loading — Confirm public DNS first, then contact support; DNS verification alone does not diagnose edge routing or TLS.

Removing a Custom Domain

Go to Status Page → Settings → Custom Domain, choose Remove Custom Domain, and remove the CNAME from your DNS provider if it is no longer needed.

Password Protection

Restrict access to your status page with a password. This is useful for internal status pages that shouldn't be public.

Enable Password Protection

Go to settings

Navigate to Status Page → Settings.

Enable protection

Toggle on Password Protected.

Set a password

Enter a password that viewers will need to access the page.

Save

Click Save. Visitors will now see a password prompt.

Password protection is basic shared-secret access. Do not use a status page to publish confidential system details or credentials.

Announcements

Post announcements on your status page to communicate scheduled maintenance, feature updates, or other news that doesn't require a full incident.

Create an Announcement

Navigate to announcements

Go to Status Page → Announcements.

Create announcement

Click New Announcement and fill in:

Title — Headline for the announcement
Content — Full message content
Type — Info, Warning, Critical, or Maintenance
Schedule — Optional start and end dates

Publish

Set status to Active to display on the status page.

Announcement Types

Type	Use Case	Display Style
Info	General updates, new features	Blue banner
Warning	Potential issues, degraded service	Yellow banner
Critical	Urgent announcements	Red banner
Maintenance	Scheduled maintenance notices	Gray banner

Scheduled Announcements

Set Start At and End At times to automatically show and hide announcements. Perfect for maintenance window notices.

Custom CSS

Advanced users can inject custom CSS to fully customize the status page appearance.

Add Custom CSS

Go to Status Page → Settings and add CSS in the Custom CSS field:

/* Example: Custom font */
body {
  font-family: 'Inter', sans-serif;
}
 
/* Example: Custom colors */
.status-operational {
  color: #22c55e;
}

Custom CSS is applied to the public status page in the browser. Enter only CSS you trust and test the public page after saving changes.

Subscriber Notifications

Visitors can submit an email address and verify ownership through a confirmation link. Verified subscribers receive email for incident creation, later incident updates, and resolution.

Subscriber emails follow the incident lifecycle. Announcements are displayed on the status page but are not subscriber-email events.

Status Page Widgets

Embed status information on your own website with widgets.

Display a simple status badge:

<iframe 
  src="https://pixomonitor.com/api/status/widget?mode=badge" 
  width="200" 
  height="40" 
  frameborder="0"
></iframe>

Display a mini status page:

<iframe 
  src="https://pixomonitor.com/api/status/widget?mode=full" 
  width="400" 
  height="300" 
  frameborder="0"
></iframe>

Parameter	Values	Description
mode	badge / full	Widget size
theme	light / dark	Color theme

Access embed codes from Status Page → Settings → Widget Embed Code for ready-to-use snippets.

SEO Settings

Control how search engines index your status page.

Robots Meta Tag

Option	Description
Index	Allow search engines to index the page
NoIndex	Tell search engines not to index

Google Analytics

Add your Google Analytics ID to track status page visitors:

Go to Status Page → Settings
Enter your Google Analytics ID (e.g., G-XXXXXXXXXX)
Save changes

Public vs. Private Data

The public page is designed for service-health information:

Shown publicly:

Monitor and component names
Component and monitor health
Response times and uptime percentages
Incident history and published post-mortems
Error messages when outage details are enabled
Monitor URLs when Show Monitor URL is enabled

Not part of the public response:

Alert-channel credentials or API secrets
Monitor configuration fields
Escalation-policy configuration

Keep Show Monitor URL disabled for targets you do not want to disclose, and review the public page after changing display settings.

Best Practices

Use descriptive names — Component names should be meaningful to users
Group logically — Organize components by service area
Brand your page — Add your logo and use custom domains
Enable subscriptions — Let users opt-in to notifications
Post updates — Use incidents to communicate during outages
Hide internal monitors — Don't assign internal services to components
Test the public view — Regularly check what users see