Bluesky April 2026 Outage Post-Mortem
21–30 of 85 posts
Re: Bluesky April 2026 Outage Post-Mortem
#22Re: Bluesky April 2026 Outage Post-Mortem
#23nostr never goes down
Re: Bluesky April 2026 Outage Post-Mortem
#24Re: Bluesky April 2026 Outage Post-Mortem
#25I don't really understand this architecture, but I thought Bluesky was distributed like Mastodon? How can it have an outage?
This writeup is useful for backend engineers: https://atproto.com/articles/atproto-for-distsys-engineers The simple answer is that atproto works like the web & search engines, where the apps aggregate from the distributed accounts. So the proper analogy here would be like yahoo going down in 1999.
Re: Bluesky April 2026 Outage Post-Mortem
#26Re: Bluesky April 2026 Outage Post-Mortem
#27> What I had missed is that we deployed a new internal service last week that sent less than three GetPostRecord requests per second, but it did sometimes send batches of 15-20 thousand URIs at a time. Typically, we'd probably be doing between 1-50 post lookups per request. That’ll do it.
Re: Bluesky April 2026 Outage Post-Mortem
#28Re: Bluesky April 2026 Outage Post-Mortem
#29> What I had missed is that we deployed a new internal service last week that sent less than three GetPostRecord requests per second, but it did sometimes send batches of 15-20 thousand URIs at a time. Typically, we'd probably be doing between 1-50 post lookups per request. That’ll do it.
Re: Bluesky April 2026 Outage Post-Mortem
#30I don't really understand this architecture, but I thought Bluesky was distributed like Mastodon? How can it have an outage?