Does Statuspage check whether your app is down?
Detection comes from your team or a connected monitoring tool. Statuspage gives you a place to report the incident and share updates with customers.
Start with parts a customer can recognize, such as Sign-in, Booking and Confirmation emails. Statuspage calls these parts components. When one stops working, you can mark the affected component and explain what customers should expect.
Who should be able to see the page or post on it?
Choose the audience before you add details. Public pages are for anyone who needs the update. Private pages restrict access using the settings you choose. Audience-specific pages can show different components to different groups.
A subscriber receives updates. A team member can work on the page according to their access. Check who can post or change settings and which plans give you narrower roles.
Private pages on eligible plans can admit viewers from approved network addresses. Before sharing the page, try it from both an allowed and an excluded account or network, depending on the access settings you chose.
A public trial is visible to logged-in team members. Activate it on a public plan, including Free, before you depend on customers being able to open it.
What do you put in the first incident update?
State the customer-facing problem and when you will update people again. You can say “Some customers can’t finish booking. We’re investigating. Next update by 14:30 UTC” before you know the cause.
Select the affected component and decide whether to notify subscribers. The incident editor offers that notification choice when a component is affected. Available channels depend on the page’s plan and settings. SMS does not send for every kind of update.
Draft a rehearsal message without publishing it. Keep real recipients out of any later test page. When a fix is ready, check the affected customer action before marking the incident resolved.
What determines the cost of a Statuspage plan?
The price depends on the type of page and its plan. Atlassian counts people who manage the page separately from people who subscribe to its updates. Pages have separate subscriptions.
Private and audience-specific pages have different plans. Check viewer or group limits, what the page can show and the notification channels before choosing. The plan for a public page does not tell you what private access costs.
| Public plan | Published capacity |
|---|---|
| Free | 100 subscribers, two team members and 25 components. |
| Hobby | US$29 per month, 250 subscribers, five team members and a custom domain. |
What can you take if you move the status page?
An admin can export email, SMS and webhook subscriber lists as CSV or JSON. Slack subscribers are outside that export. The Manage API can retrieve incidents and their updates separately.
Decide what incident history and subscriber permissions you need to preserve. Keep exported contacts private. Copy the component list and the instructions for who can post. Verify the new page’s address and subscriber setup before you switch the link customers use.
Treat the management key as a credential for the people or services that update the page. A private page’s information should stay behind the intended access controls.