SaaS Status Page Monitor: Outages, Incidents & Maintenance avatar

SaaS Status Page Monitor: Outages, Incidents & Maintenance

Pricing

from $0.50 / 1,000 status checks

Go to Apify Store
SaaS Status Page Monitor: Outages, Incidents & Maintenance

SaaS Status Page Monitor: Outages, Incidents & Maintenance

Monitor the status pages of 60 SaaS vendors (GitHub, OpenAI, Cloudflare, Vercel, Shopify, Zoom…) or any Atlassian Statuspage-compatible page. Get current status, outages, incidents and maintenance, or only what changed since your last run.

Pricing

from $0.50 / 1,000 status checks

Rating

0.0

(0)

Developer

Folt Labs

Folt Labs

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a month ago

Last modified

Categories

Security

Limited permissions

Share

SaaS Status Page Monitor — Outages, Incidents & Maintenance

Check the status of 60 SaaS vendors your business depends on — GitHub, OpenAI, Anthropic, Cloudflare, Vercel, Shopify, Zoom, Twilio, Datadog, Atlassian and more — or any Atlassian Statuspage-compatible status page (e.g. Postman, HashiCorp, Snowflake, Telerik). Get the current status, active incidents and maintenance in one clean dataset, or schedule it and receive only what changed since your last run.

Why use it

  • 📋 Built-in catalog of 60 vendors (verified) — or add any status page URL
  • 🚦 Current status: overall indicator, degraded components, active incidents and maintenance
  • 🔔 Change alerts: new, updated and resolved incidents plus status changes since your previous run — pair it with Apify integrations (Slack, email, webhooks)
  • 🗂️ One schema for every vendor, with latest update text and optional full update history
  • ⚡ Fast and cheap: small JSON requests, no browser — the whole catalog checks in seconds
  • 🛡️ Safe: only public status pages are fetched; private/internal addresses are blocked

How to use

  1. Add vendors (github, openai, cloudflare…) or status page URLs — or tick Monitor all catalog vendors.
  2. Snapshot mode gives you the current state; set Include resolved incidents from the last N days for recent history.
  3. For alerting, choose Changes mode and schedule the Actor (e.g. every 5–15 minutes). The first run is a baseline: every page's status plus currently active incidents.

Input example

{
"pages": ["github", "openai", "vercel", "https://status.example-saas.com"],
"mode": "changes",
"includeMaintenances": true
}

Ready-made recipes

Save an input as a Task, add a Schedule and an Integration in Apify Console — no code.

GoalInput highlightsScheduleSend results to
Outage alerts for your stackthe vendors you depend on, mode: "changes"every 5–15 minSlack / Teams / PagerDuty / email (webhook or Integrations tab)
Morning status reportyour vendor list, mode: "snapshot"dailyemail / Google Sheets
Incident history for SLA reviewsmode: "snapshot", lookbackDays: 30, includeUpdateHistory: truemonthlydataset export (CSV/Excel/JSON)

Output

Three record types share one dataset: status (one per page), incident and maintenance. Failed pages produce an error record (never charged).

{
"type": "status",
"vendor": "cloudflare",
"pageName": "Cloudflare Status",
"pageUrl": "https://www.cloudflarestatus.com",
"indicator": "major",
"description": "Partial System Outage",
"degradedComponents": [
{ "name": "Accra, Ghana - (ACC)", "status": "degraded_performance", "group": "Africa" },
{ "name": "Arica, Chile - (ARI)", "status": "major_outage", "group": "Latin America & the Caribbean" }
],
"activeIncidents": 2,
"activeMaintenances": 0,
"checkedAt": "2026-10-06T10:28:49.912Z"
}
{
"type": "incident",
"vendor": "cloudflare",
"id": "tl0vrgjy99r0",
"name": "Cloudflare One Clients are incorrectly challenged on some sites",
"status": "identified",
"impact": "minor",
"startedAt": "2026-09-22T19:23:17.000Z",
"updatedAt": "2026-09-23T11:02:41.000Z",
"resolvedAt": null,
"url": "https://www.cloudflarestatus.com/incidents/tl0vrgjy99r0",
"affectedComponents": ["Cloudflare One Client"],
"latestUpdate": "The issue has been identified and a fix is being implemented.",
"changeType": "new"
}
FieldValues
indicatornone, minor, major, critical, maintenance
status (incident)investigating, identified, monitoring, resolved, postmortem
status (maintenance)scheduled, in_progress, verifying, completed
changeTypeChanges mode: baseline / status-changed (status records), new / updated / resolved (incidents)

Pricing

WhatPrice
Each status record$0.0005 ($0.50 per 1,000)
Each incident or maintenance record$0.001 ($1.00 per 1,000)
Each run$0.001
Platform usageincluded — you pay nothing else

In Changes mode a check where nothing changed returns no records, so monitoring every 15 minutes costs about $0.10 a day (~$3 a month) plus whatever changes. Cap any run with maximum cost per run — the Actor stops cleanly.

Built-in catalog

1password, airtable, akamai, amplitude, anthropic, apify, asana, atlassian-jira, bitbucket, canva, circleci, clerk, cloudflare, cohere, coinbase, confluence, confluent, contentful, datadog, digitalocean, discord, docker, dropbox, elastic, expo, figma, flyio, github, groq, hubspot, launchdarkly, linear, linode, loom, mailgun, miro, mixpanel, mongodb, netlify, newrelic, notion, npm, openai, planetscale, reddit, render, sanity, segment, sendgrid (Twilio's page), sentry, shopify, squarespace, supabase, trello, twilio, typeform, upstash, vercel, webflow, zapier, zoom.

Missing a vendor? If its status page is Statuspage-compatible (it serves /api/v2/summary.json), just paste its URL.

FAQ

Which status pages work? Any page that serves the Statuspage v2 JSON API — Atlassian Statuspage and compatible hosts such as incident.io. Custom-built status pages (e.g. Stripe, Slack, Heroku) are not supported yet.

How does Changes mode remember? In a key-value store in your Apify account (status-page-monitor-state), keyed by your page list or Watchlist name.

Is this an uptime monitor? No — it reports what vendors publish on their status pages. It doesn't ping your own services.