13 days ago
Hi Railway Support,
I have a persistent infrastructure issue blocking ALL deployments on my account since today.
Account: restaurarcordeiro (Hobby plan)
Project ID: 92d48b69-fd5a-47de-9c23-502a1b14b83b
Region: US West (tried US East too — same error)
Problem:
Every single deployment fails at CREATE_CONTAINER stage within 1 second with no logs:
- Deployment failed during deploy process
- Deploy › Create container
- Failed to create deployment
What I tried:
- Multiple redeployments (15+ attempts)
- Different Docker images (evolutionapi/evolution-api:latest, atendai/evolution-api:v2.1.1)
- Changed region from US West to US East — same error
- Deleted and recreated the service — same error
- Added credits ($5) after trial expired — issue started after credit renewal
- Railway Agent confirmed: "Persistent infrastructure issue at container creation — not transient"
Important: The FIRST deployment of this service worked fine (was Online). After trial credits ran out and I added new
credits, ALL subsequent deployments fail at CREATE_CONTAINER.
Railway's own diagnosis tool says:
▎ "This deployment failed during container creation due to a transient infrastructure issue... The service also has a
▎ separate ongoing issue"
But it is NOT transient — it has been failing for hours across multiple services and regions.
Request:
Please manually investigate and reset the container scheduling for my account. This appears to be an account-level
quota or infrastructure lock after credit renewal.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 13 days ago
12 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 12 days ago
4 days ago
this is account-side, not your app. every image, every region, every service failing at create container right after your credits rolled over is the tell, nothing in your project changed, your account state did. no amount of redeploying fixes that. you need a railway team member to look at the account, drop your project id and that "failed to create container" deploy id here and ask them to check for a billing/quota lock from the credit renewal.