# Statuspage

> Check whether the services you depend on are up, straight from their official status pages: GitHub, Cloudflare, OpenAI, Zoom, Twilio, Shopify and any other page run on Atlassian Statuspage or incident.io. Get a service's status, check a whole list at once, check one component, and follow incidents and scheduled maintenance. No account or API key required.

App · Monitoring · 7 actions. Web page: https://docs.lodol.com/docs/integrations/statuspage

## Actions

### Check a component

Check one part of a service, such as GitHub Actions or the OpenAI API: its status, whether it is working, and any open incident that names it, with a sentence for a message.

**Inputs**

- Status page (`page`, text, required): The status page to read: pick a service from the list (GitHub, Cloudflare, OpenAI, Zoom and 75 more), or type the address of any status page run on Atlassian Statuspage or incident.io, such as www.githubstatus.com. A service's name, such as Discord, works too.
- Component (`component`, text, required): The component, as the status page names it. Pick it from the list, which is read from the page, or type its name; where two groups have one of the same name, give 'Group / Component'.

**Outputs**

- `description` (text): What the component covers, as the page describes it.
- `group` (text): The group the page files it under, or null.
- `id` (text): The component's id on the page.
- `is_operational` (true/false): Whether the component is fully working.
- `name` (text): The component's name, such as Actions.
- `open_incidents` (list): Open incidents that name this component. incident.io pages do not say which components an incident affects, so this is empty for them.
- `page_name` (text): The status page's name, such as GitHub.
- `page_url` (text): The status page's address.
- `platform` (text): What runs the page: 'statuspage' (Atlassian Statuspage) or 'incident_io' (incident.io, which publishes no maintenance).
- `status` (text): operational, under_maintenance, degraded_performance, partial_outage or major_outage.
- `status_label` (text): The status in words, such as Partial outage.
- `summary` (text): A sentence summing it up, for a message.
- `updated_at` (text): When its status last changed (ISO 8601).

**Example output**

```json
{
  "description": "Workflows, Compute and Orchestration for GitHub Actions",
  "group": null,
  "id": "br0l2tvcx85d",
  "is_operational": true,
  "name": "Actions",
  "open_incidents": [],
  "page_name": "GitHub",
  "page_url": "https://www.githubstatus.com",
  "platform": "statuspage",
  "status": "operational",
  "status_label": "Operational",
  "summary": "GitHub Actions: operational.",
  "updated_at": "2026-10-07T15:32:02.136Z"
}
```

### Check several services

Check a list of status pages in one step, such as the services a product depends on, and get a verdict: whether any has issues, whether any has a major outage, and which ones. A page that cannot be read is reported in its place with the reason rather than stopping the run. Up to 25 pages per step.

**Inputs**

- Status pages (`pages`, list, required): The status pages to check: a list from an earlier step, or typed in with one on each line or separated by commas. Each may be a service's name, such as GitHub, or a status page's address. Up to 25 per step.

**Outputs**

- `any_issues` (true/false): Whether any page has issues.
- `any_major` (true/false): Whether any page reports a major outage.
- `count` (number): How many were checked.
- `issue_count` (number): How many have something degraded or down.
- `not_found` (list): The pages given that could not be read.
- `pages` (list): One entry per page given, in the same order.
- `pages_with_issues` (list): The names of the pages with issues, ready to put in a message.

**Example output**

```json
{
  "any_issues": false,
  "any_major": false,
  "count": 3,
  "issue_count": 0,
  "not_found": [
    "example.com"
  ],
  "pages": [
    {
      "components_with_issues": [],
      "description": "All Systems Operational",
      "error": "",
      "found": true,
      "has_issues": false,
      "indicator": "none",
      "is_major": false,
      "page": "GitHub",
      "page_name": "GitHub",
      "page_url": "https://www.githubstatus.com",
      "platform": "statuspage"
    },
    {
      "components_with_issues": [],
      "description": "All Systems Operational",
      "error": "",
      "found": true,
      "has_issues": false,
      "indicator": "none",
      "is_major": false,
      "page": "status.openai.com",
      "page_name": "OpenAI",
      "page_url": "https://status.openai.com",
      "platform": "incident_io"
    },
    {
      "components_with_issues": [],
      "description": "",
      "error": "example.com has no status page API: it answers 404 for /api/v2/summary.json. Only status pages run on Atlassian Statuspage, or that serve its API as incident.io's do, can be read.",
      "found": false,
      "has_issues": false,
      "indicator": "",
      "is_major": false,
      "page": "example.com",
      "page_name": "",
      "page_url": "",
      "platform": ""
    }
  ],
  "pages_with_issues": []
}
```

### Get a service's status

Read a service's status page: its own verdict, such as All Systems Operational, each component that is not working, the incidents still open and any maintenance in progress, with a sentence summing it up for a message. Works with GitHub, Cloudflare, OpenAI, Zoom and any status page run on Atlassian Statuspage or incident.io. No account or API key required.

**Inputs**

- Status page (`page`, text, required): The status page to read: pick a service from the list (GitHub, Cloudflare, OpenAI, Zoom and 75 more), or type the address of any status page run on Atlassian Statuspage or incident.io, such as www.githubstatus.com. A service's name, such as Discord, works too.

**Outputs**

- `component_count` (number): How many components the page lists.
- `components_with_issues` (list): Each component not operational, the most serious first.
- `description` (text): The page's own verdict, such as All Systems Operational.
- `indicator` (text): none, minor, major, critical or maintenance.
- `is_operational` (true/false): Whether everything on the page is working.
- `maintenances_in_progress` (list): Maintenance under way now. Always empty for incident.io pages, which do not publish it.
- `open_incidents` (list): The incidents not yet resolved.
- `page_name` (text): The status page's name, such as GitHub.
- `page_url` (text): The status page's address.
- `platform` (text): What runs the page: 'statuspage' (Atlassian Statuspage) or 'incident_io' (incident.io, which publishes no maintenance).
- `summary` (text): A sentence summing it up, for a message.
- `updated_at` (text): When the page last changed (ISO 8601).

**Example output**

```json
{
  "component_count": 40,
  "components_with_issues": [
    {
      "description": null,
      "group": "Latin America & the Caribbean",
      "id": "2htqrtyxmmtr",
      "is_operational": false,
      "name": "Arica, Chile - (ARI)",
      "status": "major_outage",
      "status_label": "Major outage",
      "updated_at": "2026-02-27T23:03:00.000Z"
    },
    {
      "description": null,
      "group": "Africa",
      "id": "p2w5bf74rw6p",
      "is_operational": false,
      "name": "Annaba, Algeria - (AAE)",
      "status": "major_outage",
      "status_label": "Major outage",
      "updated_at": "2026-08-24T12:32:47.000Z"
    }
  ],
  "description": "Partial System Outage",
  "indicator": "major",
  "is_operational": false,
  "maintenances_in_progress": [
    {
      "components": [
        "Reykjav\u00edk, Iceland - (KEF)"
      ],
      "id": "4ks86g48zrsw",
      "impact": "maintenance",
      "is_in_progress": true,
      "latest_update": {
        "at": "2026-10-09T02:01:08.025Z",
        "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.",
        "status": "in_progress"
      },
      "name": "KEF (Reykjav\u00edk) on 2026-10-09",
      "scheduled_for": "2026-10-09T02:00:00.000Z",
      "scheduled_until": "2026-10-09T06:00:00.000Z",
      "status": "in_progress",
      "url": "https://www.cloudflarestatus.com/incidents/4ks86g48zrsw"
    },
    {
      "components": [
        "Lisbon, Portugal - (LIS)"
      ],
      "id": "wnz6jjsfhtm2",
      "impact": "maintenance",
      "is_in_progress": true,
      "latest_update": {
        "at": "2026-10-09T00:01:07.376Z",
        "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.",
        "status": "in_progress"
      },
      "name": "LIS (Lisbon) on 2026-10-09",
      "scheduled_for": "2026-10-09T00:00:00.000Z",
      "scheduled_until": "2026-10-09T05:00:00.000Z",
      "status": "in_progress",
      "url": "https://www.cloudflarestatus.com/incidents/wnz6jjsfhtm2"
    }
  ],
  "open_incidents": [
    {
      "components": [
        "Cloudflare One Client"
      ],
      "created_at": "2026-09-22T19:23:17.000Z",
      "id": "tl0vrgjy99r0",
      "impact": "minor",
      "is_open": true,
      "latest_update": {
        "at": "2026-09-23T11:02:41.670Z",
        "body": "The issue has been identified and a fix is being implemented.",
        "status": "identified"
      },
      "name": "Cloudflare One Clients are incorrectly challenged on some sites",
      "resolved_at": null,
      "started_at": "2026-09-22T19:23:17.000Z",
      "status": "identified",
      "update_count": 2,
      "updated_at": "2026-09-23T11:02:41.000Z",
      "url": "https://www.cloudflarestatus.com/incidents/tl0vrgjy99r0"
    },
    {
      "components": [
        "WARP"
      ],
      "created_at": "2026-08-27T18:46:19.000Z",
      "id": "9g65dxfbcjln",
      "impact": "minor",
      "is_open": true,
      "latest_update": {
        "at": "2026-09-01T08:29:56.950Z",
        "body": "We are continuing to work on a fix for this issue.",
        "status": "identified"
      },
      "name": "Incorrect geo location for some Cloudflare WARP users",
      "resolved_at": null,
      "started_at": "2026-08-27T18:46:19.000Z",
      "status": "identified",
      "update_count": 2,
      "updated_at": "2026-09-01T08:29:56.000Z",
      "url": "https://www.cloudflarestatus.com/incidents/9g65dxfbcjln"
    }
  ],
  "page_name": "Cloudflare Status",
  "page_url": "https://www.cloudflarestatus.com",
  "platform": "statuspage",
  "summary": "Cloudflare Status: Partial System Outage. 16 components have issues: Latin America & the Caribbean Arica, Chile - (ARI) (major outage), Africa Annaba, Algeria - (AAE) (major outage), Oceania Canberra, ACT, Australia - (CBR) (major outage),\u2026",
  "updated_at": "2026-08-27T00:00:00.000Z"
}
```

### Get an incident

Get one incident from a status page with every update posted on it, newest first, to follow it or quote it. Give its id or a link to it, including an stspg.io short link.

**Inputs**

- Status page (`page`, text, required): The status page to read: pick a service from the list (GitHub, Cloudflare, OpenAI, Zoom and 75 more), or type the address of any status page run on Atlassian Statuspage or incident.io, such as www.githubstatus.com. A service's name, such as Discord, works too.
- Incident (`incident`, text, required): The incident's id, as List incidents returns it, or a link to it on the status page.

**Outputs**

- `components` (list): The components it affects. incident.io pages do not say, so this is empty for them.
- `created_at` (text): When it was posted (ISO 8601).
- `id` (text): The incident's id.
- `impact` (text): none, minor, major or critical.
- `is_open` (true/false): Whether the incident is still open.
- `latest_update` (object)
- `name` (text): The incident's title.
- `page_name` (text): The status page's name, such as GitHub.
- `page_url` (text): The status page's address.
- `platform` (text): What runs the page: 'statuspage' (Atlassian Statuspage) or 'incident_io' (incident.io, which publishes no maintenance).
- `resolved_at` (text): When it was resolved (ISO 8601), or null while open.
- `started_at` (text): When it started (ISO 8601).
- `status` (text): investigating, identified, monitoring, resolved or postmortem.
- `update_count` (number): How many updates it has.
- `updated_at` (text): When it was last updated (ISO 8601).
- `updates` (list): Every update on the incident, newest first.
- `url` (text): A link to the incident.

**Example output**

```json
{
  "components": [
    "Git Operations",
    "Issues"
  ],
  "created_at": "2026-10-07T17:17:05.776Z",
  "id": "qpfv5p86dmrl",
  "impact": "critical",
  "is_open": false,
  "latest_update": {
    "at": "2026-10-07T18:04:49.441Z",
    "body": "This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.",
    "status": "resolved"
  },
  "name": "Incident with Git Operations, Issues, Actions and Pull Requests",
  "page_name": "GitHub",
  "page_url": "https://www.githubstatus.com",
  "platform": "statuspage",
  "resolved_at": "2026-10-07T18:04:49.441Z",
  "started_at": "2026-10-07T17:17:05.768Z",
  "status": "resolved",
  "update_count": 2,
  "updated_at": "2026-10-07T18:04:49.479Z",
  "updates": [
    {
      "at": "2026-10-07T18:04:49.441Z",
      "body": "This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.",
      "components": [
        "Issues",
        "Git Operations"
      ],
      "status": "resolved"
    },
    {
      "at": "2026-10-07T18:00:49.016Z",
      "body": "All systems have recovered. We have applied mitigations and do not anticipate another recurrence.",
      "components": [
        "Issues",
        "Git Operations"
      ],
      "status": "monitoring"
    }
  ],
  "url": "https://stspg.io/4p8x0jnnsx7m"
}
```

### List components

List the parts of a service its status page tracks, such as GitHub's Actions or Cloudflare's data centers, each with its status and group. Narrow to one status, or to anything not operational, or by a word in the name.

**Inputs**

- Status page (`page`, text, required): The status page to read: pick a service from the list (GitHub, Cloudflare, OpenAI, Zoom and 75 more), or type the address of any status page run on Atlassian Statuspage or incident.io, such as www.githubstatus.com. A service's name, such as Discord, works too.
- Status (`status`, text): Only components with this status. One of: `operational`, `not_operational` (Anything but operational), `under_maintenance` (Under maintenance), `degraded_performance` (Degraded performance), `partial_outage` (Partial outage), `major_outage` (Major outage).
- Name contains (`search`, text): Only components whose name or group contains this, ignoring case, such as Europe or API.

**Outputs**

- `components` (list): The matching components, in page order.
- `page_name` (text): The status page's name, such as GitHub.
- `page_url` (text): The status page's address.
- `platform` (text): What runs the page: 'statuspage' (Atlassian Statuspage) or 'incident_io' (incident.io, which publishes no maintenance).
- `total` (number): How many matched.

**Example output**

```json
{
  "components": [
    {
      "description": null,
      "group": "Europe",
      "id": "57ctn3f2qsyj",
      "is_operational": true,
      "name": "Amsterdam, Netherlands - (AMS)",
      "status": "operational",
      "status_label": "Operational",
      "updated_at": "2026-10-09T04:10:59.000Z"
    },
    {
      "description": null,
      "group": "Europe",
      "id": "bm711sgbslfk",
      "is_operational": true,
      "name": "Athens, Greece - (ATH)",
      "status": "operational",
      "status_label": "Operational",
      "updated_at": "2026-04-08T02:32:38.000Z"
    }
  ],
  "page_name": "Cloudflare Status",
  "page_url": "https://www.cloudflarestatus.com",
  "platform": "statuspage",
  "total": 2
}
```

### List incidents

List a service's recent incidents, open ones first and then the newest, each with its impact, the components it affects and its latest update. Narrow to open or resolved ones, or to a minimum impact. Status pages publish the 50 most recent (25 on incident.io).

**Inputs**

- Status page (`page`, text, required): The status page to read: pick a service from the list (GitHub, Cloudflare, OpenAI, Zoom and 75 more), or type the address of any status page run on Atlassian Statuspage or incident.io, such as www.githubstatus.com. A service's name, such as Discord, works too.
- Open or resolved (`state`, text): Only open incidents, only resolved ones, or both. One of: `any` (Open or resolved), `open` (Open (not resolved yet)), `resolved`. Default: `any`.
- Minimum impact (`minimum_impact`, text): Only incidents with at least this impact. One of: `none` (Any impact), `minor` (Minor or worse), `major` (Major or worse), `critical` (Critical only). Default: `none`.
- How many (`limit`, number): The most to return, from 1 to 50. Defaults to 10. From 1 to 50. Default: `10`.

**Outputs**

- `incidents` (list): The incidents, open ones first, then newest.
- `page_name` (text): The status page's name, such as GitHub.
- `page_url` (text): The status page's address.
- `platform` (text): What runs the page: 'statuspage' (Atlassian Statuspage) or 'incident_io' (incident.io, which publishes no maintenance).
- `total` (number): How many are returned.

**Example output**

```json
{
  "incidents": [
    {
      "components": [
        "Git Operations",
        "Issues"
      ],
      "created_at": "2026-10-07T17:17:05.776Z",
      "id": "qpfv5p86dmrl",
      "impact": "critical",
      "is_open": false,
      "latest_update": {
        "at": "2026-10-07T18:04:49.441Z",
        "body": "This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.",
        "status": "resolved"
      },
      "name": "Incident with Git Operations, Issues, Actions and Pull Requests",
      "resolved_at": "2026-10-07T18:04:49.441Z",
      "started_at": "2026-10-07T17:17:05.768Z",
      "status": "resolved",
      "update_count": 5,
      "updated_at": "2026-10-07T18:04:49.479Z",
      "url": "https://stspg.io/4p8x0jnnsx7m"
    },
    {
      "components": [
        "Git Operations",
        "Webhooks"
      ],
      "created_at": "2026-10-07T15:14:45.614Z",
      "id": "djlmxz2zd0j7",
      "impact": "critical",
      "is_open": false,
      "latest_update": {
        "at": "2026-10-07T16:25:14.613Z",
        "body": "This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.",
        "status": "resolved"
      },
      "name": "Incident with Git Operations, Pull Requests and Actions",
      "resolved_at": "2026-10-07T16:25:14.613Z",
      "started_at": "2026-10-07T15:14:45.606Z",
      "status": "resolved",
      "update_count": 2,
      "updated_at": "2026-10-07T16:25:14.647Z",
      "url": "https://stspg.io/96smrcth8bpg"
    }
  ],
  "page_name": "GitHub",
  "page_url": "https://www.githubstatus.com",
  "platform": "statuspage",
  "total": 2
}
```

### List scheduled maintenance

List a service's scheduled maintenance: what is under way now, what is coming up (soonest first) or what has finished. Only pages run on Atlassian Statuspage publish maintenance; for an incident.io page the step says so.

**Inputs**

- Status page (`page`, text, required): The status page to read: pick a service from the list (GitHub, Cloudflare, OpenAI, Zoom and 75 more), or type the address of any status page run on Atlassian Statuspage or incident.io, such as www.githubstatus.com. A service's name, such as Discord, works too.
- Which maintenance (`state`, text): Upcoming, in progress, completed, or any. One of: `upcoming_or_in_progress` (Upcoming or in progress), `upcoming`, `in_progress` (In progress), `completed`, `any` (Any, including completed). Default: `upcoming_or_in_progress`.
- How many (`limit`, number): The most to return, from 1 to 50. Defaults to 10. From 1 to 50. Default: `10`.

**Outputs**

- `maintenances` (list): In progress first, then upcoming soonest first, then completed newest first.
- `page_name` (text): The status page's name, such as GitHub.
- `page_url` (text): The status page's address.
- `platform` (text): What runs the page: 'statuspage' (Atlassian Statuspage) or 'incident_io' (incident.io, which publishes no maintenance).
- `total` (number): How many are returned.

**Example output**

```json
{
  "maintenances": [
    {
      "components": [
        "Reykjav\u00edk, Iceland - (KEF)"
      ],
      "id": "4ks86g48zrsw",
      "impact": "maintenance",
      "is_in_progress": true,
      "latest_update": {
        "at": "2026-10-09T02:01:08.025Z",
        "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.",
        "status": "in_progress"
      },
      "name": "KEF (Reykjav\u00edk) on 2026-10-09",
      "scheduled_for": "2026-10-09T02:00:00.000Z",
      "scheduled_until": "2026-10-09T06:00:00.000Z",
      "status": "in_progress",
      "url": "https://www.cloudflarestatus.com/incidents/4ks86g48zrsw"
    },
    {
      "components": [
        "Lisbon, Portugal - (LIS)"
      ],
      "id": "wnz6jjsfhtm2",
      "impact": "maintenance",
      "is_in_progress": true,
      "latest_update": {
        "at": "2026-10-09T00:01:07.376Z",
        "body": "Scheduled maintenance is currently in progress. We will provide updates as necessary.",
        "status": "in_progress"
      },
      "name": "LIS (Lisbon) on 2026-10-09",
      "scheduled_for": "2026-10-09T00:00:00.000Z",
      "scheduled_until": "2026-10-09T05:00:00.000Z",
      "status": "in_progress",
      "url": "https://www.cloudflarestatus.com/incidents/wnz6jjsfhtm2"
    }
  ],
  "page_name": "Cloudflare Status",
  "page_url": "https://www.cloudflarestatus.com",
  "platform": "statuspage",
  "total": 2
}
```