Hello Railway team,

Our production MinIO bucket service stopped responding without any application or configuration change, and all images served from it are now unavailable.

Affected service

• Project: blog
• Service: Bucket
• Environment: production
• Region: US East
• Public endpoint: https://bucket-production-d421.up.railway.app

Observed behavior

• Direct object requests time out; Railway network logs show HTTP 499 and occasional 502 responses after several seconds.
• The Next.js image optimizer returns HTTP 504 because the upstream bucket does not respond.
• Railway Console reports that the service container is not running (status: exited).
• A manual restart on 2026-08-11 around 10:16 KST completed in the UI, but the container exited immediately again.
• The only Bucket deployment log during the last 7 days is a volume-mount event. There is no "Starting Container" line, MinIO startup output, or application error.
• CPU and memory remain near zero.
• The attached volume shows approximately 1.8 GB used out of 5 GB.

Configuration notes

• Image source: minio/minio:latest
• Healthcheck: /minio/health/ready
• Restart policy: On Failure, maximum 10 restarts

Request

Please inspect the underlying host/container runtime and the attached volume state. Do not delete, reinitialize, or replace the production volume. If the volume or its host is impaired, please repair or migrate it while preserving all existing data.

A similar MinIO incident was resolved after Railway restored the volume to a working state:

https://station.railway.com/questions/misio-storage-server-doesn-t-work-proper-be2f0326

Thank you.