Introduction
At 1:42 a.m. ET, the first server went silent. Over the next 12 hours, millions of requests failed. This Bluesky outage timeline tracks every major event from the initial timeout errors to the final “all systems operational” declaration. For the high‑level summary, read our Bluesky outage 2026 pillar guide.
The Complete Timeline (All Times Eastern)
| Time (ET) | Event |
|---|---|
| 1:42 a.m. | Three Bluesky servers go down, including api.pop1.bsky.app (US East). Connection timeouts begin. |
| 2:21 a.m. | Downdetector reports a sharp spike in user complaints. Over 2,000 reports in 15 minutes. |
| 3:46 a.m. | Bluesky protocol engineer Bryan Newbold posts: “oof, our services are getting pretty hard tonight”. |
| 6:42 a.m. | Bluesky status page acknowledges the incident: “Some systems are down. We are investigating.” |
| 9:15 a.m. | COO Rose Wang confirms a DDoS attack on social media. Feeds remain broken for most users. |
| 11:40 a.m. | Early signs of recovery. Some users report feeds loading slowly. Intermittent errors continue. |
| 1:10 p.m. | Bluesky updates status page: “We have identified the root cause and are applying mitigations.” |
| 2:28 p.m. | Status page declares Bluesky operational again. “All systems are now functioning normally.” |
| 3:00 p.m. | Residual loading delays reported but no widespread failures. |
Key Observations from the Timeline
The Bluesky outage timeline reveals three important patterns:
- Slow acknowledgment: It took five hours from the first server errors to an official status page update (1:42 a.m. to 6:42 a.m.).
- Rolling recovery: Services came back in waves, not all at once. Feeds returned before notifications for many users.
- Residual delays: Even after the “operational” declaration, some users experienced slow loading for another hour.
Frequently Asked Questions (FAQ)
Q1: Why did Bluesky take so long to acknowledge the outage?
A: Small teams often wait to confirm an issue before posting. Early misdiagnosis can cause confusion. Five hours is longer than ideal but not unusual for a growing platform.
Q2: Was the outage worse in any specific region?
A: Yes. The US East region suffered an additional upstream provider failure, compounding the DDoS attack. Users in Europe and Asia had slightly better reliability.
Q3: How can I get real‑time alerts for future outages?
A: Follow Bluesky’s status page on social media or set up a monitor with a service like UptimeRobot.
Q4: Did the timeline differ between web and mobile apps?
A: Not significantly. Both web and mobile use the same backend APIs. However, mobile app caches sometimes hid the failure for a few minutes longer.
Conclusion
This Bluesky outage timeline shows a 12‑hour disruption caused by a DDoS attack, worsened by an upstream provider failure in the US East region. The slow acknowledgment frustrated users, but the eventual recovery restored full functionality by mid‑afternoon.
Return to the main Bluesky outage 2026 guide for the cause analysis and comparison table.