What is a service status page?

How public and private status pages communicate incidents, scheduled maintenance, and service availability, and where to use monitoring automation.

Best practices
Illustration of service health and status

A customer whose payment request just timed out wants to know whether to retry. The on-call engineer needs the failed request, the region, and the logs. A service status page answers the customer’s question with the facts the team can share. It explains which service is affected, what users can expect, and when another update is due.

A status page can also announce planned maintenance and retain a history of published incidents. Stripe and GitHub both have public examples. Atlassian’s product is called Statuspage. Teams can publish a status page using that product or another implementation. Atlassian Statuspage documentation

Public and private status pages

A public status page is accessible without a sign-in. Name components in terms users recognize, such as Sign-in or Payments API. Show the current component status alongside incident updates and planned maintenance, with dates and affected services where available.

A private status page limits access to authorized staff or customers. The controls depend on the implementation. A page might require a login or restrict access by network. Giving different groups access to different components requires a corresponding permission model. A noindex instruction governs indexing for search engines that support it. The page itself still needs access controls. Atlassian page types · Google Search Central on noindex

Who uses a status page?

  • A solo developer can keep the current state and incident history of an app in one place and choose whether customers need access.
  • Engineers can share a high-level view of the app or CDN while retaining detailed dashboards for investigation.
  • Support and sales can work from the same confirmed update as engineering when a customer asks about impact.
  • Operations leaders can review availability for key services with the measurement window in view. Contractual SLA reporting also requires the agreement’s own calculation rules.

Five reasons to maintain a status page

1. Answer repeat support questions in one place

Once an issue is known, a customer who finds the page can see whether it matches what they are experiencing. Give the affected service, a workaround if one exists, and a time for the next update. How much this reduces repeat tickets depends on whether users can find the page and whether the information stays current.

2. Automate the changes you can explain

A monitoring integration or API can update a component when the mapping is defined and the tool supports it. Decide how it handles alerts, missing observations, and recovery. A timeout can prompt an investigation before there is enough evidence to describe customer impact. Publish the confirmed scope and progress separately, and check how subscriber notifications are configured. Atlassian’s automation guide

3. Give users a permanent place to look

GitHub’s page shows the condition of individual services and keeps incident updates together. Link to the page from the places where users look for help. An email or a social post can then point readers to the same update. GitHub Status

4. Put historical availability in context

A prospective customer can use incident history and availability figures to understand how a service has operated. Explain which components and period the figure covers, how missing data appears, and how maintenance is treated. Compare the displayed number with an SLA only when the indicator, window, and exclusions line up. Atlassian’s guide to component uptime history

5. Keep an update channel reachable during an outage

A separate address gives users a place to look when the main site is down. GitHub uses githubstatus.com. Check what the status page and its publishing tools still share with the application, including DNS, hosting, and the identity provider. Test the view from outside your network and make sure an on-call responder can publish if the usual sign-in path is unavailable.

If a Guance HTTP probe fails, check which location ran it, which request failed, and the time window. Cross-check server or user data before putting the scope in a public update. One probe result describes that attempt.

Teams using Guance Custom Status Page can publish business services from a workspace. Each displayed service is linked to an enabled SLO without grouping dimensions. Incident and maintenance records use associated public notes from that workspace. The SLO figure follows the linked evaluation window, so a point on a 90-day trend can represent the preceding 30 days if that is how the SLO is configured. Guance’s own service status page reports on Guance’s platform.

Frequently asked questions

How does a status page differ from a monitoring dashboard?

An engineering dashboard exposes signals such as CPU and request errors for investigation. A status page explains which user-facing services are affected and what has changed. Give a time for the next update when you do not yet have a reliable recovery estimate.

Is a status page worth keeping for a small service?

A short list of the services people use and a place to post maintenance can be enough to start. Assign someone to keep it current. The effort and benefit depend on the service and how customers use the page.

Should updates be automatic or manual?

A well-defined rule can update a component from a stable input. Have the person responsible for incident communication confirm customer impact, progress, and recovery before publishing those details. A template can supply the structure.

How much incident history should be public?

Include what readers need to understand the impact and recovery, such as affected features and times. Keep internal investigation notes, customer data, and sensitive security details in an access-controlled channel.

References

Get a tailored plan

Contact us

Join the community

Scan with WeChat
to join the community

Try Guance

Start online and pay only for what you use.

Get started

Choose a Guance plan

Code hosting