PortJogger

A running companion for jogging through port cities around the world — and before that, a CLI tool for probing network ports. Two very different projects that share a name and not much else.

PortJogger v2 (2026)

Built with Claude. The idea came from a joke about the name — if you’re going to call something PortJogger, it should probably involve actual jogging. So it does now.

Reimagined as a running app focused on port cities: coastal towns, harbor districts, container ports converted to promenades. The kind of places that have good waterfront paths and interesting industrial decay. Routes, landmarks, elevation, and local context for runners who’d rather explore than GPS-follow a generic track.

On hold while the v1 identity gets untangled from the domain.

PortJogger v1 (2019)

The original tool. A lightweight CLI utility for testing network port availability — useful for diagnosing connectivity issues in containerized environments, checking whether a service is actually listening before you start debugging the application layer.

Wrote it during a period of heavy Docker work where telnet felt too manual and the available options were either too heavy or too fragile. It did one thing: tell you if a port was reachable, quickly, from the command line.