Account: santiagobustamante

Original project (already deleted by me, to test whether the problem was project-specific): glorious-contentment (8ed6b26f-a3f6-481d-9f58-0c9c86032270)

Current project: renewed-enchantment (59919120-acee-4de3-956b-67b6cfd4de6a)

Hello,

I'm VERY frustrated with this situation and need a clear answer.

I upgraded my account to the Hobby plan (monthly payment) specifically because the free plan wouldn't let me provision the 10 services my project needs — in other words, I paid on purpose to be able to do this deployment. Since then, every public domain I generate (*.up.railway.app) returns "502 Application failed to respond" without exception, and I haven't gotten a SINGLE endpoint working since I paid.

This started coinciding with the incident you reported yourselves on the status page ("Intermittent connectivity issues affecting Outbound Static IPs in US East", 18:03–18:51 UTC). The problem is the status page has shown everything as "Fully Operational" for a while now, and I still have absolutely nothing working.

Here's everything I already tried, with evidence, before writing to you — this isn't a "did you try turning it off and on again":

Container logs: clean startup, no errors, the app does come up successfully ("Nest application successfully started" or equivalent).

Explicit binding to 0.0.0.0: instead of the default — same result.

Three different regions: us-east1, us-west1, europe-west4 — same 502 in all three.

Restarted the service after the status page moved back to "Fully Operational" — still 502.

Deployed a minimal test Node server (no NestJS, no multi-stage build, just http.createServer listening on 0.0.0.0:3000) — the EXACT SAME 502. This rules out it being an issue with my application.

Deleted the entire service and recreated it from scratch, with a new domain — same 502.

Deleted the ENTIRE PROJECT and created a new one from scratch (renewed-enchantment) — still the exact same 502 across all services.

The error pattern is always the same: ~31-32 seconds of timeout before the 502 (confirmed with railway logs --http), not an instant rejection — meaning this isn't even a port-configuration issue, it's the edge→container path that never responds at all.

With a BRAND-NEW project, on an account that's already on a paid plan, and with evidence that the bug persists even with a minimal app with no logic of my own, I have no doubt left that this is a Railway infrastructure issue tied to my specific account, not something I can fix on my end.

I need two specific things from you:

Are you going to look into my account specifically and tell me what's going on, or do I have to keep guessing?

If this can't be resolved in the next few hours, I want to request a refund of the Hobby plan charge — I paid for a service I wasn't able to use even once since activating it.

Looking forward to your response.