Status Pages
Create public or private status pages to keep your team and customers informed about service health.
Status pages give your users and team a single place to check the health of your services. IonHour status pages are fully customizable, support real-time updates, and can be public, private, or password-protected.
Creating a Status Page
- Navigate to Status Pages in the sidebar.
- Click Create Status Page.
- Enter a name and a slug (URL-safe identifier, e.g.,
my-company). - Choose a visibility level.
- Save.
Your status page is immediately available at https://status.failsignal.com/your-slug.
Visibility Levels
| Level | Who can see it |
|---|---|
| Public | Anyone with the URL. No authentication required. |
| Password-Protected | Visitors must enter a password before viewing. |
| Private | Only workspace members can access it (requires login). |
Password-protected pages are useful for sharing with customers or partners who shouldn't have full workspace access but need visibility into service health.
Components
Components are the building blocks of your status page. Each component represents a service, endpoint, or system that you want to display.
Adding Components
- Open your status page settings.
- Go to the Components section.
- Click Add Component.
- Enter a name and optional description.
- Optionally link it to a check or project to show live status.
When a component is linked to a check, its status updates automatically based on the check's health. Unlinked components show a static status.
Component Groups
Organize related components by assigning a group name. Components with the same group name are displayed together under a shared heading. This is useful for grouping by team, service tier, or environment.
Reordering
Drag components or use the reorder endpoint to control the display order. Components are sorted by their position value (lower numbers appear first).
Uptime Bar
Each component can display an uptime bar — a visual history of the component's availability over a configurable period (default: 90 days, configurable up to 365 days). Toggle this per-component with the Show Uptime Bar setting.
Component Status
When linked to a check, component status is derived automatically:
| Status | Meaning | Color |
|---|---|---|
| Operational | Everything is working normally | Green |
| Degraded Performance | Service is running but impacted (e.g., dependency issues) | Yellow |
| Partial Outage | Some functionality is unavailable | Orange |
| Major Outage | Service is down | Red |
| Under Maintenance | Planned maintenance is in progress | Blue |
Announcements
Announcements let you communicate about incidents and maintenance directly on your status page. They're separate from IonHour's internal incident system — announcements are the public-facing narrative you control.
Creating an Announcement
- Open your status page settings.
- Go to the Announcements section.
- Click New Announcement.
- Enter a title and initial update (the first message your users will see).
- Set the impact level and optionally link affected components.
Announcement Lifecycle
Each announcement has a status that reflects the investigation progress:
| Status | Meaning |
|---|---|
| Investigating | You're aware of the issue and looking into it |
| Identified | The root cause has been found |
| Monitoring | A fix has been applied and you're watching for recurrence |
| Resolved | The issue is fully resolved |
Impact Levels
| Impact | When to use |
|---|---|
| None | Informational update, no service impact |
| Minor | Small impact, most users unaffected |
| Major | Significant impact, many users affected |
| Critical | Service is down or severely degraded |
Announcement Updates
Add updates to an announcement as the situation evolves. Each update captures:
- A status change (e.g., Investigating to Identified)
- A message explaining what changed
Updates are displayed in chronological order on the status page, giving visitors a clear timeline of your response.
Scheduled Maintenance
Create announcements with scheduled times to notify users about upcoming maintenance windows. Set the scheduledFor and scheduledUntil fields when creating an announcement.
Scheduled maintenance appears in a dedicated section on the status page, separate from active incidents. Subscribers are notified when maintenance is scheduled and when it completes.
Branding
Customize the look and feel of your status page to match your brand.
| Setting | Description |
|---|---|
| Logo | Your company logo (URL to an image) |
| Primary color | Hex color for accent elements (e.g., #4A90D9) |
| Background color | Hex color for the page background |
| Favicon | Custom favicon URL |
| Header HTML | Custom HTML injected into the page header (max 10,000 characters) |
| Footer HTML | Custom HTML injected into the page footer (max 10,000 characters) |
Custom Domain
Point your own domain (e.g., status.yourcompany.com) to your IonHour status page.
Setup
- Open your status page settings.
- Enter your custom domain in the Custom Domain section.
- IonHour generates a verification token.
- Add a DNS TXT record with the verification token to prove domain ownership.
- Click Verify Domain.
Once verified, visitors to your custom domain will see your branded status page.
Subscriber Notifications
Visitors can subscribe to your status page to receive updates when the status changes.
Email Subscriptions
- Visitor enters their email on the status page.
- IonHour sends a confirmation email with a verification link.
- Once confirmed, the subscriber receives notifications on status changes and announcements.
- Each email includes an unsubscribe link.
Webhook Subscriptions
For programmatic integrations, subscribers can provide a webhook URL instead of an email. IonHour sends HTTP POST requests to the webhook when the status changes.
Component-Level Subscriptions
Subscribers can optionally select specific components they care about. They'll only receive notifications for those components, reducing noise for users who only depend on a subset of your services.
Feeds and Embeds
RSS and Atom Feeds
Your status page has built-in RSS and Atom feeds for incidents:
- RSS:
https://status.failsignal.com/your-slug/feed.rss - Atom:
https://status.failsignal.com/your-slug/feed.atom
Status Badge
Embed a status badge on your website or README:
https://status.failsignal.com/your-slug/badge.svg
The badge dynamically reflects the current overall status.
Embeddable Widget
IonHour generates a JavaScript widget you can embed on any page:
<script src="https://status.failsignal.com/your-slug/widget.js"></script>
The widget shows a compact view of your service status.
Real-Time Updates
Status pages use Server-Sent Events (SSE) to push updates to connected browsers in real time. When a check status changes or an announcement is published, visitors see the update without refreshing the page.
Best Practices
- Link components to checks. Manual status updates are error-prone. Let IonHour update component status automatically from your monitoring checks.
- Use component groups to organize by service or team. A flat list of 20 components is hard to scan.
- Write announcement updates as they happen. Frequent, honest updates build trust with your users, even during outages.
- Set up a custom domain. A branded status page (
status.yourcompany.com) looks more professional than a generic subdomain. - Enable subscriber notifications. Proactive communication reduces support tickets during incidents.
- Configure uptime history. 90 days is a good default. Shorter windows (30 days) work for rapidly evolving services. Longer windows (365 days) demonstrate long-term reliability.