What to tell them:

1. Project ID:08c2ac10-3936-4670-9b4b-cc1250484971

2. Environment:production

3. Services affected:

   • suscripciones-shopify-app (FastAPI)

   • Postgres (postgres-ssl:18)

4. Timeline:

   • App was working fine 2 days ago

   • No code changes pushed

   • Started failing at 2026-04-10 02:26 UTC

5. Symptoms:

   • Postgres image pull fails: failed to resolve reference "ghcr.io/railwayapp-templates/postgres-ssl/manifests/18": dial tcp 140.82.116.33:443: i/o timeout

   • App cannot connect to Postgres on internal network (postgres.railway.internal) — both IPv4 and IPv6 timeout

   • App cannot connect via public TCP proxy either

   • Postgres container is running but rejecting all connections

6. What we've tried:

   • Internal DNS vs public proxy

   • IPv6 egress enabled/disabled

   • TCP proxy enabled/disabled

   • Container restarts

   • Code fixes (SSL parameters)

   • All failed with timeouts

This is a Railway infrastructure issue — either:

• Internal network isolation between containers

• Container registry access failure

• Network policy blocking Postgres connections

Contact Railway Support:https://railway.com/support

They need to investigate the network connectivity and container registry access in your environment.