Close

Public Pages

Effortlessly communicate with page viewers to build trust before, during, and after an incident.

Public pages

Effortlessly communicate with external stakeholders to build trust before, during, and after an incident.

Statuspage webinar illustration

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

Lightning bolt
Faster incident comms

Incident communications +50% faster than their previous method

Question mark
Fewer questions

A 24% decrease in incident-related support tickets during downtime 

Thumbs up icon
More customer trust

67% reported an increase in user trust

Stopwatch icon
Less time wasted

80% of support teams say they’re more efficient during incidents

수천 개의 기업이 신뢰하는 Statuspage

New Relic 로고
Twilio 로고
Reddit 로고
Squarespace 로고
Coinbase 로고
Shopify 로고
New Relic 로고
Twilio logo
Squarespace 로고
Reddit 로고
DigitalOcean logo
Shopify logo

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.

Opsgenie logo
Slack logo
Twitter logo
zendesk logo
Jira Service Desk logo
pagerduty logo
Microsoft Office teams logo
Intercom logo

Pricing that scales with you as you grow

인시던트 발생 시 사용자 및 고객과 공개적으로 소통할 수 있습니다.

Free

Free 플랜으로는 구독자 100명, 팀원 2명, 지표 2개, 이메일 알림 및 REST API를 이용할 수 있습니다.

Free

Free 플랜으로는 구독자 100명, 팀원 2명, 지표 2개, 이메일 알림 및 REST API를 이용할 수 있습니다.

Hobby

$29
/월

Startup

$99
/월

Business

$399
/월

Enterprise

$1,499
/월

사내 도구 및 서비스로 문제에 관해 직원들과 비공개로 소통할 수 있습니다.

Starter

$79
/월

Growth

$249
/월

Corporate

$599
/월

Enterprise

$1,499
/월

시작:

$300
/월

시작:

$300
/월

다른 사용자 집합에 대한 다른 보기

Meeples
Meeples
Balloons with checks and crosses
Message bubbles

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.

Book icon

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.