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.
Today we’re switching on a high-reliability relay: relay1.eurosky.network
The firehose of the Atmosphere, running on European infrastructure.
relay1.eurosky.network
June 10, 2026 at 7:09 AM
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.
Today we’re switching on a high-reliability relay: relay1.eurosky.network
The firehose of the Atmosphere, running on European infrastructure.
relay1 died like she lived: screwing us over
November 22, 2024 at 1:31 AM
relay1 died like she lived: screwing us over
- How many relays can you connect to?
- Well… how many are there?
- Well… how many are there?
January 28, 2026 at 2:40 AM
- How many relays can you connect to?
- Well… how many are there?
- Well… how many are there?
First 1-hour pulsar measurement 💫
March 2, 2026 at 1:30 AM
First 1-hour pulsar measurement 💫
curl --output - wss://relay1.us-east.bsky.network/xrpc/com.atproto.sync.subscribeRepos
nothing could go wrong
nothing could go wrong
October 10, 2025 at 3:53 PM
curl --output - wss://relay1.us-east.bsky.network/xrpc/com.atproto.sync.subscribeRepos
nothing could go wrong
nothing could go wrong
For developers: subscribe to the firehose at relay1.eurosky.network
Running the rainbow fanout codebase, built for high reliability. Point your AppViews, feed generators and labelers at the Eurosky relay.
Running the rainbow fanout codebase, built for high reliability. Point your AppViews, feed generators and labelers at the Eurosky relay.
relay1.eurosky.network
June 10, 2026 at 7:12 AM
For developers: subscribe to the firehose at relay1.eurosky.network
Running the rainbow fanout codebase, built for high reliability. Point your AppViews, feed generators and labelers at the Eurosky relay.
Running the rainbow fanout codebase, built for high reliability. Point your AppViews, feed generators and labelers at the Eurosky relay.
quick question do i have to consume the entirety of relay1.us-west.bsky.network to understand the plot of relay2.us-west.bsky.network
November 19, 2024 at 4:18 AM
quick question do i have to consume the entirety of relay1.us-west.bsky.network to understand the plot of relay2.us-west.bsky.network
It makes a few requests to known several AppViews, relays, PDSes and a few other things like Constellation, entryway PDS or Discover feed (all done locally on page load, once, not refreshed periodically)
+ a few things like GitHub API to double-check if the Internet even still exists
+ a few things like GitHub API to double-check if the Internet even still exists
September 22, 2026 at 5:14 PM
It makes a few requests to known several AppViews, relays, PDSes and a few other things like Constellation, entryway PDS or Discover feed (all done locally on page load, once, not refreshed periodically)
+ a few things like GitHub API to double-check if the Internet even still exists
+ a few things like GitHub API to double-check if the Internet even still exists
@bas.sh hey! would you mind configuring CORS headers on HTTP responses from the relay so XPRC endpoints like e.g. listHosts can be called there in a browser?
(this is for my new status dashboard :)
(this is for my new status dashboard :)
September 17, 2026 at 11:42 PM
@bas.sh hey! would you mind configuring CORS headers on HTTP responses from the relay so XPRC endpoints like e.g. listHosts can be called there in a browser?
(this is for my new status dashboard :)
(this is for my new status dashboard :)
IM FREE
context: bluesky's us-west relay marked my PDS as being "behind". as a result, only people using the us-east relay could see any of my new posts, while the us-west relay permanently had stale data
context: bluesky's us-west relay marked my PDS as being "behind". as a result, only people using the us-east relay could see any of my new posts, while the us-west relay permanently had stale data
March 19, 2026 at 2:45 AM
IM FREE
context: bluesky's us-west relay marked my PDS as being "behind". as a result, only people using the us-east relay could see any of my new posts, while the us-west relay permanently had stale data
context: bluesky's us-west relay marked my PDS as being "behind". as a result, only people using the us-east relay could see any of my new posts, while the us-west relay permanently had stale data
it's easy to show these are not relay-moderation actions too, they show up fine in bsky.app
sorry for the re-tags but:
@baileytownsend.dev your account is actually affected: relay1.us-west.bsky.network/xrpc/com.atp...
so is @rudyfraser.com! relay1.us-east.bsky.network/xrpc/com.atp...
sorry for the re-tags but:
@baileytownsend.dev your account is actually affected: relay1.us-west.bsky.network/xrpc/com.atp...
so is @rudyfraser.com! relay1.us-east.bsky.network/xrpc/com.atp...
August 21, 2025 at 11:46 PM
it's easy to show these are not relay-moderation actions too, they show up fine in bsky.app
sorry for the re-tags but:
@baileytownsend.dev your account is actually affected: relay1.us-west.bsky.network/xrpc/com.atp...
so is @rudyfraser.com! relay1.us-east.bsky.network/xrpc/com.atp...
sorry for the re-tags but:
@baileytownsend.dev your account is actually affected: relay1.us-west.bsky.network/xrpc/com.atp...
so is @rudyfraser.com! relay1.us-east.bsky.network/xrpc/com.atp...
@eurosky.social you have one public relay rn at relay1.eurosky.network, right? and any Jetstreams I missed?
August 20, 2026 at 2:53 PM
@eurosky.social you have one public relay rn at relay1.eurosky.network, right? and any Jetstreams I missed?
still kicking the tires before formally announcing it, but you can also use:
relay1.us-west.bsky.network/xrpc/com.atp...
(use the cursor param to paginate)
relay1.us-west.bsky.network/xrpc/com.atp...
(use the cursor param to paginate)
April 20, 2025 at 6:20 AM
still kicking the tires before formally announcing it, but you can also use:
relay1.us-west.bsky.network/xrpc/com.atp...
(use the cursor param to paginate)
relay1.us-west.bsky.network/xrpc/com.atp...
(use the cursor param to paginate)
Relays still feel like they might not be still have a full historic back fill 👀. relay1.us-east.bsky.network doesn't believe I have a net.anisota.settings record
https://relay1.us-east.bsky.network
_ _
_ _ __ _(_)_ _ | |__ _____ __ __
| '_/ _' | | ' \| '_ \/ _ \ V V /
|_| \__,_|_|_||_|_.__/\___/\_/\_/
This is an atproto [https://atproto.com] firehose fanout service, running t...
relay1.us-east.bsky.network
December 13, 2025 at 2:35 AM
Relays still feel like they might not be still have a full historic back fill 👀. relay1.us-east.bsky.network doesn't believe I have a net.anisota.settings record
August 18, 2025 at 5:19 AM
relay1.us-west.bsky.network/xrpc/com.atp... lives on in memory 🫡
November 22, 2025 at 3:27 AM
relay1.us-west.bsky.network/xrpc/com.atp... lives on in memory 🫡
fixed up CORS for lightrail.microcosm.blue in case you wanna show accounts by collection anywhere in a browser
like this top-secret to-be-announced mystery tool 👀
like this top-secret to-be-announced mystery tool 👀
March 24, 2026 at 7:07 PM
fixed up CORS for lightrail.microcosm.blue in case you wanna show accounts by collection anywhere in a browser
like this top-secret to-be-announced mystery tool 👀
like this top-secret to-be-announced mystery tool 👀
(bluesky also has sync1.1 relays deployed at relay1.us-east.bsky.network and relay1.us-west.bsky.network)
sync1.1 is the future, but BGS has had more production stress testing/debugging, and i've been finding some (fixable!) sync1.1 relay issues, particularly affecting pds self-hosters
sync1.1 is the future, but BGS has had more production stress testing/debugging, and i've been finding some (fixable!) sync1.1 relay issues, particularly affecting pds self-hosters
September 1, 2025 at 6:56 PM
(bluesky also has sync1.1 relays deployed at relay1.us-east.bsky.network and relay1.us-west.bsky.network)
sync1.1 is the future, but BGS has had more production stress testing/debugging, and i've been finding some (fixable!) sync1.1 relay issues, particularly affecting pds self-hosters
sync1.1 is the future, but BGS has had more production stress testing/debugging, and i've been finding some (fixable!) sync1.1 relay issues, particularly affecting pds self-hosters
jetstream.fire.hose.cam was listening to relay1, so it was affected by the issues with that instance. since that's now relay2, it should be more reliable going forward!
i'll get the EU (France probably) jetstream instance up by the end of this week.
i'll get the EU (France probably) jetstream instance up by the end of this week.
May 6, 2025 at 3:13 PM
jetstream.fire.hose.cam was listening to relay1, so it was affected by the issues with that instance. since that's now relay2, it should be more reliable going forward!
i'll get the EU (France probably) jetstream instance up by the end of this week.
i'll get the EU (France probably) jetstream instance up by the end of this week.
yet another #atproto helpdesk ticket, pls help:
we're seeing issues with the following pds: bsky-pds.blooym.dev
it shows on relay1.us-east.bsky.network listHosts XRPC, but records that come through the pds's subscribeRepos arent flowing through relay (tested in jetstream and appview)
we're seeing issues with the following pds: bsky-pds.blooym.dev
it shows on relay1.us-east.bsky.network listHosts XRPC, but records that come through the pds's subscribeRepos arent flowing through relay (tested in jetstream and appview)
August 14, 2025 at 5:27 PM
yet another #atproto helpdesk ticket, pls help:
we're seeing issues with the following pds: bsky-pds.blooym.dev
it shows on relay1.us-east.bsky.network listHosts XRPC, but records that come through the pds's subscribeRepos arent flowing through relay (tested in jetstream and appview)
we're seeing issues with the following pds: bsky-pds.blooym.dev
it shows on relay1.us-east.bsky.network listHosts XRPC, but records that come through the pds's subscribeRepos arent flowing through relay (tested in jetstream and appview)
At very quick glance:
- @besaid.zone's covers only ~1/3
- @upcloud.com's covers ~2/3
- atproto.africa is missing ~5%
- @bad-example.com's and @sri.xyz's have pretty much the exact same coverage as Bluesky's 🏆👏
- mine is, well, special 🙃
#atdev
- @besaid.zone's covers only ~1/3
- @upcloud.com's covers ~2/3
- atproto.africa is missing ~5%
- @bad-example.com's and @sri.xyz's have pretty much the exact same coverage as Bluesky's 🏆👏
- mine is, well, special 🙃
#atdev
January 28, 2026 at 2:50 AM
At very quick glance:
- @besaid.zone's covers only ~1/3
- @upcloud.com's covers ~2/3
- atproto.africa is missing ~5%
- @bad-example.com's and @sri.xyz's have pretty much the exact same coverage as Bluesky's 🏆👏
- mine is, well, special 🙃
#atdev
- @besaid.zone's covers only ~1/3
- @upcloud.com's covers ~2/3
- atproto.africa is missing ~5%
- @bad-example.com's and @sri.xyz's have pretty much the exact same coverage as Bluesky's 🏆👏
- mine is, well, special 🙃
#atdev