Bluesky Says DDoS Attack Disrupted Platform; Service Stabilized April 16
Summary
Bluesky said a DDoS attack starting late April 15, 2026 disrupted feeds, notifications, threads and search. Service stabilized by about 9 p.m. PDT April 16; the company reported no evidence of unauthorized access. “313 Team” claimed responsibility, but attribution is un
Key points
- Bluesky reported that a DDoS attack began late on April 15, 2026.
- The attack intermittently disrupted feeds, notifications, threads and search.
- Engineers worked overnight to mitigate the attack; Bluesky said the application had stabilized by about 9 p.m. PDT on April 16 despite ongoing DDoS traffic.
- Bluesky reported no evidence of unauthorized access to private user data.
- A group calling itself “313 Team” reportedly claimed responsibility in a Telegram message; Bluesky did not officially attribute the attack.
Article Details
- Victim Organization
- Bluesky
- Incident Type
- Distributed denial-of-service (DDoS) attack causing service availability disruptions
- Incident Date
- 2026-04-15
- Operational Impact
- Feeds, notifications, threads, and search experienced intermittent interruptions. Bluesky reported the application stabilized around 9 PM PDT on April 16 despite ongoing DDoS traffic.
- Claim Status
- confirmed