Incident report
Eurosky service disruption, 13 to 17 November 2026
Last updated: 18 November 2026.
Summary
Between Friday 13 and Tuesday 17 November, people with accounts hosted by Eurosky had trouble uploading and seeing images, and feeds and notifications stopped loading four times, for between 20 minutes and an hour each. This affected accounts on eurosky.social and mu.social handles, whichever app you use.
The root cause was a fault at Hetzner, the company that stores images for us. That fault then triggered connection problems between our servers and Bluesky’s, which made things worse.
Where things stand on Wednesday 18 November, midday CET: uploads work, images are showing again, and feeds are stable. Our storage has been faster this morning but is not yet consistently back to normal, so a large image can still take a few seconds to appear the first time it is viewed. We do not consider this fully resolved until that is back to normal.
We have no indication that any posts, accounts or stored images were lost. We are sorry for the disruption and the inconvenience it has caused.
What you may have noticed
All times are Central European Time (CET).
| What you saw | When | Now |
|---|---|---|
| Image uploads hanging for 30 to 45 seconds, then failing | Fri 13 Nov, about 13:00, to Mon 16 Nov, about 10:00. In the worst spells, between a quarter and two thirds of uploads failed. | Working. Brief, isolated failures can still occur. |
| Posts with images failing to publish, or publishing with a blank image | Same period | Fixed for new posts |
| Images missing from feeds, especially larger photos, in mu, Bluesky and other apps | Sat 14 Nov, early morning, to Tue 17 Nov, about 23:30 | Loading again. Large images can be slow the first time. |
| Feeds, notifications, profiles and search not loading | Mon 16 Nov, about 19:35 to 19:57. Tue 17 Nov, about 09:37 to 10:35, about 15:43 to 16:43, and about 20:00 to 21:00. | Fixed |
| Account moves to Eurosky finishing with some images still missing | Sat 14 Nov, early morning, to Mon 16 Nov, late morning | Transfers are retried automatically; some are still catching up |
Signing in and posting text kept working during the disruption to image upload.
Timeline
Newest first. Times are CET and approximate.
| When | What happened |
|---|---|
| Wed 18 Nov, midday | Uploads are working and images are loading through Bluesky’s image service. Fewer than 3 in 100 of its image fetches are now cut short. Storage speed is improving but not yet steady. No further outages since Tuesday evening. |
| Wed 18 Nov, 00:10 | Bluesky confirms its own monitoring of our traffic looks healthy. |
| Tue 17 Nov, 23:00 to 23:30 | Bluesky gives its image service more time to fetch images from us (10 seconds, up from about 3), which works around the ongoing slow speeds from Hetzner. Images start appearing again. |
| Tue 17 Nov, 22:30 to 22:55 | Bluesky confirms the block on our server is cleared. |
| Tue 17 Nov, 20:00 to 21:00 | Fourth outage, with the same symptoms. It clears without any change on our side. |
| Tue 17 Nov, 15:43 to 16:43 | Third outage: about half of all requests for feeds, notifications and profiles fail. It clears without any change on our side. |
| Tue 17 Nov, 09:37 to 10:35 | Second outage, with the same symptoms. The alternative network address we switched to the evening before is now refused as well. It clears without any change on our side. |
| Mon 16 Nov, 19:35 to 19:57 | First outage: feeds, notifications, profiles and search stop loading due to interaction between our servers and Bluesky’s that triggers DDoS protection. We suspect this is partly a side effect of the issues with Hetzner. We restore service by sending traffic to Bluesky over a different network address. |
| Mon 16 Nov, about 10:00 | Image uploads recover to an extent; Hetzner storage degradation still ongoing despite appearing as “fixed” on their dashboard. Images are still slow to load, so most larger ones still do not appear in feeds. |
| Sat 14 to Mon 16 Nov | The worst period for uploads, with several waves of failures. Image transfers for people moving their accounts to Eurosky also fail during this time. |
| Sat 14 Nov, early morning | Images start going missing from feeds, as Bluesky’s image service can no longer fetch them from us in time. |
| Sat 14 Nov, 01:40 | Hetzner opens an incident for its object storage service in the data centre we use. It later reports the error as fixed and under monitoring; the incident is still open on its status page. |
| Fri 13 Nov, about 13:00 | First image upload failures. Hetzner logs a separate, shorter storage incident the same day. |
What went wrong
Three problems stacked on top of each other. It helps to know how an image reaches your feed:
- Your app sends the image to our server.
- Our server saves it with Hetzner, our storage provider.
- Bluesky’s image service fetches it from us and prepares it for display through their CDN.
- Apps such as mu and Bluesky show it in feeds.
1. Our storage provider had a fault (step 2). Hetzner’s storage service became unreliable from Friday 13 November. Our server could not save new images reliably, so uploads hung and failed. This is the second storage incident we have had with Hetzner since 11 October.
2. Images were too slow to fetch (step 3). After uploads recovered, reading images back from storage stayed about five times slower than normal. Bluesky’s image service waits only about 3 seconds for an image. Smaller images made it in time; larger ones did not, so they were missing from feeds. At the peak, around 8 in 10 of its attempts to fetch images from us were cut short. Each failed attempt was retried, which added more load.
3. Our server was temporarily blocked from reaching Bluesky. Feeds, notifications and profiles are assembled by Bluesky’s service, which our server contacts on your behalf. Four times, an automated protection system on Bluesky’s side stopped accepting connections from our server. Bluesky’s assessment is that the wave of errors caused by our storage problem is what triggered it.
We also fell short ourselves. Our status page only shows the general availability of our PDS and does not show the overall impact on the services we use.
Your data
This was an availability problem, not a security incident. We have seen no sign of attack.
| What | Affected? |
|---|---|
| Your account, password and sign-in | No |
| Your posts, follows, likes and lists | No. These are stored separately from images and were not involved. |
| Images you uploaded successfully | No. They are stored intact, even if they were slow or missing in feeds for a while. |
| Uploads that failed | These were never saved. Please upload them again. |
| Posts that published with a blank image | The post is intact but the image may not have been saved. The fix is to repost them. |
What we are doing about it
Already done
- Bluesky has lifted the block on our server, given its image service more time to fetch from us, and raised the limits that apply to our traffic. We are grateful to the Bluesky team for moving quickly and for all their support.
- We have an open support case with Hetzner about the storage service still running slowly.
In progress
- Moving image storage. We are evaluating other European providers that offer the type of storage we need, and planning the move. We expect this to take up to a couple of weeks.
- A more comprehensive status page. Our status page will be changed to reflect whether the service works for users, not only whether the server responds.
- Fewer single points of failure. We are looking at serving images directly as we transition to fully deploying our own CDN service (which we already use for part of the service), so that one slow link in the chain does not make images disappear. This has been on our roadmap and we are now looking to bring this forward before the end of the year.
- Less reliance on Bluesky for feeds. Our server still contacted Bluesky’s service for some people who had chosen Eurosky’s own. We are fixing that, so those people keep their feeds if the connection to Bluesky fails again.
We will update this report when the storage move has a date.
If you are still seeing problems
- An image will not upload: try again. If it keeps failing, tell us the time and the approximate file size.
- An older post shows a blank image: delete the post and publish it again.
- An image is slow to appear: this is expected for now with larger images, the first time anyone views them. It should load within a few seconds.
- You moved your account to Eurosky and images are missing: transfers are retried automatically. If they are still missing after a few days, contact us.
You can reach us at support@eurosky.tech. Please include your username, screenshots and roughly when the problem happened.