Bluesky down right now is the dominant issue on 16 April 2026 at 09:45 BST, with users across the United States, United Kingdom and parts of Europe reporting that Home and Explore feeds are not loading, instead showing blank timelines, placeholder lines or repeated errors such as “Failed to load feeds” and “Failed to fetch,” The WP Times reports. The disruption is affecting core feed delivery rather than full platform access, pointing to a backend failure likely linked to an upstream service provider, with the highest concentration of incidents in US East infrastructure zones but clear spillover into international regions.
The outage remains partial but widespread, with users able to log in while content fails to load or refresh in real time across both mobile and web platforms. Early indicators show a service degradation rather than a full shutdown, where feed aggregation and content retrieval systems are unstable while other components remain operational. This pattern mirrors previous upstream-related incidents and confirms that, despite its decentralised architecture, Bluesky still depends on external infrastructure layers capable of triggering functional disruption without taking the entire platform offline.
What is happening with Bluesky feeds right now
The current incident is centred on feed delivery, not account access. Users can generally open the app and log in, but the platform’s core function — delivering real-time content — is failing. Across the US, UK and Europe, users report:
- Completely blank Home timelines with loading placeholders
- Explore and Discover feeds not loading
- Persistent errors on refresh attempts
- Connection warnings despite stable internet
In many cases, the system returns messages such as “Unable to connect” or “Something went wrong when contacting the feed server,” confirming a failure at the feed service level rather than a full system outage. In practical terms, Bluesky is accessible, but its primary function is partially offline.
Scale of the outage and affected regions
User reports and monitoring data show a sharp spike in complaints during early US hours and mid-morning in Europe on 16 April.
Reported issues breakdown
| Issue type | Approximate share |
|---|---|
| Feed / timeline loading | ~50% |
| Mobile app errors | ~25% |
| Website access problems | ~15% |
| Other (login, delays) | ~10% |
The majority of disruptions are linked to US East infrastructure, but the impact is clearly international, affecting:
- United States (primary concentration)
- United Kingdom
- Germany, France and wider Europe
The spread confirms the issue is tied to shared backend systems rather than a localised outage.
Why Bluesky appears operational while feeds fail
One of the key issues for users is the mismatch between system status and actual performance. This reflects how modern platforms operate:
- Core infrastructure can remain online
- Individual services such as feeds can fail independently
- Third-party providers can disrupt functionality without triggering full outages
Bluesky’s architecture relies on:
- Personal Data Servers (PDS)
- Feed generation services
- External cloud and routing providers
If feed aggregation fails, the platform appears down to users even while core systems remain technically active.
What Bluesky has said so far
Bluesky has confirmed the issue is linked to an upstream provider and is being actively addressed.
“This incident is tied to an upstream provider issue, and we are working to restore full service as soon as possible” (Bluesky status update, 16 April 2026)
No global outage has been declared, indicating a service-specific disruption rather than a system-wide failure.
User behaviour during the outage remains consistent across regions and devices, reinforcing that the issue is systemic rather than local. Users in the United States, United Kingdom and Europe report identical symptoms: feeds failing to load or update, missing or delayed posts, and repeated error messages despite stable internet connections. In some cases, the web version partially loads while the mobile app fails entirely, while switching networks or using VPN services may produce temporary improvements. These patterns point clearly to instability within backend feed delivery systems rather than any issue on the user side. At the same time, the incident highlights a structural challenge tied to Bluesky’s rapid growth. The platform’s model — built on decentralisation, user-controlled feeds and reduced reliance on opaque algorithms — has driven strong adoption, but also places increasing pressure on feed generation layers, data routing infrastructure and third-party service providers. As user volumes scale, even short disruptions become highly visible, particularly because the platform’s core value is real-time content delivery. When feeds stop updating, the service effectively stops functioning.
For users, practical options remain limited while the issue persists. Restarting the app, clearing cache, switching between mobile and web access or changing network connections may offer temporary access, but do not resolve the underlying problem. Recovery depends entirely on backend stabilisation, typically involving upstream provider fixes, traffic rerouting or load balancing across servers. Based on previous incidents, similar disruptions have often been resolved within hours, although no confirmed timeframe has been provided for the current outage.
In a broader context, the outage reflects a key reality of modern social platforms: decentralisation reduces single points of failure but introduces distributed dependency risks. Systems no longer fail as a single block — instead, specific layers such as feeds, APIs or routing can break independently, creating partial outages that are highly visible to users but harder to diagnose and resolve. As Bluesky continues to scale, maintaining stability across these distributed systems will be critical to sustaining user trust and long-term growth.
What is Bluesky and why it matters now
Bluesky is a decentralised social media platform originally initiated by Jack Dorsey as an alternative to traditional, centralised networks. Unlike platforms such as X (formerly Twitter), Bluesky is built on an open protocol (AT Protocol), allowing users to control their data, identity and the algorithms that shape their feeds. The core idea behind Bluesky is to shift power away from a single company and give users more control over what they see and how content is moderated. This includes:
- Customisable feeds instead of a single algorithm
- The ability to run independent servers (Personal Data Servers)
- Greater transparency in moderation and content ranking
This model is designed to solve long-standing issues in social media, including algorithmic bias, lack of control over content visibility and platform monopolies. However, it also introduces complexity: instead of one central system, Bluesky relies on multiple interconnected layers, including external infrastructure providers.
The current outage highlights both sides of this model. While decentralisation can improve resilience in theory, in practice it still depends on shared infrastructure — meaning failures in upstream services can disrupt core functions such as feed delivery across multiple regions at once.
Read about the life of Westminster and Pimlico district, London and the world. 24/7 news with fresh and useful updates on culture, business, technology and city life: What is the Porsche 911 GT3 S/C and why is it the most significant open-top GT car yet