Root Cause: DNS/Network Edge Issue
priteshnakra
FREEOP

14 days ago

I need help downgrading to the GCP network.

I spoke with the railway agent, and I got this feedback. I would really love some help as soon as possible:

The problem is NOT your application code. Both services are running perfectly. The issue is that requests are not reaching your services at all — no HTTP logs, no traffic.

This is almost certainly caused by the Railway's Metal Edge network issue from the May 6 EU West outage. Your services may be stuck on the Metal Edge network, which has had DNS propagation failures.

How to Fix It

  1. Go to your AIMFI (Frontend) service settings
  2. Navigate to: Settings → Public Networking
  3. Look for "Metal Edge" or "Network" option
  4. Downgrade to GCP network (or click any "Downgrade" button if available)
  5. Redeploy the service

Then do the same for your AIFMI (Backend) service.

I need help with downgrading to the GCP network; for some reason, I do not have the option to downgrade manually.

Please let me know if anyone can help!

$10 Bounty

6 Replies

Status changed to Awaiting Railway Response Railway 14 days ago


Status changed to Open Railway 14 days ago


Make sure the port your application is listening to is the same as the port the URL is mapped to.


0x5b62656e5d

Make sure the port your application is listening to is the same as the port the URL is mapped to.

priteshnakra
FREEOP

14 days ago

Both services have matching ports, I ran a diagnosis to make sure it does as well. That's not the issue. The real problem is still the Metal Edge network DNS issue, do let me know if you could help me with that!


What error do you encounter when trying to visit the site then? (The so-called “downgrade” doesn’t exist btw…)


0x5b62656e5d

What error do you encounter when trying to visit the site then? (The so-called “downgrade” doesn’t exist btw…)

priteshnakra
FREEOP

14 days ago

Oh my bad! It simply says that the site can't be reached. I've been speaking to Trailway Agents trying to figure this out. Any help on this would be really amazing!


priteshnakra

Oh my bad! It simply says that the site can't be reached. I've been speaking to Trailway Agents trying to figure this out. Any help on this would be really amazing!

I’ve let the team know about the agent’s response.

Also, have you tried clearing your local DNS cache?


0x5b62656e5d

I’ve let the team know about the agent’s response. Also, have you tried clearing your local DNS cache?

priteshnakra
FREEOP

14 days ago

Yes I did flush my DNS Cache, The domain resolves via Google DNS (8.8.8.8) to 66.33.22.243 but curl still cannot resolve the host locally. This has been going on for 20+ minutes.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...