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 2,700 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 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 status page. Typically these incidents are listed in red on a service’s status page.
• [ maintenance ] – Scheduled, proactive maintenance as published on the 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. Just reach out using the support link below.

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 in a timely manner and displayed on your internal status page in real time.

Absolutely. StatusGator supports a critical feature that many 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 IT team uses.

Your entire team or organization can! This depends on who relies on your organization’s services and software. Compared to a public status page, an internal (or private) status page is designed with your team members in mind. It can communicate the real-time status of your various services (or tools you already use) to DevOps or other teams.
If you get a status page that is designed specifically for your team, you can be the first to know of any impact on your critical services. Create your internal status page today and make sure your team is up to date.

This depends on your provider, of which there are many (such as Atlassian Statuspage, Pagerduty, Incident.io, and more). We can’t speak for other providers, but there is no lag time in processing status updates and changes with StatusGator.
Current service statuses are aggregated and automatically updated on your status page in real time. This routine collection and aggregation is designed to prevent delay or lag. This ensures incident communication is a smooth process, as your users need to be able to see the current status of their services without delay.

Absolutely! You can create your internal 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.