StatusGator gets the official status data from each company’s official status page. Status pages are published by thousands of vendors 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+ vendors. Our platform constantly monitors and automatically detects outages, 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 services 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 cloud providers 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 cloud providers to your application status. Just reach out using the support link.

StatusGator collects the status of each service from its official status page every 5 minutes, ensuring outages and resolutions are ingested into the StatusGator platform promptly and displayed on your application 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 vendor. 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 app developers use.

A hosted status page is a page on your website dedicated to communicating the service status of your applications. Whatever apps you rely on, your status page communicates whether they are up, down, undergoing maintenance, or experiencing issues.
Status pages are for users to easily find out the status of their services. With StatusGator status page monitoring, the status of all your services is on one unified page.

All status pages are designed for incident communication. Communicating current events or incidents your services might be experiencing is vital. However, there are different types to keep everyone in your business or organization informed.

Public status pages are the most popular, designed to enable your users to view status information and metrics at any time. These pages are easily accessible and can typically be found on Google every time (depending on your organization).
Private status pages are often for internal teams and DevOps. These pages typically require single sign-on or password protection for user accounts. Designed to be internal, private status pages provide your teams with the means to directly access service data. DevOps can also authenticate users freely.

Finally, audience-specific pages are pages that are tailored to a custom audience. Not all status page providers offer this. Audience-specific pages help you configure your status page to the right viewers to make sure it is relevant.

StatusGator provides all three types of pages listed above. This helps you manage status pages easily and get started with keeping your users informed. Some providers are hosted (e.g. StatusGator) and some are open-source (e.g. UptimeRobot).

Absolutely! You can create your application status page to include whatever you need. StatusGator makes it simple to create a custom status page, making sure you create the right template to display your system status.

You can also choose which services you want to display. By filtering which services you need to check, you allow your users and teams to quickly and easily check operational status.

For large organizations, this can prevent a flood of support tickets from being sent to the IT support team or help center. Email notifications are typically sent out before users can submit tickets.

A status page communicates service disruptions to keep customers in the loop. By displaying service statuses, your users get real-time updates when issues occur. This improves user visibility and keeps your customers informed. Most status pages also showcase reliability.
This is vital during the incident response process. Incident notifications can be sent out via email, SMS, or social media to keep users informed. However, their primary source of information during an incident is your status page.