Service ACTIVE and healthy internally, edge returns 502 since GCP outage recovery
largelanguagesolutions-debug
HOBBYOP

a month ago

Project: motivated-radiance

Service: intellisquawk (backend, FastAPI)

Environment: production

Domain: intellisquawk-production.up.railway.app

Region: US East

Custom domain (in front, on Netlify): app.intellisquawk.com

Symptom: All HTTP requests to the public domain return 502

("no healthy upstream"). Browser sees CORS-style "Preflight

response is not successful. Status code: 502" because the

preflight itself is what's failing.

What's working:

  • Latest deployment 99c25e73 shows ACTIVE

  • Deploy logs show clean startup: "Application startup

    complete", "Uvicorn running on http://0.0.0.0:8080"

  • TLS handshake completes cleanly at the edge

  • Restart of the active deployment did NOT resolve it

What's not working:

Timeline:

  • Onset noticed Tuesday 2026-05-19 ~21:47 ET (during your GCP

    account suspension window)

  • Status page now shows Fully Operational, my service still 502s

  • Last successful login from end users was earlier Tuesday

Hypothesis: edge routing table for my service did not refresh

post-outage. Container is healthy but the edge can't reach it.

I have a separate project "loving-courage" in the same workspace

that is not the issue here; it's a defunct duplicate I'll clean

up separately.

Need: routing refresh / edge-to-container connection re-established

on motivated-radiance.

Time-sensitive: production app down for end users.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


sam-a
EMPLOYEE

a month ago

Your 502s are a direct result of the May 19 GCP service disruption that impacted US East. While the incident is now resolved, some services need a fresh redeploy (not just a restart) to fully re-establish the connection between the edge and your container. A restart reuses the existing container, but a redeploy creates a new one that re-registers with the routing layer. Go to your service's Deployments tab, click the three dots on the latest deployment, and select Redeploy.


Status changed to Awaiting User Response Railway about 1 month ago


largelanguagesolutions-debug
HOBBYOP

a month ago

That cleared it up. Thank you!


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Solved largelanguagesolutions-debug about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...