Live data from Hacker News

Bluesky April 2026 Outage Post-Mortem

pckt.blog

11–20 of 85 posts

Re: Bluesky April 2026 Outage Post-Mortem

#14

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

less than ideal if I had to be frank.

Re: Bluesky April 2026 Outage Post-Mortem

#17
post #15

I 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

#19
post #15

I don't really understand this architecture, but I thought Bluesky was distributed like Mastodon? How can it have an outage?

It’s more of a concept of a plan for being distributed. I even went through the trouble of hosting my own PDC and still, I was unable to use the service during the outage

Re: Bluesky April 2026 Outage Post-Mortem

#20
post #17
post #15

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

Google and MSN Search were already available at this time. Also websites used to publish webrings and there was IRC and forums to ask people about things.
Post reply on HN