Skip to main content
Observability is a core principle for Linkr: the network should not assume connectivity exists — it should observe and verify.
This is a principle guiding where Linkr is headed. Live monitoring does not exist in the current build — today’s data is static. This page describes the goal, not a shipped feature. See Product status.

What observability means

Observability is understanding the state of a system by looking at its outputs. Applied to connectivity, the goal is:
  • Hotspots are not assumed to be online — they are checked
  • Reliability is not claimed — it is measured
  • Availability is not promised — it is tracked
This is the direction. Today, hotspot details are the values contributors provide, and the public preview uses a static dataset.

Why this matters for connectivity

Traditional connectivity information is full of assumptions. Coverage maps show where signals should reach. Venue listings claim Wi-Fi without verifying it works. Directories list networks that may no longer exist. These assumptions are often wrong, and users cannot tell until they try. Observability is meant to replace those assumptions with real data.

The intended approach

As monitoring is built, the aim is:
  • Status becomes live — each hotspot’s current availability determined by active checks
  • Reliability becomes measured — scores calculated from observed uptime over time
  • The map reflects reality — what you see is what has been verified

The limits of observability

Even when built, observability will not be omniscience. It can show whether a hotspot responds and how often it has been available. It cannot tell you the quality of your experience at a specific moment, or guarantee future availability.
Observability is not about being skeptical of contributors. It is about giving everyone accurate information. Better data leads to better decisions — which is why it is a priority on the roadmap.