







Europe 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.

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

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

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.
Firehose Directory | ATProto Relay Index
Complete directory of ATProto Relays and Jetstreams in the Atmosphere.
atproto relay conformance — invalid firehose data
skydeval/horizon-firehose
A Rust-based ATProto firehose consumer with CBOR/CAR decoding, per-relay failover, and Redis stream publishing
Pulsar - ATProto relay observatory
Dashboard of currently active AT Protocol relays and Jetstream servers
atproto.africa
An atproto relay instance running the rsky-relay codebase. Operated by Blacksky Algorithms.

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...
Spacedust | ATProto Notifications Firehose
A configurable ATProto notifications firehose. Consumes Jetstream, extracts links, exposes via WebSocket API.
jonny (nonvenomous) (@jonny@neuromatch.social)
Content warning: long, bsky, atproto, on the impossibility of multiple relays
firehose.stream — ATProto jetstreams
A lightweight, filterable JSON firehose of real-time ATProto events.

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.