View the status page

Once your status page is published, it becomes the single source of truth for real-time service health and incident updates. Your subscribers can instantly see the operational status of your key components, search for specific services, and review both current and historical updates, all in one place. Status page capability in JSM is exclusive to Enterprise plans.

What subscribers see on a live status page

• Branding and customization: The page reflects your organization’s branding, theme, and layout choices, reinforcing trust and professionalism.

• Overall status banner: At the top, a clear banner communicates the current state, allowing stakeholders to know at a glance if there are any issues.

• Component list: Each service or system (e.g., API Gateway, Management Portal, Data Storage) is listed with its current status. Components with incidents are highlighted, making it easy to spot issues.

• Tabs at the top

  • Live status: Shows the current health of all components

  • History: Lets users review past incidents and uptime.

• Search and filters: A search bar allows you to quickly find specific components or updates, streamlining the experience for large or complex environments.

• Subscription to updates: Stakeholders can subscribe to updates via email, ensuring they’re notified about incidents or changes that matter to them.

Your live status page is always accessible to your selected audience, thus keeping them informed every step of the way.

How are incidents showcased on status pages

When multiple incidents are reported for the same component simultaneously, they are displayed based on a clear and consistent logic that determines the status and color to be displayed for that component. This ensures that your users always view the most accurate and relevant information about the health of your services.

• Status determination: If multiple incidents are ongoing for a single component, the status corresponding to the most severe component status will be displayed. For example, if a component is marked as ‘degraded performance (yellow) for one incident and the same component for another incident is marked as ‘major outage’ (red), the component will be shown as 'major outage’ (red), since that represents the most significant impact.
  
  If there are multiple updates for the same incident affecting a component, and the initial update marks the component as experiencing a major outage, but later updates downgrade the status to a partial outage, the component’s uptime status will still reflect the most significant impact. It will continue to show “major outage,” highlighted in red.
  
  

• Color display: The color of the component will update to reflect the most severe ongoing incident. The status colors can be as follows, or can be customized based on your preference.

  • Green for operational

  • Yellow for degraded performance

  • Orange for partial outage

  • Red for major outage
    
    

• Update timing: The component’s status and color are only updated when an incident update is sent from Jira Service Management (JSM). This ensures that the displayed status always matches the latest information provided by your incident response team.
  For example:

  • Incident A is ongoing → component shows ‘degraded performance’ (yellow).

  • Incident B is reported for the same component → component status immediately updates to ‘major outage’ (red).

  • Once incident B is resolved, but incident A remains open, the component status reverts to ‘degraded performance’ (yellow).

This approach ensures that your customers are always informed of the most critical issue affecting a component, even if multiple ongoing incidents are present.

How to read uptime %

Uptime % = [(Total Time − Downtime) ÷ Total Time] × 100

For example for 30 Days:
Total Time (30 days)- 43,200 minutes
Downtime- 90 minutes
Uptime %-(43,200 − 90) ÷ 43,200) × 100 = 99.791%