







I still wanna understand how applications can consume from multiple relays in parallel.. this was something @bad-example.com mentioned a while back and I'm still not sure I fully get it
Aug 6, 2026 at 1:14 AM
Relay Directory | Taproot
Browse AT Protocol relay servers. View relay details, subscriber counts, and event volumes across the network.
jonny (nonvenomous) (@jonny@neuromatch.social)
Content warning: long, bsky, atproto, on the impossibility of multiple relays
Notes on Running a Full-Network atproto Relay (July 2024) | bryan newbold
Note: See updated post from May 2025 describing a newer, cheaper, easier to run relay implementation! These are some informal notes on setting up a full-network atproto Relay, using the bigsky relay software developed by Bluesky. This is the same software we run ourselves at https://bsky.network. T...
A Full-Network Relay for $34 a Month | bryan newbold
This is an update to a Summer 2024 blog post. At the time, atproto relays required a cache of the full network on local disk to validate data structures. With the Sync v1.1 updates, relays don't need all that disk I/O. What impact does that have on hosting setup and operating costs? Turns out the d...
Asia Relay | Firehose Network
Asia ATProto Relay. Part of the global Firehose Network.

Europe Relay | Firehose Network
Europe ATProto Relay. Part of the global Firehose Network.

North America Relay | Firehose Network
North America ATProto Relay. Part of the global Firehose Network.

Firehose Network | Global ATProto Relays
Global ATProto Relay Network. Public relays in North America, Europe, and Asia.

atproto.africa
An atproto relay instance running the rsky-relay codebase. Operated by Blacksky Algorithms.

Relay good news - Sri's leaflets
Introducing firehose.network - public infrastructure and tools for ATProto relays.
Relay good news - Sri's leaflets
Introducing firehose.network - public infrastructure and tools for ATProto relays.
@metaflame.dev gave a great explanation in this mini-thread of the advantages for the #atproto network in having multiple, independent relays operating
Metaflame
Redundancy, resilience, and possibly distance Importantly, once enough independent relays are active, they are likely to disincentivize malicious behavior for any one of them. Having multiple implementations (that is, different code) adds further resilience.
oh i forgot to mention in my talk, but some of us small indie relay operators are getting together to make @firehose.club so we can share network limit bumps and bans and build some shared tooling. we can go further together <3
two relays, three jetstreams, two plc mirrors, created lightrail (running one instance, several others deploying it), spacedust, constellation and slingshot in HA configs serving hundreds of apps, ufos, firehose compare, pds debugger, a bunch of demos, hubble-mini already mirroring every indie pds,
fig (aka:[phil])
obviously i’m personally a vc-funded billionaire and megacorp to do this. I’m super-funded on github sponsors and setting those Big Bucks on fire! $30 CAD/mo for this!!! in this economy!!!!
relay-eval
relay-eval.waow.tech