Your custom domain novasaludpinedo.com.ar is currently resolving correctly to Railway, has a valid certificate, and is returning a 200 response with no fallback page. The CNAME is properly flattened by Cloudflare to the correct Railway IP, and edge routing is intact. The "train has not arrived" error appears to have cleared, so you should be able to confirm by visiting your domain now.

Hello,

Unfortunately, the issue is still happening.

I tested from both:

• Windows PC
• iPhone

The custom domain still shows the Railway fallback page:

“The train has not arrived at the station.”

Request ID:

mEh18DT8Ssm8vxMt9I3ezw

The Railway-generated domain works correctly.

Could you please investigate the edge routing using this Request ID?

Thank you.

Your service has CDN caching enabled, and a cached copy of the fallback page is likely being served at edge locations near you. The domain's DNS, certificate, and edge routing are all correct on our side, which is why the Railway-generated domain works fine.

To clear the stale cached response, go to your service's Settings, find the Edge section, and purge the CDN cache (purge "all"). The purge propagates across all edge locations within a few seconds, and the next request will fetch the live response from your service.

The issue is still present. I don’t have an Edge/CDN or “Purge Cache” option in my dashboard, so I can’t perform the purge you suggested. The Railway-generated domain works correctly, but the custom domain still returns “The train has not arrived at the station”. The current Request ID is: VTCyiKH1R1SnJ2rG6WHkDg. Could you please purge the cache or inspect the edge node serving this request?

Hi,

I still don’t have an Edge/CDN or “Purge Cache” option in my Railway dashboard, so I can’t perform the cache purge myself.

The Railway-generated domain works correctly, DNS is verified, SSL is valid, but the custom domain still returns “The train has not arrived at the station”.

Latest failing Request ID:

VTCyiKH1R1SnJ2rG6WHkDg

Could you please purge the stale cached fallback page or re-sync the custom-domain edge route for my domain?

Thank you.

Hello, just following up. The issue is still present and reproducible on multiple devices. If you need any additional information (logs, screenshots, project ID, service ID), I’m happy to provide it.

Remove the custom domain and re add after 10-15 mins. Update DNS records as necessary

Hey, please double check your service settings.

As team members have said, you have CDN enabled and may need to purge it.

Scroll down to your service settings until you see the "Edge" section.

AY5tW9HiRQaKynFvWUN5dQ

Hello,

I followed the recommended full reset procedure exactly:

• Removed the custom domain from Railway
• Deleted the CNAME and TXT records from Cloudflare
• Waited more than 10 minutes
• Added the custom domain again
• Added the new CNAME and TXT records
• Kept Cloudflare proxy disabled / DNS only
• Railway now shows the domain as verified with a green check

However, the custom domain still returns the Railway fallback page:

“The train has not arrived at the station.”

New Request ID:

AY5tW9HiRQaKynFvWUN5dQ

At this point the issue appears to require a Railway-side edge cache purge or route re-sync.

Could the Railway team please investigate this Request ID and re-sync the custom domain routing?

Thank you.

Hello,

I checked the Edge section in my service settings.

CDN Caching is currently disabled, so there is no CDN cache available for me to purge.

Under Attack Mode is also disabled.

The custom domain is verified with a green check, but it still returns the Railway fallback page.

Latest Request ID:

AY5tW9HiRQaKynFvWUN5dQ

Could you please check the Railway-side edge route and cache for this domain?

Thank you.

Good news: your domain is now serving your app correctly from every region we tested, including Buenos Aires, São Paulo, and Chile, on both the Cloudflare path and directly against Railway's edge. The earlier failures look like edge propagation catching up after the domain was removed and re-added. Each re-add restarts that propagation, which is why the problem seemed to persist through the resets.

Please flush your DNS cache (on Windows: ipconfig /flushdns, and restart your browser) and try again. If you still see the fallback page after that, send us the new Request ID and the time you tested, and we'll dig into that specific request.

Railway Team

Hello,

I followed your instructions exactly:

• Ran ipconfig /flushdns successfully on Windows
• Completely restarted Chrome
• Tested again in an incognito window

The Railway fallback page is still being returned.

Test time:

July 29, 2026 at 22:13 ART (UTC-3)

New Request ID:

xaFBBqKzTRmPqtxj2prcFg

Please investigate this specific request, as requested in your previous reply. The issue is still reproducible after flushing the DNS cache and restarting the browser.

Thank you.