Hi Railway Support Team, We are currently facing a region-specific connectivity issue with our elogbackends service hosted on Railway. The backend works fine from India and Australia regions, however users from New Zealand are unable to access the service consistently. Backend URL: https://elogbackends-production.up.railway.app Issues observed from NZ region: - Browser shows connection/network failures while accessing backend APIs - Direct backend API access fails from browser - Curl requests from terminal also fail with SSL/TLS handshake errors Example curl error: curl: (35) schannel: failed to receive handshake, SSL/TLS connection failed We have attached screenshots/logs showing: - Browser network failures - ERR_CONNECTION_CLOSED issues - SSL/TLS handshake failure from curl requests ![image (2).png](https://station-server.railway.com/attachments/att_01ks4g6ahmfvhb506x3m3x9cw6) ![image (3).png](https://station-server.railway.com/attachments/att_01ks4g6fvgfvhrcz3v8mqjcggp) ![image (4).png](https://station-server.railway.com/attachments/att_01ks4g6qajfzya56j7xj8q4p5f) ![image (5).png](https://station-server.railway.com/attachments/att_01ks4g6zahfzsbc043hgas3jt6) Could you please investigate whether there are any networking, CDN, SSL, edge routing, or region-specific issues affecting access from New Zealand regions? Please let us know if you need any additional logs or diagnostics from our side. Thanks.

Unable to Access eLogbook backend in NZ Region , Other region works fine

sachinrohit-vtech

PROOP

25 days ago

Hi Railway Support Team,

We are currently facing a region-specific connectivity issue with our elogbackends service hosted on Railway.

The backend works fine from India and Australia regions, however users from New Zealand are unable to access the service consistently.

Backend URL:

https://elogbackends-production.up.railway.app

Issues observed from NZ region:

Browser shows connection/network failures while accessing backend APIs
Direct backend API access fails from browser
Curl requests from terminal also fail with SSL/TLS handshake errors

Example curl error:

curl: (35) schannel: failed to receive handshake, SSL/TLS connection failed

We have attached screenshots/logs showing:

Browser network failures
ERR_CONNECTION_CLOSED issues
SSL/TLS handshake failure from curl requests

image (2).png

image (3).png

image (4).png

image (5).png

Could you please investigate whether there are any networking, CDN, SSL, edge routing, or region-specific issues affecting access from New Zealand regions?

Please let us know if you need any additional logs or diagnostics from our side.

Thanks.

Attachments

Solved$20 Bounty

Pinned Solution

0x5b62656e5d

MODERATOR

25 days ago

By configuring the DNS resolver, I meant configuring the client's machine to resolve DNS queries from 1.1.1.1.

Attachments

45487.png

8 Replies

Railway

BOT

25 days ago

Your elogbackends service is deployed and healthy, and the domain resolves correctly to our anycast IP range. Since the issue is isolated to New Zealand while working from India and Australia, we need network path data from the affected region to investigate further. Please have a user in NZ download and run our Network Diagnostics tool and share the output here so we can trace where the connection is failing.

Status changed to Awaiting User Response Railway • 25 days ago

Railway

Your elogbackends service is deployed and healthy, and the domain resolves correctly to our anycast IP range. Since the issue is isolated to New Zealand while working from India and Australia, we need network path data from the affected region to investigate further. Please have a user in NZ download and run our [Network Diagnostics tool](https://docs.railway.com/networking/troubleshooting/network-diagnostics) and share the output here so we can trace where the connection is failing.

sachinrohit-vtech

PROOP

25 days ago

Hello Railway Support Team,

Please find attached the network diagnostic logs and WiFi/network details from the affected New Zealand region for investigation.

image (6).png

Kindly review the attached outputs and let us know if any additional information, tests, or logs are required from our side.

Thanks.

Attachments

nz-network-...

image%20(6)...

Status changed to Awaiting Railway Response Railway • 25 days ago

Railway

BOT

25 days ago

Thanks for the details. The screenshot shows your WiFi network settings, but we need the output from our dedicated Network Diagnostics tool instead. Please download it for macOS or Windows, run it from the affected NZ network, and share the output here so we can trace where the connection is failing.

Status changed to Awaiting User Response Railway • 25 days ago

sachinrohit-vtech

PROOP

25 days ago

Hello Railway Support team,

We have already shared the network diagnostic logs earlier as a text file, but it seems the attachment may not have been visible from your side.

So we are sharing the logs again below as screenshots/images for easier reference.

Please find the attached network diagnostic logs from the affected NZ network.

Please let us know if any more details are needed from our side

Thanks.

Attachments

image.png

Status changed to Awaiting Railway Response Railway • 25 days ago

Railway

BOT

25 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway • 25 days ago

0x5b62656e5d

MODERATOR

25 days ago

Seems like this is a network/ISP issue for those in NZ. Try having them access the site with their DNS resolver set to 1.1.1.1.

sachinrohit-vtech

PROOP

25 days ago

Hello Railway Support Team,

Thanks for the update.

To clarify, we are currently using only the Railway-provided domain and have not configured any custom DNS from our side.

The application is accessible successfully from India, Australia, and external services like ReqBin. The issue appears only for users in New Zealand browsers/terminal environments.

This suggests the issue may be related to NZ ISP routing, Railway edge routing, or IPv6 connectivity rather than application-level configuration.

We are additionally testing:

Different NZ ISPs/networks
VPN access
IPv6 disablement

Please let us know if there are any known IPv6 or NZ regional routing issues currently affecting Railway-managed domains.

Thanks.

sachinrohit-vtech

Hello Railway Support Team, Thanks for the update. To clarify, we are currently using only the Railway-provided domain and have not configured any custom DNS from our side. The application is accessible successfully from India, Australia, and external services like ReqBin. The issue appears only for users in New Zealand browsers/terminal environments. This suggests the issue may be related to NZ ISP routing, Railway edge routing, or IPv6 connectivity rather than application-level configuration. We are additionally testing: - Different NZ ISPs/networks - VPN access - IPv6 disablement Please let us know if there are any known IPv6 or NZ regional routing issues currently affecting Railway-managed domains. Thanks.

0x5b62656e5d

MODERATOR

25 days ago

By configuring the DNS resolver, I meant configuring the client's machine to resolve DNS queries from 1.1.1.1.

Attachments

45487.png

0x5b62656e5d

By configuring the DNS resolver, I meant configuring the client's machine to resolve DNS queries from `1.1.1.1`. ![45487.png](https://station-server.railway.com/attachments/att_01ks4npt61f23azpz9j33ryrsh)

sachinrohit-vtech

PROOP

24 days ago

Thank you for the suggestion. After configuring the client machine to use the 1.1.1.1 DNS resolver, the app is now working properly in the NZ region.

Status changed to Solved 0x5b62656e5d • 24 days ago

Welcome!