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.

We have identified the root cause, and it will be resolved in 10-15 minutes. Thank you for your patience!

This service is currently undergoing unplanned downtime, and we are so sorry for the inconvenience this may have caused. We are investigating the root cause right this second and will update this the moment we know more.