This guide is meant to be a one-stop shop for a high-level overview of Statuspage. We hope this helps new and potential users get familiar with our product, and discover new ways of using Statuspage. You'll find links to more detailed knowledge base articles embedded throughout this guide.
Teams that use Statuspage
Support teams, ops teams, and IT teams use Statuspage to communicate incidents and outages. Bring your team together and focus on the important things using Statuspage.
Support teams - Deflect support tickets by using Statuspage to communicate with your customers when you're down. Don't leave your customers in the dark and don't bog down your support team with repeat tickets. This leads to angry customers, and a burnt-out support team.
Operations teams - Pipe your performance metrics and system status into Statuspage so your team has a dedicated place to reference any time.
IT teams - Employees and students are becoming more and more dependent on workplace/school technology. Keep them in the loop when servers and systems are down.
How to roll out Statuspage
Set expectations with your team, and communicate with your customers so they know what's coming.
Define your page type - Make sure you know how you intend to use Statuspage. Is this for internal or external communication? Should everyone receive the same updates or do certain issues only affect certain end-users.
Rally the troops - Define which team(s) and roles own the Statuspage. This is crucial for initial implementation and longevity. Better to sort this out Day 1, before the first live incident.
Adopt a culture of transparency - Gone are the days when downtime was something you kept hush-hush. Customers expect a certain level of transparency these days. Read up on the Service Recovery Paradox.
Embed your system status in-app - Using our Status embed, you can embed your system status directly in your website, app, or help center. Anytime an incident is posted, a banner will surface on your site.
Public status pages are for communicating with external customers. Private status pages are for communicating internally with employees and stakeholders. Audience-specific pages are for prespecified users and groups to view.
Public page functionality - Public pages are viewable by anyone with an internet connection. No authentication is required. Here are some examples, status.dropbox.com, status.twilio.com, status.newrelic.com.
Public Page trials have no time limit. The only restriction is that you must be a logged-in team member in order to view the page.
Private page functionality - Private pages are hidden behind authentication. Page viewers must log in with credentials in order to view the page. We support SAML 2.0 and Google Auth for private pages. Details on private pages.
Private Page trials are limited to 30 days with full functionality.
Audience-specific page functionality - Audience-specific pages have set permissions for what users and groups can view and what notifications they can receive. Choose what components and information is visible so that users and groups see only what is of interest to them.
You can be up and running with a new status page in a matter of minutes.
Create components - Components are the functioning pieces of your website or application such as your API, mobile app, help center, and admin tool. Click Components from the sidebar to create your components. Details on components.
Backfill historical incidents - If you're migrating to Statuspage from another tool, you can add your previous incidents as a "Backfilled incident". Details on backfilling.
Invite a team member - Recruit others to help. Invite your support team, ops team, or others so they can also update the status page when things go wrong. Invite team members by clicking your avatar in the bottom left corner of your page > User management > Add user.
Subscribe to incident updates - Click View status page from the left sidebar when signed in and then click Subscribe. Updates to incidents will be sent out to all subscribers. (more on subscribers below)
Create a test incident - From within the Incidents section in the left sidebar you can create a test incident. Give it a title, a brief message and leave it in the "Investigating" stage. Once you click Create Incident, an incident will be posted on your status page and a notification sent to your test subscribers (more on incidents below).
Setting up Statuspage
Go to Your page > Page info to configure global settings like your timezone, service name, Google Analytics tracking, notifications, and billing info.
Service name - This is the name we use in SMS and Email notifications. Usually it's the name of your company or product.
Notifications - Turn notification on/off for events such as long-running incidents, billing receipts, and issues with external accounts used for integrations. Details on account notifications.
Google Analytics tracking - Measure traffic to your page by inputting a Google Analytics tracking code. Details on tracking.
Configure an invoice recipient - Your accounting team will probably want receipts. Set their email address as an invoice recipient. Details on receipts.
Components allow you to be more granular with reporting your system status. They are the functioning pieces of your application. If you want, you can automate your components, or surface a third-party component on your page.
Component groups - Keep your page organized and easy to navigate by grouping similar components together under an expandable component group.
Component automation - Automatically update the status of your components using email automation, our API, or one of our integrations.
Third-party components - If your service is heavily dependent on a third-party service, you can surface that component (as long as we offer it) on your own status page. Details on components.
Incidents are the best way to communicate with your customers during downtime. To keep your customers in the loop, add an incident to your page and post updates until it's resolved.
Scheduled maintenance - Let your customers know ahead of time when you're going to be unavailable due to maintenance. Scheduled maintenances appear on your status page and also send a notification to subscribers. Details on maintenance.
Incident templates -Be prepared for downtime by writing incident templates you can use to auto-fill when creating a live incident. Details on templates.
Postmortems - After a major incident is resolved, you can create a postmortem to explain what happened. Postmortems should include an apology, understanding of what happened, and a remediation plan. Postmortems will be published within the incident, and can notify your subscribers. Details on postmortems.
We believe in being transparent with customers. Use System Metrics to display real-time data such as response time and uptime. Metrics can be created using our API, or through a third-party data source we integrate with.
Example metrics - Some common metrics we see are API response time, server uptime, average time an outbound request sits in a queue, current exception rate of all requests, and average first reply time on customer support requests. Details on metrics.
Adding a metric using third-party data sources - If you have data in Pingdom, New Relic, Librato, or Datadog, we have integrations with each of those services and you can easily get that data flowing into Statuspage as a system metric. Details on 3rd party metrics.
Adding a custom metric - If your data is not in one of the above third-party services, you can create metric data using our API.
Managing your status page
Statuspage can send out notifications to your customers via Email or SMS when you create or update incidents. All you have to do is make sure the incident is created, we'll handle notifying the people who need to know about it.
Manually adding subscribers - If you already have a list of emails or phone numbers, you can import them as subscribers using a CSV or by adding individual subscribers manually. Details on CSV import.
Sync subscribers with our API - Use our API to pragmatically create subscribers based on events or actions in another system. More on subscriber API.
Self-service signup - As long as you have email and/or SMS subscriptions enabled, anyone who visits your page can subscribe to updates by clicking Subscribe to updates.
Component subscriptions - Component subscriptions ensure your subscribers are only getting notified about the things they care about. To enable this feature, you must be on the Business, Growth, or Corporate plan. Details on component subscriptions.
Webhook subscriptions - Anyone can subscribe to your status page to receive a webhook notification when you post/update an incident and when components are updated. Details on webhooks.
Team members can be thought of as "admins". They are the people who have access to your account to create incidents, change the state of components, and much more.
Account owner - There is only 1 account owner on each account. The only difference between the account owner and a regular team member is that the account owner can remove team members.
Access controls - Statuspage doesn't currently have any access controls or granular permission levels for team members. All team members within the account have access to each page under the account and all of the features under each page.
Removing team members - Only the account owner has permissions to remove other team members. If your account owner is no longer with the company, please reach out and we'll assist with these requests.
Basic logo vs cover image - Use a basic layout that displays your logo at the top of the page, or give your page some flair with a custom header.
Other customizations - Use a custom domain, translate your page into multiple languages, and set a custom 'from' address.
Incident communication best practices
Communicate clearly - Focus on how exactly your customers are impacted by the incident. If not everyone is impacted, let that be known.
Communicate often - Once you create your incident, don't leave your customers hanging. Post updates regularly.
Post-incident report - We call these "postmortems" in Statuspage. After a major incident, it's always good to let your customers know what happened and what you're doing to avoid the incident from happening again.
Statuspage doesn't do any direct monitoring of websites or servers but we do integrate with monitoring and alerting tools. Our API also allows you to create incidents, update components, manage subscribers, and more.
Email automation - Automatically update the status of your components by configuring your monitoring tool to send us emails. Details on email automation.
PagerDuty - Take your status page to the next level with our PagerDuty integration. Automatically create incidents and update components by configuring rules. Details on PagerDuty.
Other integrations - More integrations are available for Pingdom, New Relic, Opsgenie, xMatters, VictorOps, and Pingometer. Each of these integrations offer functionality ranging from changing the state of components, to creating incidents. Details on other.
Integrations - Display real-time metrics like uptime and response time on your status page by integrating Pingdom, New Relic, Datadog, or Librato.
API - If you're not already using one of the above supported metrics providers, you can bring in metrics using our API.
Slack - Keep your team in the loop by syncing Statuspage events (like who created an incident, or what a component status was changed to) into Slack. Control the noise by filtering out different types of events and actions. Details on Slack.