StatusGator monitors services and their individual components, so you can stay informed about the systems you rely on – and filter down to only the components you care about.
Most status pages do a good job of tagging incidents to the affected components. But sometimes providers publish incident updates without marking any components as impacted, even when the incident clearly affects something real.
For example, Figma may post an incident mentioning Figma Make, even though Figma Make isn’t listed as a component on their status page. In cases like that, a component-based monitor can miss the incident entirely. Some providers choose to list incidents as non-impacting in their early minutes until they know what components of their infrastructure are affected.
To improve coverage, and ensure you don’t miss any incidents, StatusGator can now detect incidents even when no components are listed. This means you can still be notified when a provider posts a general incident or early-stage investigation that hasn’t been fully categorized yet. We’ll rolling out support for this across the more than 7,000 services we monitor.
Log in to StatusGator anytime to review your monitors and component filters. And if you have questions, we’re always happy to help.
