Vendor Status Incident Alerts: GitHub, GCP, Statuspage

Monitor incidents and outages across vendor status pages including GitHub, Google Cloud, AWS, and Atlassian Statuspage.

SRE teams, DevOps engineers, and integration developers use this actor to track critical vendor service health, monitor active degradations, and trigger alerts as soon as an incident or resolution is posted. Turn on monitoring mode (onlyNewSinceLastRun) and run on a schedule to get only new incidents and status updates since your previous run — quiet runs with no new incidents bill zero PPE events.

How to use

1. In the Apify Console. Open the actor page and click Start — the vendors field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~vendor-status-incident-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"vendors":["githubstatus.com","status.cloud.google.com"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "vendors": [
    "githubstatus.com",
    "status.cloud.google.com"
  ]
}

One vendor domain or status page URL per line (e.g. githubstatus.com, status.cloud.google.com, status.aws.amazon.com). Atlassian Statuspage instances, Google Cloud Status, and AWS Health RSS are supported. Accepted formats: githubstatus.com, status.cloud.google.com, status.aws.amazon.com.

Output

One row per incident (when expanded, default), or one row per vendor in grouped mode:

query	found	status	vendor	vendorDomain	incidentId	title	incidentStatus	impact	startedAt	resolvedAt	updatedAt	incidentUrl	sourceUrl	latestUpdate	affectedComponents	isNew	changeType	firstSeenAt	vendorSummary	incidentCount	monitorStatus	incidents	scrapedAt
status.cloud.google.com	true	OK	Google Cloud	status.cloud.google.com	Xs2XTHzAVC9YnafnPyzj	Multiple services were experiencing issues in the europe-west2 region.	resolved	medium	2026-10-20T06:00:00.000Z	2026-10-20T12:08:00.000Z	2026-10-28T00:38:39.000Z	https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj	https://status.cloud.google.com/incidents.json	## Incident Report ### Summary On Monday, 19 Oct 2026 (Tuesday, 20 Oct BST), a data center facility that hosts europe-west2-b, experienced an external electrical power disruption. This resulted...	["AlloyDB for PostgreSQL","Apigee","BigQuery Data Transfer Service","Cloud Data Fusion","Cloud Filestore","Cloud Firestore","Cloud Load Balancing","Cloud Memorystore","Cloud NAT","Cloud Run","Cloud...				Google Cloud: 3 incident(s) in last 30d	3		<all incidents (grouped list)>	2026-11-01T14:20:37.588Z

A miss comes back as a row with "found": false and is never charged. Missing fields (e.g. resolvedAt on ongoing incidents) are always null, never 0 or "".

Limits

• Supports public Atlassian Statuspage v2 APIs (/api/v2/incidents.json), Google Cloud Status (incidents.json), and AWS Service Health RSS feeds (/rss/all.rss).
• Status pages protected behind authentication, private VPNs, or login walls are not supported.
• Standard request timeout is 120 seconds per vendor.

Pricing

• Incident returned: $3 per 1,000 incidents

Plus a $0.00005 start fee per run. Each event above is billed independently, only when it actually returns data — misses (found:false) are never charged.

Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token, and no account of your own beyond an Apify login.

Default multi-cloud vendor check (GitHub and Google Cloud, last 30 days).

{
  "vendors": [
    "githubstatus.com",
    "status.cloud.google.com"
  ],
  "sinceDays": 30,
  "maxItems": 20
}

Active outages and disruptions only.

{
  "vendors": [
    "githubstatus.com",
    "status.cloud.google.com",
    "status.aws.amazon.com"
  ],
  "statusFilter": "active",
  "sinceDays": 14
}

Scheduled incident alert (monitoring mode).

{
  "vendors": [
    "githubstatus.com",
    "status.cloud.google.com"
  ],
  "onlyNewSinceLastRun": true,
  "sinceDays": 7
}

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~vendor-status-incident-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"vendors":["githubstatus.com","status.cloud.google.com"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~vendor-status-incident-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"vendors":["githubstatus.com","status.cloud.google.com"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~vendor-status-incident-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"vendors":["{{vendor}}"]}, mapping the row's vendor into the vendors array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "vendor status page incident alerts" — the agent will find and run this actor.