StatusGator gets the official status data from each company’s official status page. Status pages are published by thousands of cloud services as a way to communicate the status of each service. StatusGator reads this status page data into its platform, ensuring that the data we aggregate is the official, published incident information.

StatusGator uses three methods to collect status data from official status pages: Web scraping, documented APIs, and undocumented APIs. We use proprietary technology to collect and normalize the data from more than 4000 cloud services. Our platform constantly monitors and automatically detects incidents, ensuring accurate, up-to-date information no matter how often a status page changes.

• [ warn ] – A minor incident as indicated by the application status page. Usually, these incidents are listed in yellow or orange on a cloud provider’s status page.
• [ down ] – A major incident as indicated by the app status page. Typically these incidents are listed in red on a service’s status page.
• [ maintenance ] – Scheduled, proactive maintenance as published on the application status page. Sometimes these have no impact but are published for informational purposes.

StatusGator can aggregate the status of any vendors using their public, official status page. If the service does not publish a status page, then we cannot aggregate their official status. If their status page is only available behind a login we currently do not support this for security reasons. Otherwise, we are happy to add vendors. Just reach out using the support link.

StatusGator collects the status of each service from their official status page every 5 minutes, ensuring incidents and resolutions are ingested into the StatusGator platform promptly and displayed on your DevOps status page in real-time.

Absolutely. StatusGator supports a critical feature that many application status pages do not – the ability to filter to specific components of a given cloud service. For many services, a component can be a region or a product. If you only use certain products, regions, or features of a given service, you can use component filters to limit your notifications to only those that affect the components your DevOps team uses.

A status page communicates status updates and information, regarding the services you rely on, to keep you informed. When a service experiences an outage or issue, this information will continuously update on your status page so users are informed. Status pages ultimately act as one source of truth when it comes to transparency surrounding your services. 

There are many providers out there (such as Atlassian, Azure, Pagerduty, and more) that can get you started with a status page. However, StatusGator goes the extra mile.

Alongside typical status page features (such as real-time updates, historical uptime, and service responsiveness), StatusGator provides users with: 

• Status aggregation and normalization 
• Customization tools
• Single sign-on 
• Custom domain or URLs
• The ability to configure alerts

These features of a status page help build customer trust and keep everyone in the loop. Showcase reliability, share incident updates, and keep users informed with StatusGator today!

With StatusGator, you can add custom features to your status page. Even if your page is internal/private for DevOps, you can tailor it as you wish. 

Firstly those with access can tailor it for specific needs. This may involve custom integrations, the ability to automate incident response via notifications to your team, or timely incident updates to specific staff. By keeping your team members in mind, StatusGator can ensure your status page communicates the right information to the right people. Additional features for customization include SSO configuration, endpoint monitoring, and metric analysis features that can be filtered and specified. 

If you want to tailor your page to your brand, you have StatusGator’s design features to do so. Incorporate your logo and custom fonts, alongside custom colors.

There are various types of status pages, but most can be categorized into 3 different types: 

• Public status pages – These pages are designed to keep your customers in the loop. By displaying real-time status updates, you can keep your customers informed when it comes to critical services. This ensures you are transparent, building trust with your users. 
• Private status pages – These internal status pages are primarily used by DevOps or internal teams. Compared to public pages, these can often be a lot more technical. This means private pages are restricted and require users to have robust password protection. 
• Audience-specific – Less common, but designed with a specific audience in mind. StatusGator offers audience specific, but many providers do not. 

The main difference between public and private status pages is that private pages keep your developers in mind. Public, on the other hand, is to communicate incidents (such as downtime) to customers. Whether you need public or private, StatusGator can get you started with a status page today.