Complete

This issue was resolved quickly after the incident occurred, as a Security Rule was implemented, blocking harmful IPs. The services itself were not affected.

Jellyfin metadata rebuild completed

Sorry for the wait. We originally expected the metadata rebuild to take around 4 hours, but due to the large number of films and TV shows on the server that required metadata indexing, the process ultimately took approximately 2 days to complete.

The rebuild has now finished successfully, and Jellyfin should be back up and running normally. Library browsing, search, metadata display, and playback functionality should all be restored.

We apologise for the...

Resolved

We’re back! Jellyfin should be up and running. Thanks for bearing with us.

AI post-mortem

The site was returning 502/530/503 errors because the instance ran out of RAM and began killing key tasks. The instance RAM was increased and rebooted, which brought services back; checks returned 200 and the incident was acknowledged and resolved shortly after.

Service has been marked as recovered automatically by the system.

AI post-mortem

The URL monitor went down and was returning 502 (then 530) errors from multiple regions, causing the alert. The service recovered on its own and the monitor started returning successful responses from all regions; the incident was auto-resolved shortly after recovery.

Jellyfin Incident Post-Mortem

Status: Resolved
Service: Jellyfin
Duration: 21 June 2026 – 22 June 2026

---

Summary

Between 21 June and 22 June 2026, Jellyfin experienced intermittent and extended unavailability due to repeated gateway/backend errors observed across multiple monitoring regions. The incident auto-resolved once normal responses were restored.

---

Impact

Users may have experienced:

• Inability to access Jellyfin
• Failed media streaming sessions
• Inte...

The Immich storage migration has been completed successfully.

Performance has returned to normal, and uploads, background jobs, media loading, and overall responsiveness should now be operating as expected.

Thank you for your patience during the migration.