Bluesky Hit by Service Disruption Today
▼ Summary
– Bluesky experienced a network disruption that caused significant delays in its “Following” feed, with posts appearing hours out of date.
– The author’s personal feed was affected, failing to show recent posts, while other users reported no issues at all.
– Attempting to view specific posts resulted in errors, with links showing the content could not be found despite the posts existing.
– Bluesky’s service status page later acknowledged the “network disruption” that delayed some posts by several hours.
– The outage was not universal, as some colleagues and users experienced no problems during the incident.
Bluesky, the decentralized social platform often seen as an alternative to X, experienced significant service problems today. Users reported a range of intermittent issues, from feeds failing to update to posts becoming inaccessible. The disruption highlighted the growing pains of a network still in its developmental stages.
The problems first became apparent when chronological timelines stopped refreshing. For many, their “Following” feeds were frozen, showing no new posts for a period of up to two hours. Given the number of active accounts followed, this sudden silence was a clear indicator that the service was struggling. Interestingly, the outage was not universal; some users reported their feeds continued to load without any interruption throughout the incident.
A particularly frustrating issue involved posting new content. While the platform’s interface indicated that a post was published successfully, even generating notifications for replies, attempting to view the post directly often resulted in an error message stating it could not be found. This created a confusing situation where content appeared to exist in one part of the system but was unavailable elsewhere.
Initially, Bluesky’s official status page did not reflect any ongoing problems. However, it has since been updated to acknowledge a “network disruption” that caused delays for some posts. Reports from other users corroborated the issues, with one colleague receiving an error message about a problem contacting the feed server. Discussions on platforms like Reddit also confirmed that other individuals were experiencing similar difficulties.
The selective nature of the outage suggests the problem was related to specific servers or network pathways rather than a complete platform failure. By the end of the day, service for most users had been restored to normal functionality. The company has been contacted for further details on the cause of the disruption.
(Source: The Verge)
