Bluesky Outage: What Happened and How We Fixed It

On May 18, 2026, Bluesky experienced a widespread outage that affected thousands of users worldwide. Both the website and mobile app were inaccessible for about an hour. Bluesky's status page confirmed elevated error rates before service was restored. Below, we answer the most common questions about the incident.

Jump to: What happened? | How many users? | Bluesky's response | Timeline | Website and app? | Widespread issue? | Communication updates

1. What exactly happened to Bluesky on May 18, 2026?

On the evening of May 18, 2026, Bluesky suffered a major service disruption. Users trying to access the social media platform encountered error messages or extremely slow loading times. Reports began flooding in around 8:21 PM ET. Bluesky's internal monitoring systems detected a sharp increase in error rates, which led to the platform becoming largely unusable. The outage affected both the main website and the mobile application. The company’s engineering team immediately began investigating the root cause, later attributing it to a server configuration issue. By 9:06 PM ET, Bluesky confirmed that service had been restored and that they were monitoring the situation to prevent recurrence.

2. How many users were affected?

Thousands of users reported being unable to access Bluesky during the outage. The exact number is difficult to pinpoint, but third-party monitoring services, such as DownDetector, showed a massive spike in complaints starting at approximately 8:20 PM ET. The geographic spread was global, with reports coming from North America, Europe, and parts of Asia. Bluesky has a rapidly growing user base, so even a relatively short downtime impacted a significant portion of active users. The company did not release an official count, but the volume of social media posts about the outage indicates it was widespread.

3. What did Bluesky say about the outage?

Bluesky acknowledged the issue quickly via their official status page and social media accounts. In a statement posted around 8:30 PM ET, they said they were investigating elevated error rates affecting the platform. They did not initially disclose the root cause but assured users that their team was working on a fix. Approximately 45 minutes later, Bluesky updated the status page to announce that service had been restored and that they were continuing to monitor the situation. The company thanked users for their patience and apologized for the inconvenience. No further details about the specific technical error were provided, but they emphasized their commitment to reliability.

4. When did the outage start and when was it resolved?

The outage began around 8:21 PM ET on May 18, 2026. Users first reported problems shortly before that time, but the official status page confirmed elevated error rates at 8:21 PM. Bluesky’s team worked through the issue, and by 9:06 PM ET—approximately 45 minutes later—service was fully restored. The total downtime was roughly 45 minutes. This timeline was communicated through Bluesky’s status site and social media posts. The quick resolution demonstrated the company's ability to respond to critical incidents efficiently.

5. Did both the website and app go down?

Yes, the outage impacted both the Bluesky website and the mobile app. Users trying to access the platform via desktop browsers encountered errors or blank pages, while mobile app users saw loading failures or were unable to log in. This dual failure suggested a backend issue rather than a problem with a specific interface. Bluesky's engineering team focused on the server infrastructure, which handled requests for both platforms. After the fix, both the web and mobile versions became accessible again simultaneously.

6. Was this a widespread issue?

Absolutely. The outage was not limited to a specific region or user group. Reports came in from multiple continents, indicating a global impact. The spike in complaints on DownDetector and social media was dramatic, with thousands of users chiming in within minutes. Such widespread issues typically point to a problem with core infrastructure rather than localized network problems. Bluesky confirmed this by stating they were investigating elevated error rates, which implies a system-wide failure. The company's ability to restore service in under an hour suggests they have robust monitoring and rapid response protocols in place.

7. How did Bluesky communicate updates?

Bluesky used two primary channels: their official status site (status.bsky.app) and their social media profiles. The status page provided real-time updates, including the initial notice of elevated error rates, ongoing investigation, and eventual restoration. Additionally, Bluesky posted brief updates on X (formerly Twitter) and their own platform. The communication was clear and timely, with no unnecessary jargon. Users appreciated the transparency, even though no detailed technical explanation was given. This approach helped manage user expectations and reduce confusion during the downtime.