🚀 AI Generated Incident Summaries Feature is Now Live! See it in action! 🎉
Blog
Product Updates
What you can show on your status page

What you can show on your status page

January 14, 2020
What you can show on your status page
In This Article:
Our Products
On-Call Management
Incident Response
Continuous Learning
Workflow Automation

Our last blog post ‘Using a Status Page in your Incident response process’ established what a status page is and how it plays an important role in your incident response processes, this article is to understand the different information components of a status page. 

When something goes down, the first thing a customer does is check if there is something wrong with their systems or if it is an issue with one of their service providers. So it’s important to make sure that your status page has all the information that is needed where they don’t feel the need to raise an issue or create a ticket, adding to your support costs.

The most essential information needed on the Status Page is to understand which component of the service has been degraded or had an outage. 

Components of a System: 

Every system has some users who may need to know the status of the system from its Status Page. Now, the system can be thought to be made up of multiple components, which in turn consist of services and microservices - some are user facing and some are integral in the functioning of a user facing component while other components could be purely internal. Note that users of these components are not just your end customers but could also be internal to your team like other engineers or folks from the product or customer success teams. It is important to lay down a branched overview of all the user facing and their respective dependent components to show their operational status. The easiest way to break this down would be to pick a component that is: 

  • Directly user facing
  • Impacting a service that is user facing
  • An API or a set of APIs being consumed by the user
squadcast status page

Operational Status: 

Once you have a branched overview of the various components that your users are interested in, the first section of your status page will have a list or table outlining these components against which the operational status of the components need to be added. The operational status indicates the current working conditions of the service or component - that is, if it is fully operational or partially degraded or if there’s an outage. 

In some cases, the first section  can be a graphical representation of the uptime history of the components to showcase the reliability of the system over a period of time. This also holds the uptime statistic such as “99.988% uptime for the last 90 days” which is useful for the customer to understand any downtime patterns. 

strip -system status page

Incident History: 

The next section is typically the incident history which provides a day-wise account of system impacting incidents that have occurred along with their current resolution status.

This gives users an idea of the type of incidents that have occurred and the resolution actions taken on it which builds trust with your customer because they’re constantly informed of the resolution activity and the level of impact any incident has on them. 

github - status page

Incident Status: 

When a service impacting incident occurs, it is important to not just communicate that a service impacting incident has occurred but also keep them in the loop to update them on what’s happening on the resolution front. This updation is usually shown in the incident history section of the status page. 

Github - Incident status

Subscribe: 

Most status pages allow their users to subscribe to updates in some form (usually email). Any incident related update that is pushed to status page will go out to the subscribers. This is the easiest form of automated customer communication that lets teams focus on resolution and just push updates to the status page instead of worrying about writing emails or dealing with communication silos within the organization.

github - status update

Twitter Updates: 

Before status pages became popular as a communication tool, organizations updated outages and service degradations on twitter. This was the easiest way to reach a massive audience and most importantly customers that pay for their service.

Today, you can add twitter updates also as a section on the status page just to let your customers know that there is one other form of communication you use to update people on any downtime. However, in today’s world, having a status page has become the de facto standard and people rarely think of checking their twitter feeds to see if a service is facing downtime and instead subscribe to status page updates or just go straight to the status page.

twitter status update


To know more about what we’re building, check out our public Product Roadmap. Feel free to drop us your ideas and feature requests at [email protected].

Written By:
January 14, 2020
Prakya Vasudevan
Prakya Vasudevan
January 14, 2020
Product Updates
SRE
Share this blog:
In This Article:
Get reliability insights delivered straight to your inbox.
Get ready for the good stuff! No spam, no data sale and no promotion. Just the awesome content you signed up for.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
If you wish to unsubscribe, we won't hold it against you. Privacy policy.
Get reliability insights delivered straight to your inbox.
Get ready for the good stuff! No spam, no data sale and no promotion. Just the awesome content you signed up for.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
If you wish to unsubscribe, we won't hold it against you. Privacy policy.
Get the latest scoop on Reliability insights. Delivered straight to your inbox.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
If you wish to unsubscribe, we won't hold it against you. Privacy policy.
Squadcast is a leader in Incident Management on G2 Squadcast is a leader in Mid-Market IT Service Management (ITSM) Tools on G2 Squadcast is a leader in Americas IT Alerting on G2 Best IT Management Products 2024 Squadcast is a leader in Europe IT Alerting on G2 Squadcast is a leader in Enterprise Incident Management on G2 Users love Squadcast on G2
Squadcast is a leader in Incident Management on G2 Squadcast is a leader in Mid-Market IT Service Management (ITSM) Tools on G2 Squadcast is a leader in Americas IT Alerting on G2
Best IT Management Products 2024 Squadcast is a leader in Europe IT Alerting on G2 Squadcast is a leader in Enterprise Incident Management on G2
Users love Squadcast on G2
Copyright © Squadcast Inc. 2017-2024

What you can show on your status page

Jan 14, 2020
Last Updated:
October 4, 2024
Share this post:
What you can show on your status page

When something goes down, the first thing a customer does is check if there is something wrong with their systems or if it is an issue with one of their service providers. So it’s important to make sure that your status page has all the information that is needed where they don’t feel the need to raise an issue or create a ticket, adding to your support costs.

Table of Contents:

    Our last blog post ‘Using a Status Page in your Incident response process’ established what a status page is and how it plays an important role in your incident response processes, this article is to understand the different information components of a status page. 

    When something goes down, the first thing a customer does is check if there is something wrong with their systems or if it is an issue with one of their service providers. So it’s important to make sure that your status page has all the information that is needed where they don’t feel the need to raise an issue or create a ticket, adding to your support costs.

    The most essential information needed on the Status Page is to understand which component of the service has been degraded or had an outage. 

    Components of a System: 

    Every system has some users who may need to know the status of the system from its Status Page. Now, the system can be thought to be made up of multiple components, which in turn consist of services and microservices - some are user facing and some are integral in the functioning of a user facing component while other components could be purely internal. Note that users of these components are not just your end customers but could also be internal to your team like other engineers or folks from the product or customer success teams. It is important to lay down a branched overview of all the user facing and their respective dependent components to show their operational status. The easiest way to break this down would be to pick a component that is: 

    • Directly user facing
    • Impacting a service that is user facing
    • An API or a set of APIs being consumed by the user
    squadcast status page

    Operational Status: 

    Once you have a branched overview of the various components that your users are interested in, the first section of your status page will have a list or table outlining these components against which the operational status of the components need to be added. The operational status indicates the current working conditions of the service or component - that is, if it is fully operational or partially degraded or if there’s an outage. 

    In some cases, the first section  can be a graphical representation of the uptime history of the components to showcase the reliability of the system over a period of time. This also holds the uptime statistic such as “99.988% uptime for the last 90 days” which is useful for the customer to understand any downtime patterns. 

    strip -system status page

    Incident History: 

    The next section is typically the incident history which provides a day-wise account of system impacting incidents that have occurred along with their current resolution status.

    This gives users an idea of the type of incidents that have occurred and the resolution actions taken on it which builds trust with your customer because they’re constantly informed of the resolution activity and the level of impact any incident has on them. 

    github - status page

    Incident Status: 

    When a service impacting incident occurs, it is important to not just communicate that a service impacting incident has occurred but also keep them in the loop to update them on what’s happening on the resolution front. This updation is usually shown in the incident history section of the status page. 

    Github - Incident status

    Subscribe: 

    Most status pages allow their users to subscribe to updates in some form (usually email). Any incident related update that is pushed to status page will go out to the subscribers. This is the easiest form of automated customer communication that lets teams focus on resolution and just push updates to the status page instead of worrying about writing emails or dealing with communication silos within the organization.

    github - status update

    Twitter Updates: 

    Before status pages became popular as a communication tool, organizations updated outages and service degradations on twitter. This was the easiest way to reach a massive audience and most importantly customers that pay for their service.

    Today, you can add twitter updates also as a section on the status page just to let your customers know that there is one other form of communication you use to update people on any downtime. However, in today’s world, having a status page has become the de facto standard and people rarely think of checking their twitter feeds to see if a service is facing downtime and instead subscribe to status page updates or just go straight to the status page.

    twitter status update


    To know more about what we’re building, check out our public Product Roadmap. Feel free to drop us your ideas and feature requests at [email protected].

    What you should do now
    • Schedule a demo with Squadcast to learn about the platform, answer your questions, and evaluate if Squadcast is the right fit for you.
    • Curious about how Squadcast can assist you in implementing SRE best practices? Discover the platform's capabilities through our Interactive Demo.
    • Enjoyed the article? Explore further insights on the best SRE practices.
    • Schedule a demo with Squadcast to learn about the platform, answer your questions, and evaluate if Squadcast is the right fit for you.
    • Curious about how Squadcast can assist you in implementing SRE best practices? Discover the platform's capabilities through our Interactive Demo.
    • Enjoyed the article? Explore further insights on the best SRE practices.
    • Get a walkthrough of our platform through this Interactive Demo and see how it can solve your specific challenges.
    • See how Charter Leveraged Squadcast to Drive Client Success With Robust Incident Management.
    • Share this blog post with someone you think will find it useful. Share it on Facebook, Twitter, LinkedIn or Reddit
    • Get a walkthrough of our platform through this Interactive Demo and see how it can solve your specific challenges.
    • See how Charter Leveraged Squadcast to Drive Client Success With Robust Incident Management
    • Share this blog post with someone you think will find it useful. Share it on Facebook, Twitter, LinkedIn or Reddit
    • Get a walkthrough of our platform through this Interactive Demo and see how it can solve your specific challenges.
    • See how Charter Leveraged Squadcast to Drive Client Success With Robust Incident Management
    • Share this blog post with someone you think will find it useful. Share it on Facebook, Twitter, LinkedIn or Reddit
    What you should do now?
    Here are 3 ways you can continue your journey to learn more about Unified Incident Management
    Discover the platform's capabilities through our Interactive Demo.
    See how Charter Leveraged Squadcast to Drive Client Success With Robust Incident Management.
    Share the article
    Share this blog post on Facebook, Twitter, Reddit or LinkedIn.
    We’ll show you how Squadcast works and help you figure out if Squadcast is the right fit for you.
    Experience the benefits of Squadcast's Incident Management and On-Call solutions firsthand.
    Compare our plans and find the perfect fit for your business.
    See Redis' Journey to Efficient Incident Management through alert noise reduction With Squadcast.
    Discover the platform's capabilities through our Interactive Demo.
    We’ll show you how Squadcast works and help you figure out if Squadcast is the right fit for you.
    Experience the benefits of Squadcast's Incident Management and On-Call solutions firsthand.
    Compare Squadcast & PagerDuty / Opsgenie
    Compare and see if Squadcast is the right fit for your needs.
    Compare our plans and find the perfect fit for your business.
    Learn how Scoro created a solid foundation for better on-call practices with Squadcast.
    Discover the platform's capabilities through our Interactive Demo.
    We’ll show you how Squadcast works and help you figure out if Squadcast is the right fit for you.
    Experience the benefits of Squadcast's Incident Management and On-Call solutions firsthand.
    We’ll show you how Squadcast works and help you figure out if Squadcast is the right fit for you.
    Learn how Scoro created a solid foundation for better on-call practices with Squadcast.
    We’ll show you how Squadcast works and help you figure out if Squadcast is the right fit for you.
    Discover the platform's capabilities through our Interactive Demo.
    Enjoyed the article? Explore further insights on the best SRE practices.
    We’ll show you how Squadcast works and help you figure out if Squadcast is the right fit for you.
    Experience the benefits of Squadcast's Incident Management and On-Call solutions firsthand.
    Enjoyed the article? Explore further insights on the best SRE practices.
    Written By:
    January 14, 2020
    January 14, 2020
    Share this post:
    Subscribe to our LinkedIn Newsletter to receive more educational content
    Subscribe now
    ant-design-linkedIN

    Subscribe to our latest updates

    Enter your Email Id
    Thank you! Your submission has been received!
    Oops! Something went wrong while submitting the form.
    FAQs
    More from
    Prakya Vasudevan
    On-call On-boarding Checklist
    On-call On-boarding Checklist
    May 20, 2020
    Best Practices in Incident Management
    Best Practices in Incident Management
    May 7, 2020
    Configure an Intuitive Service Dashboard & Reduce Response Time
    Configure an Intuitive Service Dashboard & Reduce Response Time
    April 30, 2020
    Learn how organizations are using Squadcast
    to maintain and improve upon their Reliability metrics
    Learn how organizations are using Squadcast to maintain and improve upon their Reliability metrics
    mapgears
    "Mapgears simplified their complex On-call Alerting process with Squadcast.
    Squadcast has helped us aggregate alerts coming in from hundreds...
    bibam
    "Bibam found their best PagerDuty alternative in Squadcast.
    By moving to Squadcast from Pagerduty, we have seen a serious reduction in alert fatigue, allowing us to focus...
    tanner
    "Squadcast helped Tanner gain system insights and boost team productivity.
    Squadcast has integrated seamlessly into our DevOps and on-call team's workflows. Thanks to their reliability...
    Alexandre Lessard
    System Analyst
    Martin do Santos
    Platform and Architecture Tech Lead
    Sandro Franchi
    CTO
    Squadcast is a leader in Incident Management on G2 Squadcast is a leader in Mid-Market IT Service Management (ITSM) Tools on G2 Squadcast is a leader in Americas IT Alerting on G2 Best IT Management Products 2022 Squadcast is a leader in Europe IT Alerting on G2 Squadcast is a leader in Mid-Market Asia Pacific Incident Management on G2 Users love Squadcast on G2
    Squadcast awarded as "Best Software" in the IT Management category by G2 🎉 Read full report here.
    What our
    customers
    have to say
    mapgears
    "Mapgears simplified their complex On-call Alerting process with Squadcast.
    Squadcast has helped us aggregate alerts coming in from hundreds of services into one single platform. We no longer have hundreds of...
    Alexandre Lessard
    System Analyst
    bibam
    "Bibam found their best PagerDuty alternative in Squadcast.
    By moving to Squadcast from Pagerduty, we have seen a serious reduction in alert fatigue, allowing us to focus...
    Martin do Santos
    Platform and Architecture Tech Lead
    tanner
    "Squadcast helped Tanner gain system insights and boost team productivity.
    Squadcast has integrated seamlessly into our DevOps and on-call team's workflows. Thanks to their reliability metrics we have...
    Sandro Franchi
    CTO
    Revamp your Incident Response.
    Peak Reliability
    Easier, Faster, More Automated with SRE.