Status Pages

Status pages let you communicate service health and incidents to your users in real time. Reoclo automatically monitors your domains and servers, displays component status, and tracks uptime history. When issues occur, you can post incident updates that appear on your public status page.

Each organization gets one status page with custom branding, multiple components, and incident management. The public page is accessible without authentication at a URL you control.

Creating a Status Page

Navigate to Status Pages in the dashboard sidebar and click Create Status Page.

Required Fields

• Title: Your organization or service name (shown at the top of the public page)
• Slug: URL-safe identifier for your public page (e.g., acme-api becomes /s/acme-api)
• Description: Brief explanation of what this status page covers (shown below the title)

Optional Branding

• Logo URL: Full URL to your logo image (displayed in the header)
• Favicon URL: Full URL to your favicon (shown in browser tabs)
• Accent Color: Hex color code for buttons and highlights (e.g., #3b82f6)

Tip

Use a CDN or public image host for logo and favicon URLs. The status page doesn’t upload or store images directly.

Publishing

Status pages start unpublished. While unpublished, the public URL returns a 404. Click Publish when you’re ready to make it accessible.

You can unpublish at any time to temporarily hide the page without deleting it.

Managing Components

Components represent the individual services or infrastructure pieces you want to monitor. Each component displays a status indicator and uptime history on the public page.

Adding Components

From your status page detail view, click Add Component. Choose a source type:

Domain Components

Link a component to one of your verified custom domains. Reoclo automatically monitors the domain’s health and updates the component status based on HTTP checks.

• Display Name: How the component appears on the public page (e.g., “API” instead of api.example.com)
• Source: Select a domain from your organization’s verified domains
• Auto-Incident: Enable to automatically create incidents when the domain fails health checks

When the linked domain goes down, the component status changes to major_outage. When it recovers, status returns to operational.

Server Components

Link a component to one of your BYOS servers. Status reflects the server’s health check state.

• Display Name: Public-facing name (e.g., “US East Database”)
• Source: Select a server from your organization’s server list
• Auto-Incident: Enable to automatically create incidents when the server becomes unreachable

Server components show operational when the server is ACTIVE and major_outage when UNREACHABLE.

Manual Components

Create a component not tied to any Reoclo resource. You control the status manually.

• Display Name: Component name (e.g., “Third-Party Payment Gateway”)
• Initial Status: Set to any status value (see table below)

Manual components are useful for external dependencies or services Reoclo doesn’t monitor directly.

Component Statuses

Status	Meaning	Color
operational	Service is working normally	Green
degraded_performance	Service is slow but functional	Yellow
partial_outage	Some features unavailable	Orange
major_outage	Service is down	Red
maintenance	Planned maintenance in progress	Blue
unknown	Status cannot be determined	Gray

For domain and server components, Reoclo sets the status automatically based on health checks. You can override this by setting a Status Override in the component settings.

Note

Status overrides take precedence over automatic detection. Remove the override to return to automatic monitoring.

Auto-Incident Configuration

Enable Auto-Incident on a component to automatically create incidents when failures are detected.

• Auto-Incident Threshold: Number of consecutive health check failures before creating an incident (default: 3)

When the threshold is reached, Reoclo creates a new incident in the investigating state and links it to the affected component.

Display Order

Components appear on the public page in ascending display order. Lower numbers appear first. Drag components in the dashboard to reorder them.

Managing Incidents

Incidents represent service disruptions or maintenance events. Each incident has a timeline of updates that appear on the public status page.

Creating an Incident

From the Incidents tab on your status page, click Create Incident.

• Title: Brief description of the issue (e.g., “API Latency Spike”)
• Description: Internal notes (not shown publicly)
• Severity: minor, major, or critical
• Affected Components: Select which components are impacted
• Initial State: Usually investigating

The incident appears on the public page immediately after creation.

Posting Updates

Click Add Update on an incident to post a new message.

• Message: What you want to communicate
• State: Current incident state (investigating, identified, monitoring, resolved)
• Visibility: public (shown on status page) or internal (dashboard only)

Public updates appear in reverse chronological order on the status page. Internal updates are only visible to your team in the dashboard.

Tip

Post frequent updates during major incidents. Users appreciate transparency even if there’s no new information. A simple “Still investigating, no ETA yet” is better than silence.

Incident States

State	Meaning
investigating	You’re aware of the issue and diagnosing it
identified	Root cause is known, working on a fix
monitoring	Fix is deployed, watching for stability
resolved	Issue is fully resolved

State transitions are not enforced. You can move directly from investigating to resolved if the issue resolves quickly.

Resolving Incidents

When an incident is resolved, click Resolve or post an update with state resolved. Affected components return to operational status unless they’re still failing health checks.

Public Status Page

Your public status page is accessible at:

https://app.reoclo.com/s/{your-slug}

Replace {your-slug} with the slug you configured. No authentication is required.

What Visitors See

• Header: Your logo, title, and description
• Overall Status: “All Systems Operational” or a summary of active issues
• Components: Each component with current status and 90-day uptime bar
• Active Incidents: Open incidents with all public updates in timeline format
• Recent Incidents: Resolved incidents from the past 7 days

Uptime Bars

Each component displays a 90-day uptime history as a horizontal bar. Each day is represented by a colored segment:

• Green: 100% uptime
• Yellow: 95-99% uptime
• Orange: 90-94% uptime
• Red: Below 90% uptime

Hover over a segment to see the exact uptime percentage for that day.

JSON API

The status page data is also available as JSON for building custom integrations:

https://app.reoclo.com/api/status-pages/{slug}/public

The response includes page metadata, all components with current status, active incidents with public updates, and 90-day uptime data per component.

Troubleshooting

Component Status Not Updating Automatically

Cause: The linked domain or server may not have health checks running, or the component has a status override set.

Fix:

1. Verify the domain or server health checks are running (check the detail page for the linked resource)
2. Check the component settings and remove any Status Override if you want automatic detection

Auto-Incident Not Triggering

Cause: The auto-incident threshold hasn’t been reached, or auto-incident is disabled on the component.

Fix:

1. Check the component settings and confirm Auto-Incident is enabled
2. Verify the threshold setting (default: 3 consecutive failures)
3. Check the domain or server health check history to see if failures are being detected

Public Page Shows 404

Cause: The status page is unpublished, or the slug is incorrect.

Fix: Go to Status Pages in the dashboard and click Publish. Verify the slug matches the URL you’re trying to access.

Incident Updates Not Appearing on Public Page

Cause: The update visibility is set to internal.

Fix: Edit the incident update and change visibility to public. Only public updates appear on the status page.

Logo or Favicon Not Displaying

Cause: The URL is incorrect, the image host blocks hotlinking, or the URL is not publicly accessible.

Fix: Verify the URL loads in a browser. Use a CDN or public image host that allows hotlinking. Ensure the URL uses HTTPS.

Next Steps

• Set up custom domains to monitor domain health on your status page
• Configure your deployments with health checks for better status detection
• Access control: Understand who can manage your status page