Static peer lists become outdated very quickly

When you run a Cosmos node and connectivity starts failing, a static peer list is often not enough. What you need in that moment is simple: peers that are actually reachable from the outside right now, not peers that were visible from one node a few days ago. That is why we built… Cumulo Live Peers It is a live peer checker for Cosmos Hub mainnet and testnet , updated every 30 minutes and available through both a public dashboard and API. The idea is straightforward: keep checking which peers are really reachable, filter out the unstable ones, and give node operators a list they can actually use. cumulo_live_peers_01 2490×1203 384 KB How it works Every cycle, Cumulo Live Peers builds a candidate pool from several sources: • Our own Cosmos Hub node • RPC endpoints from validators in the ecosystem • Addrbooks and peer lists collected from validator resources • Peers contributed directly by operators Then we test each candidate with a direct TCP check against its P2P port. If a peer is not reachable from the outside, it does not make it into the published list. We also do not publish peers just because they appeared once. To be included, a…

Excerpt (1196 of 3615 characters). Read the whole post on the forum ↗

not seeing our peers in the list

Hey! Thanks for checking it!

Just to clarify: we don’t manually curate or choose which peers appear in the final list. Cumulo Live Peers is a live system.

It collects peer candidates from several sources: our own node, validator RPCs, addrbooks, peer lists and direct contributions. Then it checks whether those peers are actually reachable from outside through their P2P port.

If your peers are not showing up, they are probably not being picked up from the sources we currently index, or they have not passed the external reachability/stability checks yet.

The list only includes peers that are reachable from outside and stable across recent observation windows.

Feel free to add your RPC / addrbook / peers through a PR here, and the system will start checking them in the next cycles :

Mainnet:
https://github.com/Cumulo-pro/cumulo-cosmoshub-infra/blob/main/data/validators.json

Testnet:
https://github.com/Cumulo-pro/cumulo-cosmoshub-infra/blob/main/data/validators_testnet.json

we are literally the first entry on that gh file =)

Hey @serejandmyself! Yes, Citizen Web3 is the first entry and your RPC gets queried every cycle, appreciate that!

Having a good peer doesn’t automatically mean it’ll show up in the list though. The score for each peer depends mostly on how many independent sources see it at the same time, a peer spotted by 5 different RPCs will rank higher than one only visible from a single source, even if both are equally stable. It’s less about peer quality and more about how widely it’s seen across the network.

We’re actively adding more validator RPCs to the system to broaden the source base and make the scoring more representative. If any validator wants to contribute their RPC or addrbook, the JSON is open to PRs!

Basically my questions. Where can i see your methods precisely? We re building vladiatorinfo.com and ibc.valdiatorinfo.com - worth to connect i think

Hey! Sami already shared the full documentation at the top of the thread, should cover everything you need!

I would like to connect with you guys. We can integrate your work into what we do, so you get more exposure too