Lightning operations, explained

See what changed.
Know what to inspect.

Monitor Lightning node ranking signals, track your own payment outcomes, and investigate changes from one workspace.

The pilot is free. No payment setup required.

Explore the product

Public network signals.
Your private operations.

Ranking changes

Inspect candidate stability, leadership changes, and historical consistency.

Observed payment outcomes

Use your own submitted successes, failures, latency, fees, and retries.

Open the live public dashboard →

Ranking signals are historical proxies, not payment success probabilities.

One useful workflow

From a changing signal to an investigation.

01 · Observe

Save your monitoring targets

Add node public keys and ranking thresholds. See explicitly when a node is outside the observed dataset.

02 · Understand

Read the change in context

Review time windows, ranking history, cautions, and supportive signals without confusing them with measured payment outcomes.

03 · Investigate

Bring your own payment evidence

Submit minimal outcome telemetry and inspect failure categories, retries, fees, and latency in your private weekly report.

Built for operators

Choose the job you need done.

Node operators

Keep a watchlist and incident history for ranking changes in the candidates we observe.

Wallet and payment teams

Summarize actual payment outcomes and identify the failure categories worth investigating.

Pilot access

Build a monitoring workflow around your team.

Start with a workspace, then request a monitoring, operations, API, or audit pilot. Tell us what you need and explore the free pilot.

See how the signals are calculated →