Status Pages

Status Pages let you publish public (or internal) status pages so customers and users can see the health of your services and read about incidents and maintenance without logging into AtlasAI. This is useful for SaaS products, APIs, and internal platforms.

Key features

• Multiple status pages — Create more than one page (e.g. one per product or region).
• Components — Represent services or systems (e.g. “API”, “Dashboard”, “Payments”). Each has a status: Operational, Degraded, Partial outage, Major outage, Under maintenance.
• Component groups — Group components (e.g. “Core services”, “Integrations”) for clearer layout.
• Incidents — Publish incident updates (investigating, identified, monitoring, resolved) with impact and message. Link incidents to affected components.
• Maintenance windows — Schedule and publish planned maintenance with start/end times and affected components.
• Public or private — Pages can be public (anyone with the link) or require authentication, depending on configuration.
• Subdomain — Each page can have a subdomain (e.g. status.yourcompany.com) for a stable, shareable URL.

How to access

In the Tenant Plane sidebar, open Status Pages. You need the status_pages feature (included in some plans or as an add-on). If you don’t see it, check your subscription or contact your admin.

How to create a status page

1. Go to Status Pages and click Create status page (or New).
2. Fill in:
   • Name — e.g. “Product API Status”
   • Subdomain — e.g. api-status (forms the public URL, e.g. api-status.atlastechlab.com or your custom domain)
   • Description — Short line shown on the page
   • Public — Allow unauthenticated access (check) or restrict to logged-in users (uncheck)
3. Click Create or Save.

Adding components

Components are the building blocks (services/systems) you report on.

1. Open your status page in the editor.
2. Add a component:
   • Name — e.g. “API”, “Web app”, “Database”
   • Description (optional)
   • Group (optional) — Put it in a group (e.g. “Core”) for layout
   • Display order — Order within the page
3. Set status for each component:
   • Operational — Normal
   • Degraded performance — Issues but working
   • Partial outage — Some impact
   • Major outage — Significant impact
   • Under maintenance — Planned work

You can update component status when an incident occurs or when you start/end maintenance.

Publishing incidents

When something goes wrong, publish an incident so the status page shows it.

1. On the status page, open Incidents (or the incident section).
2. Click New incident (or Create incident).
3. Enter:
   • Title — e.g. “API latency and errors”
   • Impact — None, Minor, Major, Critical
   • Status — Investigating, Identified, Monitoring, Resolved
   • Message — What you’re telling users
   • Affected components — Select which components this incident affects
4. Save. The incident appears on the public status page.
5. As you progress, add updates (new message and status) so users see the latest. When fixed, set status to Resolved.

Maintenance windows

For planned maintenance:

1. In the status page, open Maintenance (or equivalent).
2. Create a maintenance window:
   • Name and optional description
   • Scheduled start and end
   • Affected components
3. Save. The window can show as Scheduled, In progress, or Completed. The status page can show “Under maintenance” for those components during the window.

Linking to AtlasAI incidents (optional)

Depending on your deployment, you may be able to link a Status Page incident to an AtlasAI incident (from the Incidents module). That way, when you resolve the incident in AtlasAI, you can update the status page incident in one place. Check the UI for “Link to incident” or similar when creating or editing a status page incident.

Public URL and sharing

• The public URL is usually based on the page’s subdomain (e.g. https://<subdomain>.<your-domain>/status or similar). Your admin or deployment docs will state the exact pattern.
• Share this URL with customers or internal users so they can check status without logging in (if the page is public).

Summary

See also

• War room & major incidents — Coordinate during major outages; can tie to status page
• Incidents — AtlasAI incident lifecycle
• Command Center — Operations overview