Satoshi — Lightning Channel Data
https://dispatches.mystere.me/api/v1/graph/channels/03b8a5da1975f121b0b835d1187f9b0857dedfae50dcbf0ccd43e650a73effb0a8List all channels for any Lightning node from the network graph. Full edge details with capacity, policies, and peer info. 25 sats per call.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
80.1% avgResponse time
p50 466ms · p95 2193msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/1/2026, 12:00:00 AM | 0% | 1 | — |
| 8/2/2026, 12:00:00 AM | 100% | 1 | 399ms |
| 8/3/2026, 12:00:00 AM | 0% | 1 | — |
| 8/4/2026, 12:00:00 AM | 0% | 1 | — |
| 8/5/2026, 12:00:00 AM | 0% | 1 | — |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 199ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 398ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 367ms |
| 8/9/2026, 12:00:00 AM | 0% | 1 | — |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 444ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 300ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 204ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 254ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 535ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 1264ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 422ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 393ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 368ms |
| 8/19/2026, 12:00:00 AM | 100% | 21 | 501ms |
| 8/20/2026, 12:00:00 AM | 90% | 21 | 395ms |
| 8/21/2026, 12:00:00 AM | 82% | 22 | 430ms |
| 8/22/2026, 12:00:00 AM | 83% | 23 | 467ms |
| 8/23/2026, 12:00:00 AM | 86% | 21 | 436ms |
| 8/24/2026, 12:00:00 AM | 85% | 20 | 474ms |
| 8/25/2026, 12:00:00 AM | 100% | 15 | 452ms |
| 8/26/2026, 12:00:00 AM | 100% | 10 | 454ms |
| 8/27/2026, 12:00:00 AM | 92% | 13 | 642ms |
| 8/28/2026, 12:00:00 AM | 100% | 21 | 359ms |
| 8/29/2026, 12:00:00 AM | 85% | 20 | 544ms |
| 8/30/2026, 12:00:00 AM | 100% | 14 | 525ms |
- Availability
- 90
- Latency
- 94
- Security
- 93
- Transparency
- 36
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- BTC
- Networks
- lightning
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- CLOUDFLARENET
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.