ATStatus
ATStatus WikiLoading documentation...

Incident Display Position

Control where active incidents are displayed on your public status page.

Overview

By default, active incidents appear at the top of your status page for maximum visibility. However, you can customize this position based on your preference and use case.

Available Positions

1Top (Default)

Incidents appear at the very top of the status page, above everything else.

🔴 Active Incidents
Overall Status
Component List
History

Best for: Critical incident visibility, immediate user awareness

2Below Status

Incidents appear after the overall status but before the component list.

Overall Status
🔴 Active Incidents
Component List
History

Best for: Balanced visibility, showing overall status first

3Below Components

Incidents appear after the component list, at the bottom of the main content.

Overall Status
Component List
🔴 Active Incidents
History

Best for: Component-focused pages, detailed service status

How to Configure

  1. Log in to your admin panel
  2. Navigate to Admin → Features
  3. Find the Incident Display Position setting
  4. Select your preferred position from the dropdown:
    • top - At the top of the page
    • below_status - Below the overall status
    • below_components - Below the component list
  5. Click Save Changes
Instant Effect

Changes take effect immediately after saving. No rebuild or restart required.

API Configuration

You can also configure the incident position via the Features API:

PUT /api/features
Content-Type: application/json
Authorization: Bearer <your-api-key>

{
  "incidentPosition": "below_status"
}

// Response
{
  "success": true,
  "data": {
    "incidentPosition": "below_status",
    // ... other settings
  }
}

Valid Values

ValuePosition
"top"Top of page (default)
"below_status"Below overall status
"below_components"Below component list

Component Status Behavior

Regardless of where incidents are displayed, they still affect component status:

  • Linked components automatically show "Partial Outage" status
  • Parent groups of affected components also reflect the incident status
  • Overall status is calculated based on the worst component status
Visual Consistency

The incident display position only changes where the incident card appears. Component status indicators always update regardless of incident position.

Recommendations

Use CaseRecommended PositionReason
Public SaaS status pageTopUsers want to immediately know about issues
Internal IT dashboardBelow StatusBalance between overview and detail
Multi-service platformBelow ComponentsFocus on which services are affected