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."
OuterValelast Friday at 5:54 AM
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'.
userbinatorlast Friday at 4:56 AM
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"...
It seems like DDoS's are getting harder and harder to deal with. The tips that worked 10 years ago are now easily worked around. I keep seeing people on here say "just use TLS fingerprinting" like it's a panacea, but I can't remember the last time an attack didn't spoof their fingerprint.
It feels like, outside of custom behavior tracking, there's no good way to truly protect your site without making it more restrictive in general. Require JS, client side challenges, cloudflare.
tasukilast Friday at 8:26 AM
I thought it was distributed/decentralised?
strimozalast Friday at 10:52 AM
Curious how they handled it at the CDN level. I use Bunny CDN for video streaming on my project and signed URLs help a lot for abuse prevention, but a full DDoS is a different beast entirely.
adrithmetiqalast Friday at 5:48 AM
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?
ddacticlast Friday at 2:03 PM
[dead]
aaron695last Friday at 11:54 AM
[dead]
aaron695last Friday at 6:11 AM
[dead]
weird_tentacleslast Friday at 5:14 AM
[dead]
0xeddlast Friday at 5:51 AM
[dead]
decrementallast Friday at 5:31 AM
[dead]
midtakelast Friday at 6:19 AM
[flagged]
mrweasellast Friday at 8:03 AM
Hopefully there will be some post-mortem. It seems like we're don't really see that many deliberate DDoS attack anymore. Not that it doesn't happen, but they really don't provide that much value against a target like Bluesky (unless you really hate them).
I'd be interested in how the attack manifests. Is it an actual DDoS? Is it highly aggressive scraping? We should be able to see this in how the attack manifests itself. What is the sources? That's a little harder, but it would be interesting to know if it's compromised devices, residential proxies, rented cloud capacity or something else.
bit1993last Friday at 5:23 AM
A decentralized protocol by definition should not be vulnerable to DDos attacks.