# Statuspage Incidents Monitor for Vendor Status Pages > Statuspage incidents monitor: read vendor status pages for components, incidents and maintenance in JSON. Compare a snapshot to see changed services. URL: https://cliqtomedia.com/actors/statuspage-incidents-monitor/ Category: Developer & website monitoring · Status: coming soon · Apify profile: https://apify.com/cliqtomedia?fpr=cliqto Check the status pages of vendors you use, like GitHub or Cloudflare. You get status, components, recent incidents and planned maintenance. A snapshot shows what changed. ## How to use it: 3 steps 1. **Follow us on Apify.** The tool is built and waits in the queue for the Apify Store. Apify is the cloud platform where our tools run. 2. **Paste your input and press Start.** No code needed: you fill in a form (the input). It already has a working example. For example: `github` in Official status pages. Each start is one run. 3. **Download the results.** When the run ends, the results are in a table (the dataset). Open Output, press Export and pick Excel or CSV. JSON and the API are there too. ## What it does Read vendor Statuspage APIs and get service status, components, incidents and planned maintenance in JSON. Compare your previous snapshot to find changed services. ## Price Prices will be shown after release. ## Questions ### Does a green status mean the service is up? Not always. It shows what the vendor posts, not its real uptime. ### Do I get the full incident history? No. You get the vendor's latest feed, often 50 incidents, plus open ones. ### Which status pages work? Vendor pages that use the Statuspage JSON API, up to 50 per run. ### Do unchanged services cost money? Yes. Each checked service has one fee. Incidents have no extra fee. ## Data fields - `service` (string): Vendor name from the status page. - `pageUrl` (string): Normalized requested HTTPS status page. - `pageId` (string): Vendor page ID, verified across both API responses. - `overallIndicator` (string): Raw vendor overall indicator such as none, minor, major or critical. - `overallDescription` (string): Vendor text describing the overall status. - `components` (array): Current component IDs, names, states and update dates; empty when disabled. - `incidents` (array): Latest incidents feed plus all unresolved incidents from the summary, filtered by update date. - `scheduledMaintenances` (array): Upcoming or active planned work from the summary API. - `provider` (string): Status API format, not an endorsement or an uptime measurement. - `sourceUrl` (string): Summary API URL; recent history comes from incidents.json on the same page. - `sourceUpdatedAt` (string): Page update time supplied by the vendor; null when absent. - `fetchedAt` (string): UTC time when this service record was normalized. - `dataLicence` (null): Null because the vendor API supplies no data licence statement. - `historyCoverage` (string): Explicit bounded feed coverage; the full incident archive is not fetched. - `changeType` (string): Comparison with the supplied snapshot: new, changed, or unchanged. - `status` (string): Complete means this service was read within the documented feed coverage. Read RUN_SUMMARY for run-level partial failures. ## Input settings - `statusPages` (array, required): 1–50 official vendor Statuspage URLs or names: github, atlassian, cloudflare, digitalocean, discord, reddit. HTTPS root URLs only; duplicates are checked once. Use only pages operated by the vendor. - `includeComponents` (boolean): Include component IDs, names, statuses and update times in each service record. Turn off to reduce output size. - `incidentsSince` (string): Optional UTC date (YYYY-MM-DD) or ISO timestamp. Keep resolved incidents updated on or after this time. Always keep unresolved incidents, even when older. Reads the latest incident feed only. - `previousSnapshot` (object): Paste the complete SNAPSHOT record from your previous run. Version 1, maximum 1 MB and 50 pages. Use the same includeComponents and incidentsSince values. Previously seen incidents are retained; no automatic shared state. - `onlyChanges` (boolean): Save only services with new or changed status, components, incident updates or maintenance. The first run returns every service. Unchanged checks still read the API and charge the start fee. ## Step by step on Apify 1. Open Input. Keep the five sample names in `statusPages`. 2. Keep `includeComponents: true` and `onlyChanges: false`. 3. Click Start. 4. Open the Services dataset view. Check `service` and `overallIndicator`. 5. Open Status details for the nested lists. Export JSON for full nested data, or CSV for the service table. 6. Open the output links for `RUN_SUMMARY` and `SNAPSHOT`. ## Use cases | Task | Settings | Result | |---|---|---| | Refresh a vendor status dashboard | `onlyChanges: false` | One current record per checked service. | | Check for updates before sending an alert | Prior snapshot and `onlyChanges: true` | Only services with new or changed observations. | | Review recent incident updates | `incidentsSince` | Recently updated resolved incidents plus all unresolved incidents in the available feed. | | Track planned work | Any normal run | Upcoming or active maintenance in each service record. | ## Tips - Start with the five sample vendors. Then add your own status page URL. - Save the SNAPSHOT and use it next run with only changes on. - Keep the same component and date settings when you compare runs. ## Limits `CHARGE_LIMIT` gives a successful run with `partial` and preserves delivered results. A source error, bad response, deadline or graceful cancellation gives a failed run with an error or partial summary. Earlier saved rows remain. The Actor stops at the first source failure. It does not invent a green record for unread pages. A valid service with no incidents still returns its status record. - Up to 50 URL entries, checked once per distinct page. Custom URLs must be vendor-operated pages with the compatible JSON API. - Latest incident feed only. Some vendors have fewer incidents or more components. Maintenance is only the upcoming/active list in the summary. - Two source requests per page, with up to two redirects and two attempts per request. Request cap: 200; body cap: 2 MB; total body cap: 16 MB. - Source work stops after 150 seconds, even with a larger platform timeout. Default timeout is 300 seconds. Memory is fixed at 256 MB; other memory levels are rejected with `RESOURCE_ERROR`. - No key, login, CAPTCHA bypass, proxy or independent uptime probe. - Data may change between the summary and history requests. Vendor publishing delays also affect freshness. - No open data licence is supplied. Source text belongs to its provider. Follow the vendor's terms. See the GitHub API and Atlassian terms. ## Sample result ```json { "service": "GitHub", "pageUrl": "https://www.githubstatus.com", "pageId": "kctbh9vrtdwd", "overallIndicator": "none", "overallDescription": "All Systems Operational", "components": [ { "id": "0l2p9nhqnxpd", "name": "Visit www.githubstatus.com for more information", "status": "operational", "updatedAt": "2025-03-19T05:00:21.309Z" } ], "incidents": [ { "id": "hcbtzksccj2f", "name": "Disruption with some GitHub services", "status": "resolved", "impact": "minor", "createdAt": "2026-08-26T15:09:03.575Z", "updatedAt": "2026-08-31T20:41:06.290Z", "resolvedAt": "2026-08-26T16:07:52.512Z", "shortlink": "https://stspg.io/4s4bvnc0frrj", "lastUpdateText": "Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/y1t7p9fzrlj2", "lastUpdateAt": "2026-08-26T16:07:52.512Z", "scheduledFor": null, "scheduledUntil": null } ], "scheduledMaintenances": [], "provider": "atlassian-statuspage-v2", "sourceUrl": "https://www.githubstatus.com/api/v2/summary.json", "sourceUpdatedAt": "2026-10-13T16:19:26.788Z", "fetchedAt": "2026-10-13T17:26:09.319Z", "dataLicence": null, "historyCoverage": "latest_incidents_feed_and_all_unresolved", "changeType": "new", "status": "complete" } ``` ## Use cases with this tool - [Know what your competitors do](https://cliqtomedia.com/actors/use-cases/competitor-monitoring/): See what your competitors launch, hire, change and advertise. Every week, without opening their sites. ## Similar tools - [Link Route Audit — Bulk HTTP Status & Redirects](https://cliqtomedia.com/actors/bulk-url-status-redirect-checker/) - [GitHub Releases Monitor & Scraper](https://cliqtomedia.com/actors/github-releases-monitor-scraper/) - [Software End-of-Life Checker](https://cliqtomedia.com/actors/software-end-of-life-checker/) - [Dependency Vulnerability Scanner (OSV)](https://cliqtomedia.com/actors/osv-dependency-vulnerability-scanner/) - [GitHub Repositories & Users Search (No Login)](https://cliqtomedia.com/actors/github-search/) - [OpenAPI Catalog & Breaking Change Detector](https://cliqtomedia.com/actors/openapi-spec-catalog-diff/)