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

{ "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)

{
  "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)

🤖 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