OpsProbe
Open Console

Latest progress

OpsProbe v0.3.22 is now released.

This update records the actual public-preview state as of September 7, 2026: what is live, what was recently deployed, and what the next feature release is building.

Updated September 7, 2026 Latest formal release v0.3.22 Next target: packaging and multi-node probes

Quick answer

OpsProbe is in the public-preview MVP stabilization phase. The core monitoring workflow and server-side analytics are live in production, while v0.3.22 tightens the analytics boundary so the admin console reflects only OpsProbe traffic.

Production status

API version0.3.22 ยท healthy after deployment
Product modelStandardized SaaS only
MonitoringHTTP, DNS, SSL, TCP port
Release statePublic preview MVP

Recent work

  • Restricted visitor analytics to known OpsProbe pages.
  • Excluded self-monitoring and common scanner noise from page-view analytics.
  • Aligned historical backfill with the same visitor boundary rules.
  • Removed noisy historical page-view records from production analytics.

These changes are recorded in the v0.3.22 release notes and are live in production.

v0.3.22 released

v0.3.8 introduced the expanded administrator analytics workspace. v0.3.10 added chronological full-history trends and server-side IP region/ISP enrichment. v0.3.12 added local-first IP2region enrichment with external fallback. v0.3.16 added a dedicated probe-submission view and more layered instant diagnostics. v0.3.17 added a public trust surface, better legal metadata, and cleaner layout alignment. v0.3.18 added a visible FAQ block, FAQPage schema, and stronger entity markup for search and AI systems. v0.3.19 made the instant probe more forgiving with protocol-tolerant input and visible loading states. v0.3.20 added richer DNS and HTTP evidence. v0.3.21 deepened the probe with DNS intelligence, redirect timelines, TLS version and cipher evidence, and a smoother probe-to-console handoff. v0.3.22 tightens the analytics boundary so visitor data stays on product traffic.

Page trafficKnown OpsProbe pages only
Noise removalSelf-monitoring and scanners excluded
Internal viewDedicated administrator entry
SessionRedis-backed eight-hour cookie
BoundaryCustomer Console has no Analytics menu

Geo/ISP enrichment, retention controls, detailed funnel reporting, and multi-region diagnostics remain follow-up work.

Not live yet

  • Billing and plan enforcement
  • Geo/ISP enrichment and retention controls for analytics
  • Multi-region probe selection
  • One-click conversion from anonymous probe result to saved monitor
  • Business-flow monitoring, deep security scanning, and AI analysis

What comes next

  1. Define standardized pricing and packaging.
  2. Plan multi-node probe voting and regional diagnostics.
  3. Harden analytics retention, geo/ISP enrichment, and role-based access.
  4. Expand business-flow and security monitoring.