# SaaS Status Page Monitor: Outages, Incidents & Maintenance (`folt/status-page-monitor`) Actor

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.

- **URL**: https://apify.com/folt/status-page-monitor.md
- **Developed by:** [Folt Labs](https://apify.com/folt) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 status checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

```json
{
  "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.

| Goal | Input highlights | Schedule | Send results to |
| --- | --- | --- | --- |
| **Outage alerts for your stack** | the vendors you depend on, `mode: "changes"` | every 5–15 min | Slack / Teams / PagerDuty / email (webhook or Integrations tab) |
| **Morning status report** | your vendor list, `mode: "snapshot"` | daily | email / Google Sheets |
| **Incident history for SLA reviews** | `mode: "snapshot"`, `lookbackDays: 30`, `includeUpdateHistory: true` | monthly | dataset 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).

```json
{
  "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"
}
```

```json
{
  "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"
}
```

| Field | Values |
| --- | --- |
| `indicator` | `none`, `minor`, `major`, `critical`, `maintenance` |
| `status` (incident) | `investigating`, `identified`, `monitoring`, `resolved`, `postmortem` |
| `status` (maintenance) | `scheduled`, `in_progress`, `verifying`, `completed` |
| `changeType` | Changes mode: `baseline` / `status-changed` (status records), `new` / `updated` / `resolved` (incidents) |

### Pricing

| What | Price |
| --- | --- |
| 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 usage | included — 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.

# Changelog

This Actor's version history is a separate document: https://apify.com/folt/status-page-monitor/changelog.md

# Actor input Schema

## `pages` (type: `array`):

Vendor names from the built-in catalog (e.g. github, openai, cloudflare, vercel, shopify, zoom, twilio, datadog, atlassian-jira) or any Statuspage-compatible status page URL (e.g. https://www.githubstatus.com). See the README for the full catalog.

## `monitorAllCatalogVendors` (type: `boolean`):

Adds all 60 vendors from the built-in catalog to the list above.

## `mode` (type: `string`):

Snapshot = current status of every page plus active incidents and maintenance. Changes = only what changed since your previous run (new/updated/resolved incidents, status changes) — ideal for scheduled alerts.

## `lookbackDays` (type: `integer`):

Snapshot mode only. 0 = only active incidents. Max 90.

## `includeMaintenances` (type: `boolean`):

Adds upcoming and in-progress maintenance windows.

## `includeComponents` (type: `boolean`):

Adds every component with its status to each status record. Degraded components are always included.

## `includeUpdateHistory` (type: `boolean`):

Adds all status updates of each incident (newest first). The latest update is always included.

## `stateKey` (type: `string`):

Changes mode only: names the memory of what you've already received. Leave empty to derive it from the page list.

## `maxConcurrency` (type: `integer`):

How many status pages to check in parallel.

## Actor input object example

```json
{
  "pages": [
    "https://www.githubstatus.com"
  ],
  "monitorAllCatalogVendors": false,
  "mode": "snapshot",
  "lookbackDays": 0,
  "includeMaintenances": true,
  "includeComponents": false,
  "includeUpdateHistory": false,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

One status record per page plus incident and maintenance records (or only changes, in Changes mode).

## `allFields` (type: `string`):

The same records with every field, as JSON.

## `summary` (type: `string`):

Per-input status, counts and anything that could not be processed.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "pages": [
        "https://www.githubstatus.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("folt/status-page-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "pages": ["https://www.githubstatus.com"] }

# Run the Actor and wait for it to finish
run = client.actor("folt/status-page-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "pages": [
    "https://www.githubstatus.com"
  ]
}' |
apify call folt/status-page-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,folt/status-page-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lfxX491DwIA9XLXUs/builds/uVFPQbYnluVgKXnO9/openapi.json