Vendor status pages

Monitor vendor status pages and emit incident digests

SaaS Status Page & Incident Scraper fetches public vendor status pages and optional incident RSS/JSON feeds, then returns one executive digest per vendor: current state, incident counts, affected components, recommended actions, and evidence. It is third-party SaaS/cloud uptime monitoring — not HHS OCR breach disclosures, not Google News RSS, and not a login to internal portals.

$8.00 / 1,000 status incident digests ($0.008 per delivered vendor baseline or changed digest)

Open SaaS Status Page & Incident Scraper on Apify

Public status-page digests, not OCR breaches or news RSS

Use this page when the job is vendor status pages and incident feeds you list. Use HHS Healthcare Data Breach Change Scraper for public HHS OCR disclosures. Use RSS & Atom Feed Extractor for known-publisher feed XML. Use Google News Scraper for query-based headlines. Use Subprocessor & Trust Center Scraper for DPA and subprocessor page diffs.

This Actor HHS Healthcare Data Breach RSS & Atom Feed Extractor
Intent Vendor status-page incident digests Newly published HHS OCR disclosures Known-publisher feed items
Input vendors[] with statusPageUrl Date window and optional filters feedUrls (max 50)
What it reads HTTP status pages plus optional RSS/JSON HHS OCR Breach Portal rows Feed XML
Primary output One digest per vendor with evidence One disclosure digest per query window Item URL, title, timestamp

Store ID: taroyamada/status-page-incident-digest-monitor. HTTP plus JSON/RSS; no headless browser.

Use cases

How is SaaS Status Page & Incident Scraper different from HHS Healthcare Data Breach Change Scraper and RSS Feed Extractor?

This Actor fetches public vendor status pages and optional incident RSS/JSON feeds, then emits one executive digest per vendor: current state, incident counts, affected components, recommended actions, and evidence. Required input is vendors (objects with statusPageUrl). Store ID taroyamada/status-page-incident-digest-monitor. HHS Healthcare Data Breach Change Scraper monitors the public HHS OCR Breach Portal, not SaaS status pages. RSS & Atom Feed Extractor parses known-publisher feed XML for headlines and item URLs; it is not a vendor-incident digest. Google News Scraper is query-based news RSS. Use this Actor for third-party SaaS/cloud status pages you list.

What input is required?

vendors is required: an array of objects. Each vendor must have statusPageUrl. README examples that send vendors as strings, incidentSinceDays, or emitChangedOnly are not live schema fields. additionalProperties is false. Use datasetMode as the change filter.

Field Type Default Notes
vendors object[] required Each item needs statusPageUrl. Optional incidentFeedUrl, id, name, criticality, owner, tags
requestTimeoutSeconds integer 30 HTTP timeout per page/feed
userAgent string — Optional UA override
maxIncidentsPerVendor integer 10 Max incidents in evidence
incidentLookbackDays integer 30 0 means all feed items
delivery string dataset dataset or webhook
datasetMode string all all, changes_only, or action_needed
webhookUrl string — Required when delivery is webhook
notifyOnNoChange boolean false If false, skip webhook when nothing changed
snapshotKey string status-page-incident-snapshots Store example run uses status-page-incident-quickstart
concurrency integer 3 Parallel vendors. README: keep 2–3
nowIso string — Deterministic timestamp for tests
dryRun boolean false No snapshots, no webhook

Published schema prefill / starter vendor (Stripe is a capability example, not an affiliation):

{
  "vendors": [
    {
      "id": "stripe",
      "name": "Stripe",
      "criticality": "high",
      "owner": "Ops",
      "tags": ["payments", "core"],
      "statusPageUrl": "https://status.stripe.com",
      "incidentFeedUrl": "https://status.stripe.com/history.rss"
    }
  ],
  "delivery": "dataset",
  "datasetMode": "all",
  "snapshotKey": "status-page-incident-quickstart",
  "concurrency": 2,
  "dryRun": false
}

Run SaaS Status Page & Incident Scraper on Apify

What does a digest contain?

Published README fields include vendorId, vendorName, checkedAt, executiveSummary, incidentState, incidentCount, affectedComponents, actionNeeded, recommendedActions, changedSinceLastRun, evidence, and meta (statusPageUrl, incidentFeedUrl, criticality, owner, tags, parseSource, fingerprint, previousFingerprint, isFirstRun). The published Stripe sample is a README illustration, not a live coverage guarantee. Unreachable pages set incidentState unknown and actionNeeded true.

How do datasetMode, snapshots, and webhooks work?

datasetMode default is all: always emit the digest. changes_only emits when the fingerprint changed. action_needed emits only when actionNeeded is true. Keep snapshotKey constant for change detection. notifyOnNoChange default is false: skip webhook when nothing changed. dryRun true saves no snapshots and fires no webhook.

Does this Actor log into vendor portals or render a browser?

No. It uses HTTP plus JSON/RSS parsing without a headless browser. It is not for authenticated internal portals and it does not bypass anti-bot. incidentFeedUrl is optional. Only scan public status pages you are authorized to monitor.

How is SaaS Status Page & Incident Scraper priced?

Billing is pay per event. The live Store card is $8.00 / 1,000 status incident digests. The billed event is Status incident digest (apify-default-dataset-item) at $0.008, charged for one delivered vendor status baseline or changed incident digest. There is no Actor Start on the current pricing tab. The README Cost section that still quotes $0.01 start plus $0.003 per item is stale.

$8.00 per 1,000 status incident digests ($0.008 per delivered digest)

See SaaS Status Page & Incident Scraper pricing on Apify

Limits to keep in mind

Open SaaS Status Page & Incident Scraper on Apify

Related pages