A network transparency and
stability measurement tool.
Libreprobe surfaces what your connection reveals — and actively measures how stable and responsive your route to different providers is. Two systems: one that reads what infrastructure knows, one that measures what the browser experiences.
Info is infrastructure-assisted introspection. A Cloudflare Worker reads the metadata Cloudflare attaches to every request — your IP, geolocation, ASN, TLS details, and edge node — and surfaces it. This layer is convenient and replaceable: any platform that adds rich request headers would work the same way.
Stability is active client-side measurement. A browser-based sampler sends repeated HTTP requests to a provider endpoint you choose, measures round-trip times locally, and scores the results against per-provider baseline profiles. This system is endpoint-agnostic and portable — it can probe a Worker, a CDN, a self-hosted API, or any other compatible endpoint.
Info uses a Cloudflare Worker to read request metadata and return it as JSON. Cloudflare enriches the request with geolocation, ASN, TLS handshake details, and the edge node identifier before the Worker runs. The Worker formats this and exits — no state is carried forward.
Stability is a JavaScript measurement framework running entirely in the browser. It sends repeated HTTP requests to any compatible endpoint, measures TTFB locally, and scores results against provider-specific baselines. No measurement data is sent to Libreprobe. The architecture is designed to be portable — providers are configurable, and the scoring logic is provider-aware rather than hardcoded.
Network diagnostics tools are not new. Many provide useful insights into IP addresses, routing, and connection metadata. Libreprobe exists to offer a minimal, transparent implementation focused on two things: surfacing what your connection reveals about you, and measuring how stable and responsive your route to different providers actually is — without accounts, analytics scripts, ads, or monetisation mechanisms.
The Info page is useful because metadata enrichment is opaque by default — most users never see what infrastructure operators know about their connection. Making that visible is a straightforward transparency win.
The Stability page is more technically interesting. Active path measurement is endpoint-agnostic, portable, and provider-comparative. It is not tied to any single platform. The scoring logic uses per-provider baselines, so a 150 ms RTT can be "good" for one provider and "elevated" for another — reflecting the reality that different routes have different characteristics. This architecture can extend to self-hosted endpoints, multi-region probes, or any compatible HTTP target.
The goal is clarity. A small, readable codebase. No hidden flows. No layered product tiers. Just a straightforward diagnostic surface you can inspect and verify for yourself.
The name is intentional. Libre — free as in freedom. probe — a diagnostic instrument.