evolution-api: 10+ consecutive CREATE_CONTAINER failures - service down 5+ days
brunnerfelipe-cloud
HOBBYOP

a month ago

Service ID: 967bdfb2-2e4d-4fc8-ac0b-540ea7d19c3f

Project: superb-patience

Environment: production

OUTAGE: 5+ days (since ~June 3, 2026)

Every deployment fails at "Deploy > Create container"

Error: "Failed to create deployment - Infrastructure Error"

Failed deployment IDs:

  • 3d25beda-6299-4df9-af82-727a2cad7008
  • 607f3f74-737e-4295-a6d8-2eb13b72c65b
  • 2ea5e935-b235-4b5c-b7d5-3cf12b7c919c
  • 10+ total failures

Regions tried: us-west2 and us-east4 (both fail)

Configuration: unchanged from last successful deploy (June 3)

Linked services (Postgres): healthy

Docker image (atendai/evolution-api:latest): valid

This is infrastructure-level failure. Please investigate urgently.

$10 Bounty

4 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 1 month ago


a month ago

Deploying a Whatsapp bot is not allowed on railway unless you're using official Meta API

Change your image source to evoapicloud/evolution-api


mayori

~~Deploying a Whatsapp bot is not allowed on railway unless you're using official Meta API~~ Change your image source to `evoapicloud/evolution-api`

a month ago

You can use the official Meta API in the evolution-api bot.


a month ago

oh, didnt know that haha, I'll edit my answer


a month ago

evoapicloud/evolution-api:v(your version here) to be more precise.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...