a month ago
Project: zucchini-rebirth (3623dd9e-991e-48ec-9f6d-3f73959da597)
Service: web (852852c9-47ef-49ae-8b2b-8ba8eb90e2b0), environment production
Since roughly 2026-07-08 ~20:30 UTC, every deployment fails instantly at "Deploy → Create container" with "Failed to create deployment" after successful builds (6+ consecutive attempts, via CLI railway up and redeploy). Your in-dashboard Diagnose tool states it's a platform-side issue preventing container creation, not our code/config.
The service has a volume (web-volume, mounted at /data) and a custom domain (ermaz.app). The service is currently fully down. Recent failed deployment IDs include: 602a7a03-96ab-43ca-a10d-859a800ddefb, 723668f6-97e6-4390-be3d-232ca3e5cf8f.
Could you unblock container creation for this service, or advise if the volume/host needs migration on your side?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hi - apologies. We had an incident which caused this behavior. (https://status.railway.com/incident/V0KCMT8G) Everything should be back to normal now. Let us know if you see otherwise.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago