SaaS Status & Incident Monitor

Monitor SaaS status pages, incidents, outages, maintenance notices, affected services, and reliability signals.

Who this is for

• Reliability teams
• Customer success teams
• Competitive intelligence teams

What it helps you do

• Track competitor uptime incidents
• Collect status page updates and affected services
• Build reliability datasets for reporting

Inputs you can use

• Status page URLs
• Company names
• Maximum incidents

Data you get

• company
• incident title
• status
• severity
• affected services
• date
• update text
• source URL

How to get better results

• Start with a narrow, specific query or a small list of source URLs.
• Use realistic limits for the first run, then increase the volume once the output looks right.
• Keep source URLs, dates, and location context when you need repeatable market monitoring.
• Review a few sample records before connecting the dataset to a larger workflow.

Notes

• Results depend on what the public source exposes at run time.
• Some pages may hide, delay, rename, or remove fields, so individual records can have partial data.
• Use the built-in output table to inspect results before exporting to spreadsheets, dashboards, or automation tools.

Support

If a run returns unexpected data, open an issue from the Actor page with the input used, the run ID, and the result you expected.