A Nostr relay list is a curated or automatically discovered list of WebSocket relay server endpoints that a Nostr client uses to publish and subscribe to signed events. Because Nostr has no centralised routing, a client’s relay list determines its social graph reach: events are broadcast to all listed relays, and the client pulls its feed from the same set. Relay lists are stored as NIP-65 kind:10002 events on the network itself, enabling portable relay preferences that travel with the user’s public key across clients.
Semantic Classification
Content
-
- wss://nostr.oxtr.dev/ - 40ms
- wss://relay.chorus.community/ - 58ms
- wss://relay.nostr.net/ - 66ms
- wss://relay.exit.pub/ - 69ms
- wss://nostr.mom/ - 98ms
- wss://nostr.vulpem.com/ - 103ms
- wss://relay.degmods.com/ - 103ms
- wss://relay.agora.social/ - 119ms
- wss://a.nos.lol/ - 125ms
- wss://relay.primal.net/ - 130ms
- wss://nostr.data.haus/ - 137ms
- wss://relays.land/spatianostra - 145ms
- wss://nostr.sathoarder.com/ - 156ms
- wss://relay.nostromo.social/ - 163ms
- wss://sendit.nosflare.com/ - 166ms
- wss://nostr.yael.at/ - 182ms
- wss://orangesync.tech/ - 184ms
- wss://nostr.einundzwanzig.space/ - 192ms
- wss://soloco.nl/ - 194ms
- wss://nostr.chaima.info/ - 195ms
- wss://relay1.nostrchat.io/ - 199ms
- wss://relay.noswhere.com/ - 226ms
- wss://relay.nostr.band/wss://cobrafuma.com/relay - 239ms
- wss://relay.seq1.net/outbox - 248ms
- wss://nos.lol/ - 249ms
- wss://nostr.azzamo.net/ - 269ms
- wss://feeds.nostr.band/popular - 286ms
- wss://purpura.cloud/ - 337ms
- wss://ithurtswhenip.ee/ - 340ms
- wss://relay.davidebtc.me/ - 348ms
- wss://feeds.nostr.band/lang/zh - 371ms
- wss://nostrue.com/ - 436ms
- wss://nostr.roundrockbitcoiners.com/ - 440ms
- wss://multiplexer.huszonegy.world/ - 442ms
- wss://relay.agorist.space/ - 463ms
- wss://relay.damus.io/ - 475ms
- wss://relay.nostr.band/ - 481ms
- wss://relay.nostriot.com/ - 497ms
- wss://relay.nos.social/ - 507ms
- wss://feeds.nostr.band/nostrhispano - 510ms