Skip to content
Generated url cannot be reached
ab2850
OP

15 days ago

Deployment status is success and running also online for an hour now but the generated url is not working saying site cannot be reached.

Solved

7 Replies

15 days ago

We're continuing to work on the external network blocks described on the incident page. Please follow that page for further updates.


Status changed to Awaiting User Response Railway • 15 days ago


playpalsuk

15 days ago

Any update almost been 24 hours and downtime causing major disruptions for my project


Status changed to Awaiting Railway Response Railway • 15 days ago


sam-a
EMPLOYEE

15 days ago

I’m sorry for the continued disruption. Our network team reports that the affected HTTP edge has now moved to a new IP range to mitigate the external network blocks.

Could you retry your application using a fresh DNS lookup and let us know whether it is reachable now? If it still fails, please share the affected application URL, your network provider and country, and the UTC time of the failed attempt. Please omit any private URL tokens or credentials.

We’re continuing to track access on affected networks through the incident page.


Status changed to Awaiting User Response Railway • 15 days ago


sam-a

I’m sorry for the continued disruption. Our network team reports that the affected HTTP edge has now moved to a new IP range to mitigate the external network blocks. Could you retry your application using a fresh DNS lookup and let us know whether it is reachable now? If it still fails, please share the affected application URL, your network provider and country, and the UTC time of the failed attempt. Please omit any private URL tokens or credentials. We’re continuing to track access on affected networks through the [incident page](https://status.railway.com/incident/QBCLHG1V).

playpalsuk

14 days ago

Hi,

I've now repeated the DNS tests following Railway's latest infrastructure update.

Unfortunately, the issue remains unresolved.

Both Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) return SERVFAIL for playpals.world.

Cloudflare's diagnostic specifically reports:

162.159.25.42:53 returned SERVFAIL for playpals.world A

Google DNS also reports SERVFAIL from both of your authoritative nameservers:

  • 162.159.24.201
  • 162.159.25.42

This suggests the failure is occurring when public DNS resolvers query Hostinger's authoritative nameservers, before the request reaches Railway's HTTP edge.

Please escalate this to your DNS engineering team and investigate:

  1. Why both authoritative nameservers return SERVFAIL for the root A record.
  2. Whether the root ALIAS record is resolving correctly.
  3. Whether the .world registry DS record is consistent with the domain's DNSSEC configuration.
  4. Whether there is an issue with the authoritative DNS zone or delegation.

Railway has already moved its HTTP edge to a new IP range, but this has not changed the DNS resolution results.

Please investigate the authoritative DNS issue rather than treating this solely as a Railway firewall block.

I do not authorise a DNS zone reset or changes to my email records.


Status changed to Awaiting Railway Response Railway • 14 days ago


sam-a
EMPLOYEE

14 days ago

We tested your domain just now from our side: it resolved and your app answered over HTTPS through our edge, with a valid certificate.

The authoritative nameservers for the domain belong to your DNS provider, not to us, so we have no access to that zone, its ALIAS record, or its DNSSEC/DS configuration. SERVFAIL answers from those nameservers, or a DS record that doesn't match the zone's signing keys, need to be checked with your DNS provider and registrar. We haven't made any changes to your DNS or email records, and we can't.

If the domain resolves for you but still can't be reached, that fits the external network blocks still affecting some networks. Trying from another network, such as mobile data, is the quickest way to tell the two apart.


Status changed to Awaiting User Response Railway • 14 days ago


sam-a

I’m sorry for the continued disruption. Our network team reports that the affected HTTP edge has now moved to a new IP range to mitigate the external network blocks. Could you retry your application using a fresh DNS lookup and let us know whether it is reachable now? If it still fails, please share the affected application URL, your network provider and country, and the UTC time of the failed attempt. Please omit any private URL tokens or credentials. We’re continuing to track access on affected networks through the [incident page](https://status.railway.com/incident/QBCLHG1V).

Anonymous

14 days ago

both of my applications are unreachable. Are yuo still working on a fix for this?


Status changed to Awaiting Railway Response Railway • 14 days ago


14 days ago

Yes, the external network blocks are still being worked on. Access has been restored on some networks, but it remains affected on others, and we don't have an estimated time for every affected network to lift its blocks.

If your apps fail to load from your current connection but load from another network, such as mobile data, that points to these blocks. Sharing the incident notice with your network administrator or provider lets them review any blocks on Railway IP addresses and allow access to your apps.


Status changed to Awaiting User Response Railway • 14 days ago


Railway
BOT

6 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 6 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...