northamerica.firehose.network — a low-latency ATProto relay serving the Atmosphere.
Firehose Network | Global ATProto Relays
Global ATProto Relay Network. Public relays in North America, Europe, and Asia.
Europe Relay | Firehose Network
Europe ATProto Relay. Part of the global Firehose Network.
Asia Relay | Firehose Network
Asia ATProto Relay. Part of the global Firehose Network.
Firehose Directory | ATProto Relay Index
Complete directory of ATProto Relays and Jetstreams in the Atmosphere.
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.
atproto relay conformance — invalid firehose data
atproto.africa
An atproto relay instance running the rsky-relay codebase. Operated by Blacksky Algorithms.
skydeval/horizon-firehose
A Rust-based ATProto firehose consumer with CBOR/CAR decoding, per-relay failover, and Redis stream publishing
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...
&displayname=bryan%20newbold&handle=@bnewbold.net&avatar=https://cdn.bsky.app/img/avatar/plain/did:plc:44ybard66vv44zksje25o7dz/bafkreiglnysron3h2je7nf6cmvtimuaxi7xe2c7rkxitmks3mzmajnc2ou@jpeg)
Spacedust | ATProto Notifications Firehose
A configurable ATProto notifications firehose. Consumes Jetstream, extracts links, exposes via WebSocket API.
10.06.2026 – release 2 of 3 Today we’re switching on a high-reliability relay: relay1.eurosky.network The firehose of the Atmosphere, running on European infrastructure.
@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 this is interesting. At first I thought it was yet another lexicon to wrap data on, but it's a way for anyone to use ATProto as a discovery mechanism for their non-PDS-hosted datasets. I hadn't thought of the ATmosphere and the relays as a way to surface arbitrary existing data until know.
IPFS
🪩 Introducing matadisco.org! — a way to discover open datasets via #atproto that doesn't depend on any single institution staying online. 🕺🏼 We have more public data than ever (satellite imagery, climate models, genomic sequences), but finding it is still painfully hard.
