Child pages
  • Status and Incident Management with Statuspage
Skip to end of metadata
Go to start of metadata

Whoever offers their services online knows that errors and server problems will occur. In this context, it is important that you publicize these failures as clearly as possible. In the worst case, your support teams will be overrun with queries and the delayed responses lead to disappointed customers. Statuspage allows you to proactively deal with malfunctions and minimize incident requests, thus saving you costs while increasing your commitment to your internal and external customers.

 What is Statuspage?

    • Statuspage is a cloud-based service that allows you to communicate disruptions openly and to make the process of fault handling detailed and transparent for your customers.
    • Customers can be informed via different services (email, SMS etc.) when an incident occurs.
    • Statuspage can be operated as a single page (see https://status.twilio.com/) or embedded directly in your issue system.

Why makes Statuspage a good service?

    • Statuspage has an availability of 99.995%.
    • Up to 40,000 requests per second can be processed to be able to intercept any form of interference (e.g. in the form of a DDoS attack).
    • Setting up the service takes less than 30 minutes.
    • It can be integrated with four different SMS and email providers.
    • Most Status and Incident Communication providers already use Statuspage.

Public and private pages

    • In addition to the public Statuspage, a non-public version can also be used.
    • There are internal use cases, for example, when you work on your connected services and third party components in your infrastructure, this can lead to disturbances in other services used internally.
    • IP restrictions (eg SAML) can be used to create private status pages and populate them with the metrics from various services such as Stripe, Mailgun or PagerDuty.

Example of Statuspage used by the developer twilio

 Advantages of using Statuspage

    • Proactive and open handling of incidents fosters trust with your internal and external customers.
    • During the downtime, the support overhead can be reduced by up to 30%.
    • Incidents can be listed on the Statuspage automatically or manually.

What are the advantages for Atlassian customers?

    • Statuspage can be integrated into Atlassian Hipchat, so that status messages can be pushed into a separate Hipchat space, for example.
    • Integration with Jira Service Desk is also possible so that customers can view incidents before they create a ticket.
    • Jira integration is planned.

 

Statuspage distributed via Atlassian is planned for summer 2017. From this point onwards, you can purchase Statuspage with all other Atlassian licenses. We look forward to your inquiry.

Diese Seite auf Deutsch anzeigen



Metrics available in Statuspage