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
深受数千家企业的信赖
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
在事件发生期间，与您的用户和客户公开沟通。
Hobby
- 250 位订阅者
- 5 名团队成员
- 5 个指标
- 电子邮件通知
- Slack 通知
- 基础的自定义
- 自定义网域
- 访问 REST API
Startup
- 1000 位订阅者
- 10 名团队成员
- 10 个指标
- 电子邮件/短信/Webhook 通知
- Slack 通知
- 自定义 CSS
- 自定义网域
- 访问 REST API
- 团队成员单点登录（通过 Atlassian Access）
Business
- 5000 位订阅者
- 25 名团队成员
- 25 个指标
- 电子邮件/短信/Webhook 通知
- Slack 通知
- 自定义 CSS/HTML/JS
- 自定义网域
- 访问 REST API
- 团队成员单点登录（通过 Atlassian Access）
- 组件订阅
- 每年提供采购订单和发票
Enterprise
- 25,000 位订阅者
- 50 名团队成员
- 50 个指标
- 电子邮件/短信/Webhook 通知
- Slack 通知
- 自定义 CSS/HTML/JS
- 自定义网域
- 访问 REST API
- 团队成员单点登录（通过 Atlassian Access）
- 组件订阅
- 每年提供采购订单和发票
与员工私下沟通有关内部工具和服务的问题。
Starter
- 5 名团队成员
- 50 名员工
- 5 个指标
- 电子邮件通知
- 自定义 CSS
- 事件模板
- 警报集成
- 团队成员单点登录（通过 Atlassian Access）
Growth
- 15 名团队成员
- 300 名员工
- 15 个指标
- 电子邮件/短信/Webhook 通知
- 自定义 CSS/HTML/JS
- 事件模板
- 警报集成
- 组件订阅
- IP 允许列表
- 团队成员单点登录（通过 Atlassian Access）
Corporate
- 35 名团队成员
- 1000 名员工
- 35 个指标
- 电子邮件/短信/Webhook 通知
- 自定义 CSS/HTML/JS
- 事件模板
- 警报集成
- 组件订阅
- IP 允许列表
- 团队成员单点登录（通过 Atlassian Access）
- 每年提供采购订单和发票
Enterprise
- 50 名团队成员
- 5000 名员工
- 50 个指标
- 电子邮件/短信/Webhook 通知
- 自定义 CSS/HTML/JS
- 事件模板
- 警报集成
- 组件订阅
- IP 允许列表
- 团队成员单点登录（通过 Atlassian Access）
- 每年提供采购订单和发票
针对不同的用户组提供不同视图
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.