Statuspage Incident Digest

Monitor dozens of vendor status pages in one run. Give this Actor a list of public status pages powered by Atlassian Statuspage (GitHub, OpenAI, Atlassian, Cloudflare, Discord, Dropbox, Twilio and thousands more) and it returns one clean, normalized row per incident: name, status, impact, start and resolution time, duration, affected components and a permanent link.

No browser, no proxies, no login. The Actor only reads the official public JSON endpoint every Statuspage site exposes (/api/v2/incidents.json), so runs are fast, cheap and reliable.

Who is it for?

• SRE / DevOps teams who want one feed of upstream outages for every SaaS dependency.
• IT procurement and vendor-risk teams comparing vendor reliability (incident counts, impact, time-to-resolve).
• MSPs and agencies reporting third-party incidents to clients.
• AI agents and automations that need a structured "is vendor X having problems right now?" signal.

How it works

1. You enter status page URLs, e.g. https://www.githubstatus.com or just status.openai.com. Any path is ignored; only the origin is used.
2. For each page the Actor calls {origin}/api/v2/incidents.json (the ~50 most recent incidents).
3. Optional filters are applied (since, onlyUnresolved, maxItems).
4. Each incident is saved to the dataset. A run summary is stored in the key-value store under SUMMARY.

Pages that fail (not a Statuspage site, DNS error, timeout) are logged and listed in SUMMARY.failures; they are never charged.

Input

Field	Type	Description
pageUrls	array of strings (required)	Public Statuspage URLs.
maxItems	integer, 1–50 (default 50)	Max incidents per page.
since	ISO date (optional)	Skip incidents that started before this, e.g. 2026-10-01.
onlyUnresolved	boolean	Only incidents that are still open.
includeUpdates	boolean	Attach the full update timeline (status + message).

{
  "pageUrls": ["https://www.githubstatus.com", "https://status.openai.com"],
  "maxItems": 20,
  "since": "2026-10-01"
}

Output

{
  "id": "93njd414rpbx",
  "name": "Incident with Actions, Pull Requests and Issues",
  "status": "resolved",
  "impact": "minor",
  "started_at": "2026-10-12T12:21:47.965Z",
  "resolved_at": "2026-10-12T20:16:07.447Z",
  "duration_minutes": 474,
  "is_resolved": true,
  "components": ["Issues", "Pull Requests", "Actions"],
  "shortlink": "https://stspg.io/flldq0dn2wdz",
  "page": "GitHub",
  "page_url": "https://www.githubstatus.com",
  "source_url": "https://www.githubstatus.com/api/v2/incidents.json"
}

Export as JSON, CSV, Excel or via the Apify API, or connect it to Slack, Zapier, Make or webhooks.

Pricing (pay per event)

You only pay for results:

• Actor start – small flat fee per run.
• Status page checked – per page successfully fetched.
• Incident returned – per incident row written to the dataset.

Set a maximum cost per run in the run options; the Actor stops cleanly when the limit is reached. Tip: use since or onlyUnresolved on scheduled runs to pay only for new incidents.

Scheduling tip

Create a Schedule (e.g. every 15 minutes) with onlyUnresolved: true and a webhook or Slack integration to get alerted when any of your vendors has an open incident.

FAQ

Which sites work? Any status page hosted on Atlassian Statuspage (most have a "Powered by Atlassian Statuspage" footer). Custom-built status pages are not supported.

Why only ~50 incidents? That is what the public endpoint returns. Schedule the Actor to build your own history.

Is this legal? The Actor reads only public, unauthenticated JSON that status pages publish for exactly this purpose. It does not log in, bypass protections or collect personal data.

Something broke? Open an issue on the Actor's Issues tab and include the page URL.