Observatory

Public network signal without false certainty.

The Observatory gives operators a disciplined way to ask whether a symptom looks local, regional, or broad. It is context for triage, not a substitute for packet evidence, provider notices, or change review.

Public signals only Confidence labels No provider blame Triage context
Signal posture Guarded
01
Check scope Compare symptoms across users, sites, and regions
02
Read confidence Low coverage means the signal should stay advisory
03
Act on evidence Use ChangeGuard before changing production configs
GNHI

Broad signal, not exact diagnosis

GNHI is a directional index for public network health. It helps frame the first question: does the evidence look isolated, regional, or broadly correlated?

Confidence

Coverage changes the posture

Confidence describes signal breadth, not truth. Sparse coverage keeps conclusions modest, even when the current score moves.

Boundaries

No private telemetry claims

The Observatory does not claim carrier telemetry, internal cloud metrics, customer identity, or root-cause certainty from public signal alone.

Operator habit Use it before blame, not instead of evidence.

The best workflow is simple: check public signal, compare it to local evidence, preserve the findings, then use ChangeGuard or NetPaste when the next action involves configuration or shared CLI output.

Next step

Move from signal to action.

ChangeGuard

Review a candidate change with evidence, findings, and lab-validation boundaries.

Open ChangeGuard
NetPaste

Clean and selectively redact terminal output before sharing incident evidence.

Open NetPaste
Methodology

Read the current GNHI philosophy, confidence model, and limitations.

Read Methodology