Bluesky is experiencing a significant service outage, with the company confirming on its status page that systems in at least one region went down starting around 6:42 GMT on April 16, 2026.
"We are investigating an incident with service in one of our regions… Some systems down," the company posted. "We are starting to see some early recovery, but many users and services are still impacted."
The outage comes at an awkward moment for the Jack Dorsey-founded platform, which has positioned itself as the decentralized alternative to X and has been absorbing waves of users frustrated with Elon Musk's changes to that platform. April has already been a rough month. A prior incident earlier this month knocked the service offline for thousands of users and prompted the company to publish detailed post-mortems explaining technical failures, including problems with port exhaustion.
What We Know So Far
Details remain thin. Bluesky has described the incident as regional, suggesting that users in certain geographic areas are bearing the brunt while others may see intermittent issues or none at all. The status update indicates early signs of recovery, but "early" is doing a lot of work in that sentence. Users across the platform have reported inability to load feeds, post content, or access notifications.
The regional framing is worth noting. Bluesky's architecture relies on the AT Protocol, a decentralized framework that theoretically allows for distributed hosting and resilience. In practice, the platform still depends heavily on centralized infrastructure for core services. When a region goes down, the decentralized philosophy meets the reality of operational complexity.
A Pattern Forming
Two major outages in a single month raises questions about Bluesky's infrastructure maturity. The platform has grown rapidly, particularly after X's controversial policy changes pushed creators and casual users toward alternatives. Growth is good. Growth that outpaces your ability to keep the lights on is less good.
The port exhaustion issue from the earlier April outage is a classic scaling problem. It happens when a system runs out of available network connections, usually because traffic exceeds what the infrastructure was designed to handle. That Bluesky hit this wall suggests the platform's growth has been faster than its engineering team anticipated, or that the team is still building out the redundancy needed to handle surges.
For users who migrated from X seeking stability and a calmer experience, repeated outages are a reminder that smaller platforms come with trade-offs. X has its own problems, but it rarely goes fully offline. Bluesky is still proving it can handle the weight of its ambitions.
The company has generally been transparent about technical issues, publishing explanations that go into genuine detail rather than vague corporate apologies. That approach builds trust. But trust only carries you so far when people can't access the service.
We'll update this story as Bluesky provides more information on the scope and resolution of the outage.
