# SaaS Status Monitor — real incident & outage tracking (`agent_muse/saas-status-monitor`) Actor

Stop learning about outages from your users. Monitors official status pages (statuspage.io) of the services you depend on — real vendor-published incidents, component health and scheduled maintenance. One run, full operational picture.

- **URL**: https://apify.com/agent\_muse/saas-status-monitor.md
- **Developed by:** [John Israel Lofamia](https://apify.com/agent_muse) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

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 Monitor

Track **real** SaaS outages from official status pages — not synthetic ping
checks. Reads the statuspage.io v2 API (keyless, no registration), the same
source of truth that GitHub, OpenAI, Cloudflare, Atlassian, Zoom and
thousands more publish their incidents to.

### What it collects per run

- **Headline status** per service: operational / minor / major / critical
  incident, with the vendor's own status text.
- **Incident history**: name, status (investigating → resolved), impact
  level, start/resolve times, number of vendor updates, link to the incident.
- **Scheduled maintenance**: upcoming windows with start/end times.
- **Components** (optional): per-component health, degraded ones first.

### Inputs

- **Services** (default: GitHub, OpenAI, Cloudflare status pages): any
  statuspage.io-powered status page URLs.
- **Incident history (days)** (default 7, max 90).
- **Include resolved incidents** (default on).
- **Include components** (default on).
- **Max results** (default 100, max 1000): headlines and newest incidents
  come first.

### Notes

- Pages that aren't on statuspage.io get one graceful error row instead of
  crashing the run — the rest of the services still report.
- Re-run on a schedule to catch new outages the moment vendors acknowledge
  them.

# Actor input Schema

## `daysBack` (type: `integer`):

How far back to pull incident history (days).

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

Include one row per service component (degraded components first).

## `includeResolved` (type: `boolean`):

Include resolved incidents in the history, not just active ones.

## `maxResults` (type: `integer`):

Maximum rows to return. Status headlines and newest incidents come first.

## `services` (type: `array`):

Status page URLs to monitor. Must be statuspage.io-powered pages (GitHub, OpenAI, Cloudflare, Atlassian, Zoom, ...).

## Actor input object example

```json
{
  "daysBack": 7,
  "includeComponents": true,
  "includeResolved": true,
  "maxResults": 100,
  "services": [
    "https://www.githubstatus.com",
    "https://status.openai.com",
    "https://www.cloudflarestatus.com"
  ]
}
```

# Actor output Schema

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

Link to the dataset with service statuses, incidents, maintenances and component rows.

# 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 = {
    "services": [
        "https://www.githubstatus.com",
        "https://status.openai.com",
        "https://www.cloudflarestatus.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("agent_muse/saas-status-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 = { "services": [
        "https://www.githubstatus.com",
        "https://status.openai.com",
        "https://www.cloudflarestatus.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("agent_muse/saas-status-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 '{
  "services": [
    "https://www.githubstatus.com",
    "https://status.openai.com",
    "https://www.cloudflarestatus.com"
  ]
}' |
apify call agent_muse/saas-status-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,agent_muse/saas-status-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/vkxPkVXbpia12U55M/builds/ewCcCCNX0Uwuv5Udo/openapi.json