SaaS Status Page Incident Monitor

Monitor public SaaS status-page RSS/Atom history feeds and produce a normalized incident dataset plus a Markdown digest.

What it does

• Fetches public status history feeds such as GitHub, Cloudflare, Stripe, OpenAI, and any compatible RSS/Atom feed.
• Normalizes incidents into a consistent output schema.
• Filters by lookback window, optional keywords, and scheduled maintenance inclusion.
• Emits one dataset item per matching incident.
• Saves a human-readable DIGEST.md and machine-readable OUTPUT.json to the key-value store.

Who it is for

• MSPs and internal IT teams tracking vendor incidents across their dependency stack.
• SaaS operators who need a daily upstream-dependency digest.
• Reliability/SRE teams that want lightweight vendor-outage context without building feed plumbing.

Example input

{
  "daysBack": 7,
  "keywords": ["api", "auth", "billing"],
  "includeMaintenance": false,
  "maxItems": 50,
  "feeds": [
    {"name": "GitHub", "url": "https://www.githubstatus.com/history.rss"},
    {"name": "Cloudflare", "url": "https://www.cloudflarestatus.com/history.rss"},
    {"name": "Stripe", "url": "https://www.stripestatus.com/history.rss"}
  ]
}

Output item schema

{
  "id": "stable sha256-based id",
  "sourceName": "GitHub",
  "sourceUrl": "https://www.githubstatus.com/history.rss",
  "title": "Incident with Actions",
  "url": "https://www.githubstatus.com/incidents/...",
  "publishedAt": "2026-07-07T10:00:00+00:00",
  "severity": "incident",
  "status": "resolved",
  "summary": "Resolved - Actions jobs recovered."
}

Limits and caveats

• This Actor uses public RSS/Atom feeds only. It does not log in or bypass access controls.
• Statuspage descriptions vary by vendor; severity and status are best-effort classifications from public text.
• For paid/production monitoring, customers should choose their own vendor feed list and keyword filters.
• Healthy/no-incident vendors may still publish scheduled maintenance notices; use includeMaintenance=false to suppress them.

Local development

python3 -m venv .venv
. .venv/bin/activate
pip install -r requirements.txt
python3 -m pytest tests -v
python3 -m py_compile src/*.py tests/*.py
apify validate-schema .actor/INPUT_SCHEMA.json
apify run --purge

Monetization angle

Position as a small B2B dependency-outage digest. Start low-friction on Apify with pay-per-result or free usage while measuring demand. If it gets usage, add stateful delta-only output, Slack/Telegram/webhook delivery, and predefined feed packs for startups, devtools, finance APIs, and cloud providers.