#routing

Live data for Bitcoin's Lightning Network — the instant-payment layer on top of Bitcoin — served straight from mempool.space's public API, no key, nothing cached. The stats endpoint returns the state of the whole network: how many nodes and payment channels exist, the total capacity locked in Bitcoin, the average and median channel capacity, the average fee rate, and the split between clearnet and Tor nodes — the network runs tens of thousands of channels holding thousands of BTC. The top endpoint is the node league table, ranked by liquidity (capacity) or by connectivity (channel count), with each node's alias, capacity and channel count — Bitfinex and Binance run some of the largest routing nodes. The search endpoint finds nodes by alias and returns their public key, capacity and channel count. This is the routing-and-liquidity layer for any Lightning wallet, node operator, payment or analytics app — who the big routing nodes are and how much capacity the network holds. Live from mempool.space, nothing stored. Distinct from on-chain Bitcoin and fee APIs — this is the Lightning Network layer. 4 endpoints.

api.oanor.com/lightning-api

Encode and decode Google/Mapbox encoded polylines — the compact ASCII string used by the Google Maps Directions API, Mapbox, Valhalla, OSRM and GPX-style route geometry to pack a list of coordinates into a few bytes. Decode an encoded string into an array of latitude/longitude points, encode a coordinate list back into a polyline (precision 5, the Google default, or 6 for OSRM/Valhalla overview), and measure a path — point count, total length by the haversine great-circle formula in km and miles, and the bounding box. Perfect for drawing routes on a map, storing tracks compactly, computing trip distance and fitting a map viewport. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from coordinate-format conversion (Plus Code/MGRS/UTM) and geohash.

api.oanor.com/polyline-api

Internet routing and number-resource intelligence as an API, powered by RIPEstat — the open data service of the RIPE NCC, one of the world's five Regional Internet Registries. Answer the questions network engineers, security teams and researchers ask about the public internet: which Autonomous System and prefix does an IP address belong to; what is an AS (its operator/holder name, whether it is currently announced in BGP, its type and registration block); which IPv4 and IPv6 prefixes does an AS announce; who are an AS's BGP neighbours and peers (and how many); who is the abuse-reporting contact for an IP, prefix or ASN, and which RIR is authoritative; and is a prefix correctly originated according to RPKI route-origin validation (valid, invalid or unknown) with the matching ROAs. The data is real-time, drawn from the RIPE NCC's global network of BGP route collectors and the registries. Inputs accept IPv4 and IPv6 addresses, CIDR prefixes and AS numbers (with or without the AS prefix). Ideal for network operations, threat intelligence and abuse handling, BGP and RPKI monitoring, IP reputation and OSINT tooling, and internet research. Data from the RIPE NCC RIPEstat service.

api.oanor.com/ripestat-api

Driving routes with distance, duration and geometry, distance/duration matrices for up to 25 points, and nearest-road snapping — on the global OpenStreetMap road network. Coordinates are simple lat,lon pairs.

api.oanor.com/routing-api