isitup-cli 0.1.4

Is it up? Ping, HTTP, and TCP checks in one small, fast CLI.

isitup is a small CLI that periodically checks whether servers respond to ping and, depending on how the target is written, HTTP or a TCP port:

Ping is checked independently from the HTTP/TCP probe: many hosts (behind load balancers, CDNs, or firewalls) drop ICMP but serve their actual service just fine, so a blocked ping alone doesn't mark a target down: the "Status" column is based on the probe (HTTP or TCP), with ping shown alongside as extra diagnostic info. A target only shows as OFFLINE when both ping and the probe fail; a ping-only target's status is based on ping alone, since there's nothing else to check.

If the same host appears more than once (e.g. example.com and https://example.com/health), it's only pinged once per round. The ping result is shared across all targets pointing at that host.

While checks are running you get a live spinner and a progress bar per target counting down its timeout; results are then shown in a table that updates in place (via rich) rather than reprinting on every round.

Each target also keeps a rolling window of its last 20 response times for the session (HTTP response time or TCP connect time, whichever applies), shown as Min/Max latency columns and a tiny sparkline ("Trend"), along with the last time it was seen online and the last time it was seen offline. This history is in-memory only and resets each time you start the tool.

Installation

The package is published on PyPI as isitup-cli, but it installs a plain isitup command:

uv tool install isitup-cli
# or: pipx install isitup-cli
# or: pip install isitup-cli

To try unreleased changes straight from main instead (no PyPI release needed):

uv tool install git+https://github.com/ramsesoriginal/isitup

Either way, remove it later with uv tool uninstall isitup.

Usage

isitup example.com https://example.org db.internal:5432

--url/-u work the same way and can be freely mixed with positional targets: isitup example.com -u https://example.org is the same as isitup example.com https://example.org:

isitup --url example.com --url https://example.org --url db.internal:5432

Or with a config file:

cp config.example.yaml config.yaml
# edit config.yaml
isitup --config config.yaml

Config files and CLI-supplied targets (positional or --url) can be combined; the tool watches the union of both. The config file is watched for changes and reloaded automatically: add, remove, or edit targets without restarting the tool (CLI-supplied targets can't change at runtime, only what's in the file).

Options

--plain and --json are mutually exclusive with each other, and both skip the interactive spinner/progress UI entirely.

Note on ping

Some servers/networks (common on cloud providers, behind load balancers or CDNs) block ICMP echo requests entirely even though the service itself is perfectly reachable. The "Status" column already accounts for this and won't flag such a target as down (unless it's ping-only, in which case ping is the only signal there is). If you'd rather not run ping checks against a target at all (e.g. to skip the ~2s ping timeout), either set ping: false for it in the config file, or pass --no-ping to disable ICMP checks globally. Note that a ping-only target (bare hostname, no port) can't have ping: false, there would be nothing left to check.

Failure classification

When the HTTP or TCP probe fails, the specific reason is captured as error_kind (visible in --json output, and shown as a short tag like DOWN (DNS) in the Service column otherwise):

Development

uv sync
uv run isitup --once --url https://example.com

uv run pytest       # tests
uv run ruff check .    # lint
uv run ruff format .   # format
uv run mypy src tests  # type check

Every push and pull request runs this same lint/type-check/test suite via GitHub Actions, across Linux and Windows.

Changelog

See CHANGELOG.md.

License

GPL-3.0: see LICENSE for the full text.