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

Component Groups

For complex systems, organize components into groups:

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

Status Page Settings

Customize the appearance and behavior of your status page.

Basic Settings

Display Options

Layout Options

Theme Options

Custom Domains

Instead of using the default pixomonitor.com/status/yourpage URL, you can host your status page on your own domain like status.yourcompany.com. This creates a more professional, branded experience for your users and keeps everything under your company's domain.

Why Use a Custom Domain?

• Professional appearance — Your status page URL matches your brand
• Trust — Users see your domain, not a third-party service
• Consistency — All your web properties share the same domain
• SEO — Build domain authority under your own brand

Prerequisites

Before setting up a custom domain, make sure you have:

1. Access to your domain's DNS settings — You'll need to add a CNAME record through your domain registrar or DNS provider (e.g., Cloudflare, GoDaddy, Namecheap, Route 53)
2. A subdomain to use — We recommend status.yourdomain.com, but you can use any subdomain
3. A paid PixoMonitor plan — Custom domains are available on paid plans

Step-by-Step Setup

status.yourcompany.com

nslookup status.yourcompany.com

Troubleshooting

"CNAME record not found"

Cause: DNS hasn't propagated yet, or the CNAME record wasn't added correctly.

Solutions:

• Wait longer (up to 48 hours) and try again
• Double-check that you added a CNAME record, not an A record
• Verify the CNAME target is exactly pixomonitor.com
• Make sure you entered the subdomain correctly (e.g., status, not status.yourcompany.com)

"CNAME record found but does not point to pixomonitor.com"

Cause: Your CNAME record points to a different target.

Solutions:

• Update your CNAME record to point to pixomonitor.com
• Remove any conflicting A records for the same subdomain
• If using Cloudflare proxy (orange cloud), try setting it to "DNS only" (gray cloud) during setup

"This domain is already in use"

Cause: Another PixoMonitor account has already claimed this domain.

Solutions:

• If you own that account, remove the domain from it first
• Contact support if you believe this is an error
• Use a different subdomain (e.g., statuspage.yourcompany.com instead of status.yourcompany.com)

SSL certificate not working

Cause: Certificate provisioning can take a few minutes after domain verification.

Solutions:

• Wait 5-10 minutes after verification
• Clear your browser cache and try again
• If using Cloudflare, ensure SSL mode is set to "Full" or "Full (Strict)"

Removing a Custom Domain

To remove a custom domain and revert to the default URL:

1. Go to Status Page → Settings → Custom Domain
2. Click Remove Custom Domain
3. Optionally, delete the CNAME record from your DNS provider

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

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

Announcement Types

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;
}

Subscriber Notifications

Allow users to subscribe to status updates. Subscribers receive email notifications when incidents are created, updated, or resolved.

How Subscriptions Work

1. Visitors click "Subscribe" on your status page
2. They enter their email address
3. When incidents occur, subscribers receive automatic email updates

Notification Events

Subscribers are notified when:

• New incidents are created
• Incident status changes (Investigating → Identified → Resolved)
• Incident severity changes
• Updates are posted to incidents

Status Page Widgets

Embed status information on your own website with widgets.

Badge Widget

Display a simple status badge:

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

Full Widget

Display a mini status page:

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

Widget Options

SEO Settings

Control how search engines index your status page.

Robots Meta Tag

Google Analytics

Add your Google Analytics ID to track status page visitors:

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

Public vs. Private Data

The status page only shows safe, public information:

Shown publicly:

• Monitor names
• Component status (UP/DOWN)
• Response times
• Uptime percentages
• Incident history
• Error messages (if enabled)

Never shown:

• Monitor URLs (optional)
• Configuration details
• API keys or secrets
• Internal error details
• Escalation policies

Best Practices

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