• Our custom domain stopped accepting connections

  entirely — TCP handshakes never completed (curl: connect=0.000000s, hangs to

  timeout). Users saw "Can't reach the server."

• Our container was completely healthy throughout: scheduled background jobs

  kept logging on time for the full outage window, and the DB stayed reachable.

  No crash, no OOM, no restart.

• The service's generated domain served perfectly the entire time — GET /api/version returned in ~200ms with a clean TLS handshake (301 via our canonical-host redirect).

• The custom domain's CNAME target that Railway had assigned, resolved to a Railway-owned edge IP that refused/hung connections. whois confirms

  these are Railway IPs (RLWY-HIKARI-01, Railway RC-1550). So the live service

  moved to a different Railway edge IP (69.46.46.82) and the edge behind the

  custom domain's target was dead.

• A Railway service RESTART did NOT fix it (we polled for 2+ minutes after) —

  confirming the fault is in the edge/routing layer, independent of the container.

Solution/fix? Our current solution: Delete and re-add the custom domain and wait for it to come live, not very sustainable. Thanks!