Internal Status Page


An Internal Status Page allows devops and your designated account users to share outages, incidents, maintenance schedules, and uptime statistics internally. Use Internal Status Pages to:

  • Share current status and incident history 
  • Track the state of critical components
  • Limit visibility and subscriber privileges to your registered account users

View our Status Page setup documentation here, or check out our sample Internal Status Page.

Table of Contents

Internal Status Page Use Case 


For this use case, let’s look at a large company with multiple teams responsible for different aspects of system operations and services. During a downtime event, each of the affected teams benefits from:

  • A direct notification of the incident at onset
  • A real-time view of check status
  • Notifications on progress throughout the incident
  • A single point of contact for incident questions or observations

Create unique Internal Status Pages for your services as needed. Because we want only relevant team members notified of downtime, we will allow subscribers to our Page and can skip making the Page public.

We can make the Page public with a custom URL, either using the URL or our own custom CNAME. If we choose this route, we can further control access with basic authorization to lock the Page down so only users with the proper credentials can see it. 


When a downtime event occurs, DevOps can push alerts via Internal Status Page incidents. With incident descriptions, you can add important notes about scheduled maintenance, degraded performance, or the state of an outage. 


These updates prove useful to customer-facing roles, like support or customer service, as well as managerial roles relying on services to complete tasks. 

As you progress through resolving the incident, add additional status updates easily to your Page and push them through as email notifications or standalone updates. This proactive approach improves visibility of critical outages throughout all levels of your organization.

With controlled access and multiple configurations possible, Internal Status Pages are ideal for teams to quickly communicate the state of non-public-facing components to team members.

We Recommend Internal Status Pages for:


  • Sharing metrics and incident history internally as a resource for your team and account users
  • Controlling visibility among your account users
  • Clarifying responsibilities among your team to reduce response time when issues arise

Learn how to customize and configure your Internal Status Page here.

Want to see our checks in action? Check out our youtube-logo-final.svg YouTube Library for more!

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.