How to Setup Self-Hosted Status Page?

A self-hosted status page lets you display the real-time health of your website, APIs, and servers under your own brand and domain — building user trust, reducing support tickets, and showing transparency during incidents. This guide walks you through every step to set one up in MonitoringDaddy.

What Is a Self-Hosted Status Page?

A self-hosted status page is a public (or private) web page that reflects the live operational status of your services. Instead of pointing users to a generic third-party URL, you host it on a subdomain you own — for example, status.example.com — while MonitoringDaddy powers the uptime data behind it.

The page updates automatically based on your existing monitors. When a service goes down, the status page reflects that in real time. When it recovers, the page turns green again — all without any manual action from your team.

Why Public Status Pages Matter

A well-maintained status page delivers measurable business value beyond just showing a green dot:

• Transparency builds trust. Users who can check your status page themselves are less likely to assume the worst — or flood your inbox.
• Fewer support tickets. During incidents, a live status update cuts inbound tickets significantly because users already know you are aware and working on it.
• Professional image. A branded status page signals that you take reliability seriously — an expectation from SaaS buyers, enterprise clients, and API consumers.
• Incident accountability. Historical uptime data on the page demonstrates your track record of reliability to prospects and customers.
• SEO and direct traffic. A public, indexed status page can appear in search results when users look for your service health.

How Status Pages Work in MonitoringDaddy

MonitoringDaddy connects your status page directly to your existing monitors. Each monitor you attach feeds its live check results — up, degraded, or down — into the status page display. You do not need to maintain the page manually; the monitoring engine does it for you.

If you do not yet have monitors configured, start with website uptime monitoring first, then return here to attach those monitors to your status page.

Before You Begin

• Have at least one active monitor set up in MonitoringDaddy (website, API, server, or SSL).
• Decide whether the page will be public, private, or password-protected.
• Choose a subdomain for your custom domain if you plan to use one (for example, status.example.com).
• Have access to your domain's DNS control panel if you want a custom domain.
• Prepare your brand logo and favicon files (optional but recommended).

Step-by-Step: How to Set Up a Self-Hosted Status Page

Step 1: Name Your Status Page

Navigate to Status Pages in the MonitoringDaddy dashboard and click Create Status Page. Enter a name that clearly identifies the service or organization this page represents.

This name appears in the browser tab and as the primary heading on the live status page.

Step 2: Set the Slug

The slug is the URL path used to access your status page on the MonitoringDaddy-hosted URL before a custom domain is applied. Choose a short, lowercase, hyphen-separated identifier.

This means your page will initially be reachable at monitoringdaddy.com/status/example until you configure a custom domain.

Step 3: Attach Monitors

Select the monitors you want to display on this status page. Each monitor you select will appear as a service row showing its current status and recent uptime history.

You can attach monitors from any type: website, API endpoint, server agent, SSL certificate, or domain. Choose only the monitors relevant to what your users care about — avoid cluttering the page with internal or staging monitors.

Step 4: Upload a Logo (Optional)

Upload your brand logo to make the status page feel like a native part of your product. Supported formats include PNG and SVG. The logo appears in the header of the status page.

Step 5: Upload a Favicon (Optional)

A favicon appears in the browser tab when someone has your status page open. Upload a square PNG or ICO file (16×16 or 32×32 pixels). This small detail significantly improves the professional appearance of your branded status page.

Step 6: Enter Your Website URL

Provide your primary website URL. This is used for linking back to your main site from the status page header.

Step 7: Add a Contact URL

Give users a way to reach you during an incident. MonitoringDaddy supports multiple contact URL formats:

This link appears as a "Contact" or "Support" button on the status page, letting affected users reach out without searching for your contact details.

Step 8: Choose Privacy Settings

Set who can access your status page:

• Public — Anyone with the URL can view the page. Best for customer-facing services.
• Private — Only you (the account owner) can access the page. Useful for internal monitoring dashboards.
• Password — Visitors must enter a password to view the page. Suitable for partners or specific teams.

Step 9: Set Meta Title and Meta Description

These fields control how your status page appears in search engine results and link previews. Fill them in even if you plan to use the Noindex option — they still affect browser tab titles and social sharing previews.

Step 10: Configure Noindex

Enable Noindex if you do not want search engines to crawl or rank your status page. This is common for password-protected or internal pages. Leave it OFF if you want the page indexed — a public, indexed status page can build trust with prospects who search for your service reliability.

Step 11: Configure a Custom Domain

Hosting your status page on your own subdomain is strongly recommended for branding consistency. Enter your intended custom domain:

Then add the following DNS record in your domain registrar or DNS control panel:

DNS changes typically propagate within a few minutes to a few hours depending on your provider's TTL settings. Once propagation is complete, MonitoringDaddy automatically detects the DNS record and activates the custom domain — no additional steps are required.

Step 12: Add Custom CSS (Optional)

Inject custom CSS to override the default status page styles and match your brand colors, fonts, or layout preferences. The CSS is scoped to the status page container.

You can change background colors, font sizes, card styles, and more. Inspect the live page in your browser's developer tools to identify specific selectors to target.

Step 13: Add Custom JavaScript (Optional)

Inject custom JavaScript to add analytics tracking, chat widgets, custom event listeners, or any other behavior you need on your status page.

JavaScript is executed after the page loads, so it will not interfere with status data rendering.

Recommended Configuration

For a typical customer-facing SaaS or web application, this configuration is a solid starting point:

Best Practices for Status Pages

Communicate During Incidents

A status page is most valuable during an outage. Use incident communication features to post real-time updates — "Investigating," "Identified," "Monitoring," and "Resolved" — so users know you are actively working on the issue. Regular updates, even brief ones, dramatically reduce support ticket volume.

Keep Your Monitor List Focused

Only surface monitors your users depend on. Showing too many internal or infrastructure monitors can confuse customers. Aim for service-level monitors (website, API, login, checkout) rather than raw server metrics.

Enable Subscriber Notifications

Allow visitors to subscribe for email notifications when your service status changes. This turns your status page from a passive dashboard into an active communication channel — subscribers get proactively notified instead of having to check manually during incidents.

Test Your Status Page Before Launch

Before announcing the page publicly, verify that all attached monitors are reporting correctly, the custom domain resolves over HTTPS, the logo and favicon display properly, and the contact link works. Run a test by temporarily pausing a monitor to confirm the status page reflects the change.

Troubleshooting

Next Steps

With your status page live, the next priority is ensuring your monitors are comprehensive. Add website uptime monitoring for every critical endpoint you expose to users. Review the full monitoring guide for SSL, domain, and server coverage. When your monitoring setup grows, explore MonitoringDaddy's pricing plans to find the tier that fits your scale.

Frequently Asked Questions