Project: supportive-compassion (ID d108e9e2-ad56-4f23-a3dd-050dd103bbaa), deployed from the official railway.com/deploy/supabase template (6ixfalls/supabase-postgres, PostgREST v14.12, Envoy).

Symptom: Every request to /rest/v1/* through the public Envoy gateway returns:

HTTP 503

upstream connect error or disconnect/reset before headers. reset reason: remote connection failure

/auth/v1/* (GoTrue) requests through the same Envoy instance work fine, so this looks specific to the Postgrest route/cluster, not Envoy as a whole.

What I've checked/tried, none of which changed anything:

• Postgrest's own deploy logs are clean on every restart -- connects to Postgres successfully, schema cache loads fine (7 relations), no errors.
• • Envoy's REST_HOST variable correctly points to postgrest.railway.internal, matching Postgrest's actual private domain.
• • Redeployed Postgrest (x2), Envoy (x2), Postgres, and Supavisor -- identical error every time, byte-for-byte.
• • No incident showing on status.railway.com or in the community forum matching this.

Possibly relevant: the issue first appeared shortly after I redeployed one unrelated service (GoTrue Auth, for a config change) and, separately, an accidental UI click briefly created a phantom service on the project canvas that I deleted before it ever deployed. Around that same window, the Railway dashboard itself showed me a "Networking info temporarily unavailable -- Domains and TCP proxy details could not be loaded" toast. I can't confirm causation, but the timing is suspicious enough to mention.

This looks like a private-networking issue between two services in the same project/environment, not an app-level misconfiguration. Any help figuring out what's actually failing on the backend would be appreciated -- happy to provide deployment IDs or logs on request.