Status.io

App · 3 actions

Keep an eye on any public status page hosted by Status.io, such as GitLab's: check its overall and per-component status, list recent incidents and maintenance, and start a workflow when the status changes or a new incident is posted. No account needed.

Actions

ActionWhat it does
Get component statusCheck one component of a status page, such as GitLab's 'CI/CD': whether it is operational, its status in each location, and any open incident or maintenance that affects it.
Get statusGet a status page's current status: the overall status (such as Operational or Partial Service Disruption), every component and its status in each location, the incidents open right now, and maintenance in progress or scheduled.
List recent incidents and maintenanceList a status page's 10 most recent incidents and maintenance windows, newest first, resolved ones included, each with every update that was posted to it.

Get component status

Check one component of a status page, such as GitLab's 'CI/CD': whether it is operational, its status in each location, and any open incident or maintenance that affects it.

Inputs

Status pagestatus_pagetextRequired
The status page's address, as you would open it in a browser, such as status.gitlab.com. A status.io/pages/... link works too.
ComponentcomponenttextRequired
The component to check. Pick one, or type its name as the status page shows it.

Outputs

active_maintenancelist
Maintenance in progress that affects this component.
componentobject
The component.
incidentslist
Open incidents that affect this component.
is_operationaltrue/false
True when the component works normally everywhere.
pageobject
The status page.
statustext
The component's status, e.g. 'Degraded Performance'.
summarytext
One readable line, e.g. 'API: Operational.'
upcoming_maintenancelist
Scheduled maintenance that will affect this component.
Example output
{
  "active_maintenance": [],
  "component": {
    "id": "67ea346990c050053ab18e89",
    "is_operational": true,
    "locations": [
      {
        "id": "5b36e11140e76c04b7220a31",
        "is_operational": true,
        "name": "Google Compute Engine",
        "status": "Operational",
        "status_code": 100,
        "updated_at": "2026-10-16T17:24:52.435Z"
      }
    ],
    "locations_with_problems": [],
    "name": "CI/CD",
    "status": "Operational",
    "status_code": 100,
    "updated_at": "2026-10-16T17:24:52.435Z"
  },
  "incidents": [],
  "is_operational": true,
  "page": {
    "id": "5b36dc6502d06804c08349f7",
    "name": "GitLab System Status",
    "url": "https://status.gitlab.com"
  },
  "status": "Operational",
  "summary": "CI/CD: Operational.",
  "upcoming_maintenance": []
}

Get status

Get a status page's current status: the overall status (such as Operational or Partial Service Disruption), every component and its status in each location, the incidents open right now, and maintenance in progress or scheduled. Works with any public status page hosted by Status.io.

Inputs

Status pagestatus_pagetextRequired
The status page's address, as you would open it in a browser, such as status.gitlab.com. A status.io/pages/... link works too.

Outputs

active_maintenancelist
Maintenance in progress right now.
componentslist
Every component on the page, in the page's order.
components_with_problemslist
The names of the components that are not operational.
incidentslist
The incidents open right now.
is_operationaltrue/false
True when everything on the page is operational.
pageobject
The status page.
statustext
The page's overall status, e.g. 'Operational'.
status_codenumber
Status.io's code for the status: 100 Operational, 200 Planned Maintenance, 300 Degraded Performance, 400 Partial Service Disruption, 500 Service Disruption, 600 Security Event.
summarytext
One readable line, e.g. 'GitLab System Status: Operational. All 23 components are operational.'
upcoming_maintenancelist
Maintenance scheduled for later.
updated_attext
When the overall status last changed (ISO 8601, UTC).
Example output
{
  "active_maintenance": [],
  "components": [
    {
      "id": "5342d1b837768a325c00000b",
      "is_operational": true,
      "locations": [
        {
          "id": "64513de85fc76c053615177e",
          "is_operational": true,
          "name": "Docker Web Services",
          "status": "Operational",
          "status_code": 100,
          "updated_at": "2026-09-30T11:00:04.729Z"
        }
      ],
      "locations_with_problems": [],
      "name": "Docker Hub Registry",
      "status": "Operational",
      "status_code": 100,
      "updated_at": "2026-09-30T11:00:04.729Z"
    },
    {
      "id": "61e1a6108e1cce053fe15fa8",
      "is_operational": true,
      "locations": [
        {
          "id": "64513de85fc76c053615177e",
          "is_operational": true,
          "name": "Docker Web Services",
          "status": "Operational",
          "status_code": 100,
          "updated_at": "2026-04-20T17:34:31.468Z"
        }
      ],
      "locations_with_problems": [],
      "name": "Docker Authentication",
      "status": "Operational",
      "status_code": 100,
      "updated_at": "2026-04-20T17:34:31.468Z"
    }
  ],
  "components_with_problems": [],
  "incidents": [],
  "is_operational": true,
  "page": {
    "id": "533c6539221ae15e3f000031",
    "name": "Docker Systems Status Page",
    "url": "https://status.io/pages/533c6539221ae15e3f000031"
  },
  "status": "Operational",
  "status_code": 100,
  "summary": "Docker Systems Status Page: Operational. All 2 components are operational.",
  "upcoming_maintenance": [
    {
      "components_affected": [
        "Docker Hub Registry",
        "Docker Authentication"
      ],
      "id": "6a8df8fe19fb1a04da432583",
      "is_resolved": false,
      "latest_update": "On 8/25, we will migrate our status page to incident.io.",
      "locations_affected": [
        "Docker Web Services",
        "Client Machines",
        "AWS"
      ],
      "name": "Migrating to incident.io Status Pages",
      "planned_end": "2026-08-25T20:30:00.000Z",
      "planned_start": "2026-08-25T20:25:00.000Z",
      "started_at": "2026-08-25T20:20:14.738Z",
      "state": "Scheduled",
      "status": "Planned Maintenance",
      "type": "maintenance",
      "updated_at": "2026-08-25T20:20:14.773Z",
      "updates": [
        {
          "at": "2026-08-25T20:20:14.773Z",
          "message": "On 8/25, we will migrate our status page to incident.io.",
          "state": "Scheduled",
          "status": "Planned Maintenance"
        }
      ],
      "url": "https://status.io/pages/maintenance/533c6539221ae15e3f000031/6a8df8fe19fb1a04da432583"
    }
  ],
  "updated_at": "2026-10-19T22:30:05.964Z"
}

List recent incidents and maintenance

List a status page's 10 most recent incidents and maintenance windows, newest first, resolved ones included, each with every update that was posted to it.

Inputs

Status pagestatus_pagetextRequired
The status page's address, as you would open it in a browser, such as status.gitlab.com. A status.io/pages/... link works too.
Showevent_typetext
Incidents, maintenance, or both. Defaults to both.One of: all (Incidents and maintenance), incidents (Incidents only), maintenance (Maintenance only). Default: all.

Outputs

countnumber
How many were found.
eventslist
The page's most recent incidents and maintenance (up to 10), newest first. Read from the page's history, which does not say which components each one affected.
pageobject
The status page.
Example output
{
  "count": 1,
  "events": [
    {
      "components_affected": [],
      "id": "6ad24c7acb21fb05a5db963c",
      "is_resolved": true,
      "latest_update": "The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally.",
      "locations_affected": [],
      "name": "503s on GitLab.com",
      "planned_end": null,
      "planned_start": null,
      "started_at": "2026-10-16T16:10:00.000Z",
      "state": "Resolved",
      "status": null,
      "type": "incident",
      "updated_at": "2026-10-16T17:24:52.000Z",
      "updates": [
        {
          "at": "2026-10-16T16:10:00.000Z",
          "message": "We are investigating the cause of 503s on GitLab.com and the site moving slowly.",
          "state": "Investigating",
          "status": null
        },
        {
          "at": "2026-10-16T17:24:00.000Z",
          "message": "The issue is fully resolved and operations on GitLab.com and GitLab Duo are operating normally.",
          "state": "Resolved",
          "status": null
        }
      ],
      "url": "https://status.io/pages/incident/5b36dc6502d06804c08349f7/6ad24c7acb21fb05a5db963c"
    }
  ],
  "page": {
    "id": "5b36dc6502d06804c08349f7",
    "name": "GitLab System Status",
    "url": "https://status.gitlab.com"
  }
}

On this page