Introduction to Statuspage
Learn incident communication best practices and tips, as well as which type of status page is right for you and how to use it effectively.
Stats from teams using Statuspage
Faster incident comms
Incident communications +50% faster than their previous method
Fewer questions
A 24% decrease in incident-related support tickets during downtime
More customer trust
67% reported an increase in user trust
Less time wasted
80% of support teams say they’re more efficient during incidents
Trusted by thousands of companies
Connect the tools you already love
Inform your customers even faster with our native integration suite. Connect your status page to the most popular communication, monitoring, and alerting tools, or use our REST API.
Pricing that scales with you as you grow
Communicate publicly with your users and customers during an incident.
Hobby
- 250 Subscribers
- 5 Team Members
- 5 Metrics
- Email Notifications
- Slack Notifications
- Basic Customization
- Custom Domain
- Access to REST APIs
Startup
- 1,000 Subscribers
- 10 Team Members
- 10 Metrics
- Email/SMS/Webhook Notifications
- Slack Notifications
- Custom CSS
- Custom Domain
- Access to REST APIs
- Team member SSO (with Atlassian Access)
Business
- 5,000 Subscribers
- 25 Team Members
- 25 Metrics
- Email/SMS/Webhook Notifications
- Slack Notifications
- Custom CSS/HTML/JS
- Custom Domain
- Access to REST APIs
- Team member SSO (with Atlassian Access)
- Component Subscriptions
- Yearly PO & Invoicing Available
Enterprise
- 25,000 Subscribers
- 50 Team Members
- 50 Metrics
- Email/SMS/Webhook Notifications
- Slack Notifications
- Custom CSS/HTML/JS
- Custom Domain
- Access to REST APIs
- Team member SSO (with Atlassian Access)
- Component Subscriptions
- Yearly PO & Invoicing Available
Communicate privately with your employees about issues with internal tools and services.
Starter
- 5 Team Members
- 50 Employees
- 5 Metrics
- Email Notifications
- Custom CSS
- Incident Templates
- Alerting Integrations
- Team member SSO (with Atlassian Access)
Growth
- 15 Team Members
- 300 Employees
- 15 Metrics
- Email/SMS/Webhook Notifications
- Custom CSS/HTML/JS
- Incident Templates
- Alerting Integrations
- Component Subscriptions
- IP Allowlisting
- Team member SSO (with Atlassian Access)
Corporate
- 35 Team Members
- 1,000 Employees
- 35 Metrics
- Email/SMS/Webhook Notifications
- Custom CSS/HTML/JS
- Incident Templates
- Alerting Integrations
- Component Subscriptions
- IP Allowlisting
- Team member SSO (with Atlassian Access)
- Yearly PO & Invoicing Available
Enterprise
- 50 Team Members
- 5,000 Employees
- 50 Metrics
- Email/SMS/Webhook Notifications
- Custom CSS/HTML/JS
- Incident Templates
- Alerting Integrations
- Component Subscriptions
- IP Allowlisting
- Team member SSO (with Atlassian Access)
- Yearly PO & Invoicing Available
Different views for different sets of users
What is incident communication?
Incident communication is the process of alerting users that a service is experiencing some type of outage or degraded performance. This is especially important for web and software services, where 24/7 availability is expected. Since downtime is inevitable, check out our comprehensive guide to incident communication best practices.
Incident Management Handbook
Interested in learning what happens when an Atlassian service goes down? We've created the Incident Management Handbook to summarize our incident management process and pass on our experiences. These are the lessons we've learned responding to incidents for more than a decade. While it’s based on our unique experiences, the practices and theories can be adapted to suit the needs of your own team.