evolution-api production outage - container scheduling failure in us-west2
trafegocombraga-7
HOBBYOP

a month ago

Service: evolution-api (ID: 8f1deb92-b6ed-4c60-8815-aae2d095829f)

Environment: production (ID: de2fa3ea-6b90-42c2-bdbe-c62465c64509)

Region: us-west2

Status: Offline - 11+ consecutive deployment failures on July 7, 2026

Every deployment fails at CREATE_CONTAINER stage with "Failed to create deployment" before any application code runs. No logs produced. Configuration is unchanged from last successful deployment (May 6). Postgres database is online and healthy.

This is a production outage. Please investigate container scheduler in us-west2 and restore service availability.

Solved$10 Bounty

Pinned Solution

a month ago

The image moved from atendai/evolution-api to evoapicloud/evolution-api.

Just change your source image to evoapicloud/evolution-api, make sure you're using the right version (see https://hub.docker.com/r/evoapicloud/evolution-api/tags for all the versions).

1 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

The image moved from atendai/evolution-api to evoapicloud/evolution-api.

Just change your source image to evoapicloud/evolution-api, make sure you're using the right version (see https://hub.docker.com/r/evoapicloud/evolution-api/tags for all the versions).


Status changed to Solved medim about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...