Bluesky has been dealing with a DDoS attack for nearly a full day
dotmanish
27 points
12 comments
April 17, 2026
Related Discussions
Found 5 related stories in 55.7ms across 4,783 title embeddings via pgvector HNSW
- Bluesky Is Down alex_suzuki · 21 pts · April 16, 2026 · 62% similar
- Bluesky April 2026 Outage Post-Mortem jcalabro · 134 pts · April 10, 2026 · 58% similar
- Bluesky users are mastering the fine art of blaming everything on "vibe coding" ulrischa · 26 pts · April 10, 2026 · 48% similar
- BlueHammer abuses Windows Defender's update process to gain SYSTEM access BullsEye0 · 26 pts · April 11, 2026 · 45% similar
- Bluesky CEO Jay Graber is stepping down minimaxir · 349 pts · March 09, 2026 · 44% similar
Discussion Highlights (5 comments)
minimaxir
The prevalent discourse/attempt-at-a-meme-but-people-are-taking-it-seriously saying "Bluesky is down because of AI vibecoding!" is starting to get annoying and unoriginal. Even when Bluesky confirmed it's a DDoS, the line is now "maybe they wouldn't have gotten DDoSed if they didn't vibecode and their code was better."
userbinator
What are the chances some company offers to "save" them with a security service which coincidentally will also require users to use the latest officially-sanctioned browsers, OSes, and "trusted" hardware to pass the "security check"...
bit1993
A decentralized protocol by definition should not be vulnerable to DDos attacks.
adrithmetiqa
Is this just for fun or is there some underlying purpose to those type of attack? Is it possible to have any certainty when answering that question?
OuterVale
The interface seemed to function as normal, but specifically the API was targeted, which left a lot of confused users who were seeing the interface peppered with errors. Watching as it unfolded, it seems it affected certain regions to begin with and then slowly spread worldwide. Seems they might have failed to host the status page ( https://status.bsky.app ) separately as well, because that went down several times throughout the outage. They also weren't very active in updating the status page, and the notice that was there had a typo of 'reginos' and a description of 'null'.