Command-line client
Check your cloud vendors from the terminal, then keep the stack
The OutageDeck CLI reads normalized official status data for more than 170 cloud and SaaS providers. Use it interactively, return structured JSON to a script, or turn the same provider list into a prefilled outage-alert setup.
Install
Use the package manager you already have
The same open-source binary is available for macOS, Linux, and Windows on AMD64 and ARM64, plus a minimal Linux container for short-lived jobs.
Homebrew on macOS or Linux
brew install outagedeck/tap/outagedeckMacPorts on macOS
sudo port selfupdate
sudo port install outagedeckScoop on Windows
scoop bucket add outagedeck https://github.com/outagedeck/scoop-bucket
scoop install outagedeckmise
mise use -g github:outagedeck/cli@0.1.3Nix
nix run github:outagedeck/cli -- --versionGo install
go install github.com/outagedeck/cli/cmd/outagedeck@latestContainer on Linux
docker run --rm ghcr.io/outagedeck/cli:0.1.3 status --fail-on=never github cloudflareThe official MacPorts catalog, Homebrew tap, Scoop bucket, release archives, container image, and checksums all point to the same public source. The container runs as a non-root user with no shell or package manager and includes provenance plus an SBOM.
Use
One command for the question you are already asking
Provider checks work without an account or API key. Data is refreshed from each vendor's official source about every 10 minutes.
Check a dependency stack
outagedeck status aws cloudflare github openaiFind the provider slug
outagedeck search "Claude"Keep watching the checked stack
outagedeck alerts aws cloudflare github openaiStructured CI check
outagedeck status --json --fail-on=outage aws github openaiThe alerts command validates and deduplicates provider names locally, then prints an OutageDeck account link with that exact stack selected. It makes no extra status request. Free email alerts cover up to five providers.
Predictable in CI
Choose whether a degraded provider, an outage, or only a major outage should fail the job. Use --fail-on=never when the result belongs in a report but should not block a deployment.
| 0 | Every provider is below the selected failure threshold. |
| 1 | A request, provider slug, or command argument failed. |
| 2 | At least one provider met the selected failure threshold. |
Small and inspectable
- Requests send provider slugs, not project or customer data.
- The CLI adds no telemetry of its own.
- Unreachable or malformed provider responses are errors, never reported as operational.
- Anonymous access includes 120 API requests per hour. An account key raises that quota when the CLI becomes part of scheduled checks.
GitHub CLI
Prefer gh? Install the companion extension
The GitHub CLI extension defaults to GitHub provider and service health, while keeping the same stack-specific alert handoff.
Install for GitHub CLI
gh extension install outagedeck/gh-outagedeck
gh outagedeckFrom a check to a response
Build the stack once, then let the next outage find you
Start with a shareable live board or create free email alerts for an example AWS, GitHub, and Cloudflare stack. Paid plans add Slack, Microsoft Teams, Discord, webhook delivery, and higher API quotas.