Status Pages

Status pages help you communicate outages and planned maintenance transparently.

They are customer-facing pages that show a live overview of service health, plus a short history of recent incidents and maintenance windows.

What a status page shows

• Overall state (Operational / Degraded / Maintenance)
• A list of Services (websites) for the customer
• Optional Recent History (incidents + maintenance windows)

How the state is calculated

Uptimeify derives the public state from two signals:

• Open incidents → the affected service is shown as Degraded
• Active maintenance windows (and no open incidents) → the service is shown as Maintenance

If neither applies, the service is Operational.

Create a status page

In the app, go to Admin → Status Pages → Create.

You can configure:

• Customer (required)
• Public name (page title)
• Slug (used for friendly URLs)
• Description (optional)
• Visibility
  • public: anyone can view the page
  • customer_members_only: login required + access to the customer
• Published: disable to temporarily hide the page without deleting it

URLs

Each status page is reachable via:

• /status/:id (always available)
• /status/:slug (based on the configured slug)

Custom domain (optional)

You can connect a hostname like status.example.com to a status page.

When you set a custom domain, Uptimeify will provide a TXT record for verification:

• TXT name: _uptimeify-verify.<your-hostname>
• TXT value: <token>

Steps:

1. Add the TXT record to your DNS.
2. Wait for DNS propagation.
3. In Admin → Status Pages, click Verify on the domain.
4. Once verified, click Activate.

Notes:

• Verification checks the TXT record (token match).
• A hostname can only be bound to one status page.

Recent history settings

In the status page edit form, you can decide what appears in Recent History:

• Incidents
• Maintenance windows

This only affects the history list. Live indicators (like “service is currently in maintenance”) are still shown.

Troubleshooting

“Status page not found”

• Check whether the page is Published.
• If visibility is customer_members_only, you must be logged in and have access to the customer.

“TXT verification failed (token not found)”

• Confirm the TXT record name is exactly _uptimeify-verify.<your-hostname>.
• Ensure the TXT value matches the token provided by Uptimeify.
• Give DNS a bit more time to propagate.