Statuspage Scraper
Pricing
Pay per event
Statuspage Scraper
Get any company's Atlassian Statuspage as clean JSON — components, incidents, uptime status. Free to start, API & MCP ready.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Turgay NANTA
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Share
Get any company's Atlassian Statuspage as clean JSON: components with live status plus recent incidents. One click, no required fields, no LLM.
What it does
Atlassian Statuspage is the most widely used status-page platform — Cloudflare, HubSpot, Slack, GitHub-adjacent tools and thousands of other companies publish live system status through it, by design public so customers don't have to ask support. This actor reads any company's public Statuspage and returns both the live component list (name, status, group) and recent incidents (name, impact, status, first update) as clean JSON. Give it a company's Statuspage subdomain (cloudflare) and get its full status picture in one call.
Why this one:
- Official public v2 JSON API — no HTML parsing, no proxies
- Returns BOTH components and incident history in one run
- Works on any of the thousands of companies on Statuspage
- No LLM anywhere — deterministic output, predictable costs, no hallucinated fields
- Clean by default — canonical URLs (tracking parameters stripped), parsed numbers, merged duplicates
Quick start (no code)
- Click Try for free / Start — every field has a working default, nothing is required.
- (Optional) change query to what you need.
- Open the Dataset tab when the run finishes → export as JSON, CSV or Excel.
Input
| Field | Required | Default | Description |
|---|---|---|---|
query | no | cloudflare | Statuspage subdomain. Find it in the status page URL: <subdomain>.statuspage.io (many companies also mirror it on a custom domain using the same subdomain name). |
maxResults | no | 20 | Maximum clean results (capped at 500) |
enrich | no | false | Deterministic enrichment per record — see below |
monitor | no | false | Compare with the previous run, flag NEW records only |
Example input:
{"query": "cloudflare","maxResults": 50}
Output
Real example record (from a live run):
{"id": "57ctn3f2qsyj","title": "Amsterdam, Netherlands - (AMS)","url": "https://www.cloudflarestatus.com","seller": "Cloudflare","status": "operational","created_at": "2014-10-27T20:35:05.259Z","updated_at": "2026-07-23T16:04:59.620Z","record_type": "component","completeness": 0.5}
The final _summary row carries run totals (total_clean, deduped, enriched); in monitor mode a _changes row lists keys new since the last run.
Field reference
| Field | Meaning |
|---|---|
id | Component or incident ID (stable, deduplication key) |
title | Component name, or incident name for incident rows |
url | Status page URL, or incident shortlink for incident rows |
seller | Company/page display name |
status | Component status, or incident status (resolved/monitoring/investigating) for incident rows |
impact | Incident severity — present on incident rows only |
record_type | component or incident |
price / price_text | Parsed numeric value + original text, when the source publishes one |
completeness | 0–1 filled-fields score (with enrich) |
Use cases
- Vendor reliability tracking — monitor the uptime of infrastructure and SaaS you depend on.
- Incident history research — pull recent incidents with impact levels for a post-mortem or vendor review.
- Status-change alerts — schedule with monitor mode;
change-alertfires on new components or incidents. - Dashboards — aggregate a portfolio of vendors' status into one internal board.
- AI agents — live 'is vendor X having issues right now?' answers via MCP.
Enrichment (optional, charged only when it produces something)
Set enrich: true and every record additionally gets: e-mail addresses extracted from the description (when present), the canonical domain of the record's URL, and a completeness score (0–1, how many core fields are filled). Deterministic — the same input always yields the same output — and you are only charged for records that actually got enriched. Records where enrichment adds nothing are free.
Monitor mode — change alerts on a schedule
Set monitor: true and the actor compares the current run with the previous one (per-actor named storage) and flags only NEW records. Combine with Apify Schedules for a daily/hourly watch: the _changes summary row lists what appeared since the last run, and the change-alert event is charged per new record only — an unchanged run costs you almost nothing.
Use it from your code
Python
from apify_client import ApifyClientclient = ApifyClient("<YOUR_API_TOKEN>")run = client.actor("EnezLi/statuspage-scraper").call(run_input={ "query": "cloudflare", "maxResults": 50 })for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item)
JavaScript
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });const { defaultDatasetId } = await client.actor('EnezLi/statuspage-scraper').call({ "query": "cloudflare", "maxResults": 50 });const { items } = await client.dataset(defaultDatasetId).listItems();console.log(items);
curl
curl -X POST "https://api.apify.com/v2/acts/EnezLi~statuspage-scraper/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>" \-H "Content-Type: application/json" \-d '{ "query": "cloudflare", "maxResults": 50 }'
Use it with AI agents (MCP)
This actor is agent-ready: it appears in Apify's AGENTS / MCP servers catalog, so any MCP-capable assistant (Claude, custom agents, LangGraph tools) can discover and call it with a one-line tool call — zero required fields means an agent can run it safely with defaults. Connect your agent to the Apify MCP server and ask for live data in natural language.
Pricing — Pay-Per-Event, start is free
| Event | When charged |
|---|---|
| Actor start | Free ($0) — try it with one click |
result | Per clean result returned |
enrichment | Only per record that actually got enriched |
change-alert | Monitor mode: per NEW record since the previous run |
No subscription, no minimum. Volume discounts apply automatically through Apify account tiers (up to −44% on GOLD). Typical run cost example: 20 results ≈ a few cents total — you can predict your bill from the numbers above before you run.
Is this legal?
This actor collects publicly available data only — the same information any visitor sees in a browser, via public endpoints. It does not bypass logins, collect private personal data, or store credentials. You are responsible for using the output in compliance with the source site's terms and the laws that apply to you (e.g. GDPR when the output contains personal data).
Support & feedback
Found a bug, need another field, or want a variant for a related platform? Open an issue on the Issues tab — issues are monitored and answered, and frequently-requested fields get added to the standard output. The actor is maintained as part of a scraper family built on one shared, tested core (bugs fixed once are fixed everywhere).
Changelog
- 0.1 (2026-07) — initial public release: search, dedup, optional enrichment, monitor mode, PPE pricing.
Limitations (honest ones)
Reads Statuspage's official public v2 API; private or unpublished pages return zero rows. Incident update history is summarized (first update only), not the full timeline.
FAQ
How do I find a company's Statuspage subdomain?
Open the company's status page; the hosted URL is <subdomain>.statuspage.io even when a custom domain like status.company.com is shown instead — try the company's obvious short name first.
Why do I get fewer incidents than components?
The actor fills up to maxResults with components first, then incidents — raise maxResults to get more of both, or note that not every company has recent incidents.
A subdomain returned zero results — why?
Either it's misspelled, or the company doesn't host on Statuspage. The run ends cleanly either way — nothing charged for results.
Do I need an API key or account on the source platform?
No. The actor uses public endpoints — you only need your Apify account.
Does it use AI / an LLM?
No. The core is fully deterministic: same input, same output, no hallucinations, no per-token costs.
Can I run it on a schedule?
Yes — use Apify Schedules; combine with monitor mode to pay only for what's new.
What's the maximum number of results?
500 per run (memory-safe cap). Run multiple queries or schedule runs for more.
How is my bill calculated?
Only from the events in the Pricing table — start is free, and there is no subscription.