OpsProbe
Open Console

Release notes

OpsProbe v0.2.14: configurable TCP ports.

Released on August 8, 2026, v0.2.14 adds configurable TCP port monitoring for verified websites.

Release date August 8, 2026 Version v0.2.14 Type patch

Quick answer

OpsProbe now lets users set the TCP port that should be checked for a verified website, while preserving the default HTTPS or HTTP port when no custom value is supplied.

What changed

  • Added `port_number` to monitor records and API responses.
  • Updated the worker so TCP probes use explicit ports when configured.
  • Added a console form for creating or updating a site's TCP port monitor.
  • Backfilled existing TCP monitors from the site URL scheme default.

API and schema

`POST /v1/mvp/sites/:site_id/monitors` now accepts `port_number` for `port` monitors. The `monitors` table now includes `port_number`, with a range check for valid TCP ports.

Verification

  • `cargo fmt --check` passed.
  • `cargo check` passed.
  • `cargo test` passed.
  • `node --check web/app.js` passed.

Known limits

This release supports one explicit TCP port per site. Multi-port presets and region selection remain planned.