Production service is unreachable through its public Railway domain after the US West connectivity incident was marked resolved. Project/service: Arkitex-ren-bogholder Environment: production Deployment ID: 3cc76012 Domain: https://arkitex-ren-bogholder-production.up.railway.app Region shown in Railway: US East Replica count: 1 Railway shows deployment 3cc76012 as Active. Deploy logs show: - F35_BOOTSTRAP_HEALTH_BOUND host=0.0.0.0 port=8080 - F35_APPLICATION_IMPORT_COMPLETE application_ready=true - Uvicorn running on 0.0.0.0:8080 - Earlier GET /health and GET /kontrolpanel/ejer returned HTTP 200. Current external checks after Railway status returned to Fully Operational: - GET /health: timeout after 20 seconds, zero bytes, HTTP 000 - GET /kontrolpanel/ejer: timeout after 20 seconds, zero bytes, HTTP 000 - The owner also cannot open the domain from their PC. We have deliberately not restarted or redeployed the service to preserve evidence and state. Please investigate public routing/domain reachability for this deployment and advise whether an edge route or service networking recovery action is required.

Production domain times out although deployment is Active

arkitex-platform

PROOP

4 hours ago

Production service is unreachable through its public Railway domain after the US West connectivity incident was marked resolved.

Project/service: Arkitex-ren-bogholder

Environment: production

Deployment ID: 3cc76012

Domain: https://arkitex-ren-bogholder-production.up.railway.app

Region shown in Railway: US East

Replica count: 1

Railway shows deployment 3cc76012 as Active. Deploy logs show:

F35_BOOTSTRAP_HEALTH_BOUND host=0.0.0.0 port=8080
F35_APPLICATION_IMPORT_COMPLETE application_ready=true
Uvicorn running on 0.0.0.0:8080
Earlier GET /health and GET /kontrolpanel/ejer returned HTTP 200.

Current external checks after Railway status returned to Fully Operational:

GET /health: timeout after 20 seconds, zero bytes, HTTP 000
GET /kontrolpanel/ejer: timeout after 20 seconds, zero bytes, HTTP 000
The owner also cannot open the domain from their PC.

We have deliberately not restarted or redeployed the service to preserve evidence and state. Please investigate public routing/domain reachability for this deployment and advise whether an edge route or service networking recovery action is required.

$20 Bounty

2 Replies

Railway

BOT

4 hours ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 4 hours ago

0x5b62656e5d

MODERATOR

4 hours ago

I’d try redeploying the service.

manuproject

HOBBYTop 5% Contributor

3 hours ago

one thing you can also try without touching your deployment or losing state

delete and re-add just the domain (not the service), that sometimes forces railway to re-register a fresh route.

Welcome!