# Heroku Status

> Know when Heroku itself has a problem: check whether apps, databases or the dashboard are down, read incidents and Heroku's updates, see planned maintenance, and start a workflow when Heroku posts a new incident.

App · 4 actions. Web page: https://docs.lodol.com/docs/integrations/heroku-status

## Actions

### Get Heroku's status

Check whether Heroku's Apps, Data and Tools are up right now, and what's open.

**Inputs**: None.

**Outputs**

- `apps` (text): Apps (running apps, routing, builds): ok, degraded or down
- `checked_at` (text): When the status was read (ISO 8601, UTC)
- `data` (text): Data (Postgres, Redis, Kafka): ok, degraded or down
- `incidents` (list): The incidents
- `open_incidents` (number): How many incidents are open
- `status` (text): The worst of the three: ok, degraded or down
- `tools` (text): Tools (dashboard, CLI, API): ok, degraded or down

**Example output**

```json
{
  "apps": "ok",
  "checked_at": "2026-10-28T11:02:00Z",
  "data": "ok",
  "incidents": [
    {
      "began_at": "2026-10-28T10:55:09.120Z",
      "id": "2966",
      "impact": "degraded",
      "latest_update": "The upstream errors have been resolved.",
      "link": "https://status.heroku.com/incidents/2966",
      "maintenance": false,
      "open": true,
      "regions": [
        "NA",
        "EMEA"
      ],
      "state": "investigating",
      "systems": [
        "Tools"
      ],
      "title": "Heroku Feature Degradation",
      "updated_at": "2026-10-28T15:59:15.496Z"
    }
  ],
  "open_incidents": 1,
  "status": "degraded",
  "tools": "degraded"
}
```

### Get incident

Get one incident with every update Heroku posted, newest first.

**Inputs**

- Incident (`incident`, text, required): The incident's number, from a list or the trigger, or its link on status.heroku.com.

**Outputs**

- `began_at` (text): When it began (ISO 8601, UTC)
- `id` (text): The incident's number
- `impact` (text): The worst it put a system in: ok, degraded or down
- `latest_update` (text): Heroku's latest update on it
- `link` (text): A link to it on status.heroku.com
- `maintenance` (true/false): True for planned maintenance
- `open` (true/false): True until it's resolved or completed
- `regions` (list): The regions Heroku tagged it with, such as NA or EMEA
- `state` (text): investigating, identified, monitoring or resolved; maintenance is scheduled, in_progress or completed
- `systems` (list): The parts of Heroku affected: Apps, Data or Tools
- `title` (text): Heroku's title for it
- `updated_at` (text): When Heroku last changed it
- `updates` (list): Every update, newest first

**Example output**

```json
{
  "began_at": "2026-10-28T10:55:09.120Z",
  "id": "2966",
  "impact": "degraded",
  "latest_update": "The upstream errors have been resolved.",
  "link": "https://status.heroku.com/incidents/2966",
  "maintenance": false,
  "open": false,
  "regions": [
    "NA",
    "EMEA"
  ],
  "state": "resolved",
  "systems": [
    "Tools"
  ],
  "title": "Heroku Feature Degradation",
  "updated_at": "2026-10-28T15:59:15.496Z",
  "updates": [
    {
      "at": "2026-10-28T15:59:15.496Z",
      "text": "The upstream errors have been resolved.",
      "type": "resolved"
    }
  ]
}
```

### List planned maintenance

List the maintenance Heroku has planned or has under way, soonest first.

**Inputs**: None.

**Outputs**

- `count` (number): How many
- `maintenance` (list): The maintenance windows; latest_update says when each runs

**Example output**

```json
{
  "count": 1,
  "maintenance": [
    {
      "began_at": "2026-11-12T17:00:00.000Z",
      "id": "2970",
      "impact": "ok",
      "latest_update": "On November 12, 2026, starting at 17:00 UTC and continuing until 22:00 UTC, Heroku will be performing scheduled maintenance.",
      "link": "https://status.heroku.com/incidents/2970",
      "maintenance": true,
      "open": true,
      "regions": [
        "NA",
        "EMEA"
      ],
      "state": "upcoming",
      "systems": [
        "Apps"
      ],
      "title": "Heroku Platform Maintenance",
      "updated_at": "2026-10-28T15:59:15.496Z"
    }
  ]
}
```

### List recent incidents

List Heroku's open and ten latest incidents, newest first.

**Inputs**

- System (`system`, text): Only ones affecting this part of Heroku. Leave blank for all. One of: `Apps`, `Data`, `Tools`.
- Since (`since`, date): Only ones that began on or after this day.

**Outputs**

- `count` (number): How many
- `incidents` (list): The incidents

**Example output**

```json
{
  "count": 1,
  "incidents": [
    {
      "began_at": "2026-10-28T10:55:09.120Z",
      "id": "2966",
      "impact": "degraded",
      "latest_update": "The upstream errors have been resolved.",
      "link": "https://status.heroku.com/incidents/2966",
      "maintenance": false,
      "open": false,
      "regions": [
        "NA",
        "EMEA"
      ],
      "state": "resolved",
      "systems": [
        "Tools"
      ],
      "title": "Heroku Feature Degradation",
      "updated_at": "2026-10-28T15:59:15.496Z"
    }
  ]
}
```
