# Service Status & Outage Scanner: Is It Down + History (`centorprat/service-status-outage-scanner`) Actor

Give it status-page hosts/URLs (githubstatus.com, status.openai.com) or company names to auto-resolve. For each it reads the public Statuspage API into a status brief: current status, affected components, open incidents and recent incident history, with a reliability signal. Keyless.

- **URL**: https://apify.com/centorprat/service-status-outage-scanner.md
- **Developed by:** [Centor Prat](https://apify.com/centorprat) (community)
- **Categories:** Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.50 / 1,000 service checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Service Status & Outage Scanner: Is It Down + History

**Point it at a service and get a clean read on whether it's having problems — and how reliable it's
been.** Give a status-page host/URL (`githubstatus.com`, `status.openai.com`) or just a company name; it
reads the service's public **Statuspage API** and composes a brief: current status, which components are
down, open incidents, scheduled maintenance, and a count of recent incidents for a reliability signal.
Keyless, agent-callable, built to answer *"is this service up, and how often does it break?"*

> 📋 **Self-reported, verbatim.** This reads the company's **own** public status page — factual, not an
> independent uptime measurement and not an accusation. A company that reports incidents honestly may show
> more than one that underreports.

### ⚡ Why it's useful

The answer to "is X down?" and "how flaky has X been lately?" in one call — across your whole vendor
stack. Current status **and** a recent-incident count, so it's a due-diligence and monitoring signal, not
just a single up/down check.

### 📋 What each brief contains

| Field | Meaning |
|---|---|
| `signal` | `operational` / `minor-issue` / `partial-outage` / `major-outage` / `incident-open` |
| `status` | The status page's own description (e.g. "All Systems Operational") |
| `componentsAffected` | Components not currently operational, with their state |
| `openIncidents` | Current incidents (name, impact, status, link) |
| `recentIncidents` | Count of incidents in the recent window (reliability read) |
| `scheduledMaintenances` | Upcoming maintenance count |
| `statusPageUrl` | The resolved status page |

### 📥 Input

```json
{ "services": ["githubstatus.com", "status.openai.com", "dropbox"], "recentDays": 90 }
```

A status host/URL is used directly; a bare company name or domain is auto-resolved to common status-page
patterns (`status.<company>.com`, `<company>.statuspage.io`, …). One brief per service.

### 📤 Example output (real run, trimmed)

```json
{
  "service": "www.cloudflarestatus.com",
  "signal": "partial-outage",
  "status": "Partial System Outage",
  "componentsAffected": [ {"name": "...", "status": "degraded_performance"} ],
  "openIncidents": [ {"name": "...", "impact": "minor", "status": "monitoring"} ],
  "recentIncidents": { "days": 90, "count": 50 },
  "statusPageUrl": "https://www.cloudflarestatus.com"
}
```

In the same run, `githubstatus.com`, `status.openai.com` and `dropbox` all returned
`operational` — and `dropbox` resolved from just the company name.

### 💰 Pricing (pay-per-event)

- **Service checked — $0.01** per service whose status page resolves. Unresolved services are free.

### 💡 Use cases

- **Procurement / vendor due diligence:** check a vendor's reliability history before you sign.
- **Ops / SRE / support:** one call to see which of your dependencies are degraded right now.
- **Status dashboards / agents:** a normalized status signal across many services.

### 🔑 Keyless & agent-callable

No API keys, no accounts, no paid child Actors — just public Statuspage endpoints.

### 🚀 Ready-made tasks (one click)

- [Is It Down? SaaS Status Check (GitHub, Cloudflare, Discord)](https://apify.com/centorprat/service-status-outage-scanner/examples/is-it-down-saas-status-check)

### 🤖 For AI agents (MCP)

```
https://mcp.apify.com/?tools=actors,docs,centorprat/service-status-outage-scanner
```

Loads as `centorprat--service-status-outage-scanner`. Claude Code:

```
claude mcp add apify -- npx -y @apify/actors-mcp-server --actors centorprat/service-status-outage-scanner
```

# Actor input Schema

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

e.g. \["githubstatus.com", "status.openai.com", "dropbox"]. A status host/URL is used directly; a company name or domain is auto-resolved to common status-page patterns. One brief per service.

## `recentDays` (type: `integer`):

How far back to count incidents from the status page's incident history for the reliability signal.

## `webhookUrl` (type: `string`):

If set, the briefs are POSTed here as JSON when the run finishes.

## Actor input object example

```json
{
  "services": [
    "githubstatus.com",
    "status.openai.com"
  ],
  "recentDays": 90
}
```

# Actor output Schema

## `briefs` (type: `string`):

One brief per service: resolved status page, current status indicator and description, a signal, the components not operational, open incidents, scheduled maintenances, and a recent-incident count for a reliability read. Self-reported Statuspage data, reported verbatim.

# 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": [
        "githubstatus.com",
        "status.openai.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("centorprat/service-status-outage-scanner").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": [
        "githubstatus.com",
        "status.openai.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("centorprat/service-status-outage-scanner").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": [
    "githubstatus.com",
    "status.openai.com"
  ]
}' |
apify call centorprat/service-status-outage-scanner --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,centorprat/service-status-outage-scanner"
        }
    }
}
```

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/xMgv3smqEXMifUXKp/builds/JwPaj8pBf0hwjjFaI/openapi.json