Read the Docs got hit by a distributed denial-of-service attack, and the team has published a postmortem explaining what happened.
The open-source documentation host - the default place a huge number of projects, especially in the Python ecosystem, point their docs - says it experienced a DDoS attack in the days leading up to this post. In a write-up on its own blog, the team walks through how the attack unfolded and the steps taken to keep the service available. The post is framed as an explainer rather than a bare status-page update, laying out what the incident looked like from the inside. It quickly made the rounds on Hacker News, picking up over 80 points and more than 20 comments.
Read the Docs is unglamorous infrastructure that a large slice of the open-source world quietly depends on. When it wavers, it is the kind of outage developers notice immediately - a broken doc link, a stalled build - even if they never think about who runs the servers behind it. A detailed public write-up gives other small teams running critical infrastructure a real data point on what a DDoS attack against them might look like and how to prepare.
Publishing a postmortem at all is the more interesting move here. Plenty of infrastructure providers eat an attack like this and say nothing beyond a green checkmark on a status page; explaining the mechanics in public is still the exception, not the rule.