Introduction
You opened the Bluesky app, ready to scroll through your custom feeds. Instead, you saw a blank screen. Then an error message. Then nothing. You are not alone. The Bluesky outage 2026 on April 16 affected thousands of users across the United States, the United Kingdom and parts of Europe, preventing them from accessing Home feeds, Explore timelines and notifications. This report explains what happened, why it happened and when the platform came back online.
What Happened During the April 16 Disruption?
The Bluesky outage 2026 began as a partial disruption rather than a complete shutdown. Users could still log in and view profiles, but core features failed.
- Home timeline would not load, showing only a spinning wheel or a blank screen.
- Explore and Discover feeds returned messages like “Failed to load feeds” or “Unable to connect.”
- Notifications and threads also became inaccessible for many users.
Bluesky protocol engineer Bryan Newbold noted around 3:46 a.m. ET that “oof, our services are getting pretty hard tonight”. The problems appeared in waves, with connection timeouts affecting specific servers.
When Did the Outage Start and End?
The Bluesky outage 2026 timeline unfolded over several hours:
| Time (ET) | Event |
|---|---|
| 1:42 a.m. | First signs of trouble; three servers go down. |
| 2:21 a.m. | Downdetector reports a sharp spike in user complaints. |
| 6:42 a.m. | Bluesky’s status page acknowledges the incident. |
| 11:40 a.m. | Early signs of recovery; app and web begin working again. |
| 2:28 p.m. | Status page declares Bluesky operational again. |
External resource: For real‑time status monitoring, visit Bluesky’s official status page or check user‑reported issues on Downdetector.
What Caused the Disruption?
The Bluesky outage 2026 had two reported causes.
DDoS Attack (Primary Cause)
Bluesky COO Rose Wang attributed the service interruptions to a denial‑of‑service attack. The platform later explained that it had been attempting to mitigate “a sophisticated Distributed Denial‑of‑Service (DDoS) attack, which intensified throughout the day.” The attack affected feeds, notifications, threads and search. Bluesky stated it had not seen any evidence of unauthorized access to private user data.
Upstream Service Provider Issue (US East Region)
In other reports, the disruption was linked to an issue with an upstream service provider, specifically affecting the US East region. The provider’s failure impacted feed delivery systems.
For a deeper technical breakdown, read our Bluesky DDoS attack explained guide.
Comparison Table: Bluesky vs. Other Major Outages
| Platform | Outage Date | Primary Cause | Duration | Feed Impact |
|---|---|---|---|---|
| Bluesky | April 16, 2026 | DDoS attack | ~12 hours | Partial |
| X (Twitter) | July 2023 | Rate‑limiting | ~8 hours | Full |
| March 2024 | Server error | ~6 hours | Partial | |
| October 2021 | BGP routing | ~7 hours | Full |
Bluesky’s outage was unusual because logins stayed up while feeds failed.
Real-World Lessons from the Outage
The Bluesky outage 2026 offers practical lessons:
- Partial outages are confusing. You can log in but feeds are empty. This makes users think their phone is broken.
- Status pages save time. Always check
status.bsky.appbefore restarting your router. For a full guide, see how to check service status during an outage. - DDoS attacks are getting smarter. The “rolling blackout” pattern made the attack harder to stop.
For a minute‑by‑minute breakdown, visit our Bluesky outage timeline.
Why Did Feeds Fail While Logins Worked?
This is called a partial outage. Feeds are more complex than login systems. During a DDoS attack, attackers target the hardest‑working parts of the platform. That is why feeds go down first.
For a simple explanation, read our guide: Feeds fail, logins work – partial outage explained.
What Should You Do During the Next Outage?
Do not restart your router. Do not clear your cache. Follow these steps instead:
- Check the official status page.
- Look at Downdetector.
- Ask a friend in another region.
- Set a 15‑minute timer.
For the complete 7‑step checklist, see our social media outage checklist.
Frequently Asked Questions (FAQ)
Q1: Was the Bluesky outage a complete shutdown?
A: No. It was a partial outage. Users could still log in and view profiles, but feeds failed to load.
Q2: Did a DDoS attack cause the outage?
A: Yes. Bluesky confirmed a sophisticated DDoS attack intensified throughout the day.
Q3: How long did the outage last?
A: About 12 hours, from 1:42 a.m. to 2:28 p.m. ET on April 16, 2026.
Q4: Could I have fixed it on my end?
A: No. The problem was entirely server‑side. Troubleshooting your own device did nothing.
Conclusion
The Bluesky outage 2026 on April 16 affected thousands of users. A sophisticated DDoS attack, combined with an upstream provider failure, caused feeds and notifications to break while logins remained functional. By mid‑afternoon ET, Bluesky was operational again.
For ongoing service status updates, bookmark Bluesky’s official status page.