postship incidents
What is down on a project, and since when.
Updated on 17 September 2026
On this page
The project's URLs whose last verdict is bad — incidents in the app's sense, the raw fact, not what the status page tells. One line per URL: address, check type, verdict, since when.
This command does not consume the quota: it is a read.
What PostShip does
Usage
postship incidents --project <id> [--fail-if-open] [--json]Options
| Option | What it does |
|---|---|
--project, -p <id> | The project. Or ./.postship.json, or POSTSHIP_PROJECT. |
--fail-if-open | Exit 1 when at least one incident is open. |
--json | The raw list. |
Examples
postship incidents -p 3f1c…“Nothing open.” or the table.
postship incidents --fail-if-openIn a repo with ./.postship.json: block when something is down.
Exit codes
0 · 1 with --fail-if-open when an incident is open · 2 project not found, token, network.
Troubleshooting
“Project not found.”
The token has no access to this project, or the id is wrong — the answer is the same in both cases, on purpose.
See also
The postship command — every command, installation and sign-in · CI recipes — complete workflows to copy.
In the terminal, postship help incidents says the same; postship docs incidents opens this page.