10 days ago
Requests to gyaf9o8m.up.railway.app (69.46.46.57) from multiple Australian fixed-line networks complete TCP but time out during TLS. The identical request, forced to the same IPv4 address and SNI, succeeds over a mobile hotspot with HTTP 404. My home route traverses TPG/AAPT and Vocus. Please investigate Hikari Edge peering, return routing, and PMTU toward these networks.
25 Replies
10 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 10 days ago
mayori
Try change your DNS to `1.1.1.1`
10 days ago
Tried that and also 8.8.8.8 .
Neither of them worked.
10 days ago
Have you tried using a VPN to access the sites? Also, you won't be able to access the sites from gyaf9o8m.up.railway.app directly. You'd need to use the custom domain you've added to the service.
10 days ago
Hi team, we're experiencing the same on all our Singapore servers. From all Australian fixed-line networks. NZ works fine. Project: 3e218ec0-7c31-4a5e-ba63-d0f7439aa07d Service 5f590b6d-e94b-4033-80a1-25d34e6ddea4
nickm
Hi team, we're experiencing the same on all our Singapore servers. From all Australian fixed-line networks. NZ works fine. Project: 3e218ec0-7c31-4a5e-ba63-d0f7439aa07d Service 5f590b6d-e94b-4033-80a1-25d34e6ddea4
10 days ago
Multiple users around Australia. With/without VPN. Was working yesterday. Impacting all of our services.
nickm
Multiple users around Australia. With/without VPN. Was working yesterday. Impacting all of our services.
10 days ago
Could you share some URL(s) that were affected?
10 days ago
I'm able to access it just fine. Seeing that you're an Enterprise user, have you raised this through the Enterprise channels yet?
10 days ago
So am I. I'm in New Zealand. Only impacts fixed-line from Sydney/Melbourne fixed line
0x5b62656e5d
I'm able to access it just fine. Seeing that you're an Enterprise user, have you raised this through the Enterprise channels yet?
10 days ago
No – i'm jumping on the issue right now and saw this so wanted to corroborate. I haven't done a help ticket in a while! Happy to. Shall I do within Discord?
nickm
No – i'm jumping on the issue right now and saw this so wanted to corroborate. I haven't done a help ticket in a while! Happy to. Shall I do within Discord?
10 days ago
No, it's alright. I'll check with the team internally.
(Also, the help channel in Discord has been archived. Support for non-Enterprise users should go through Central Station.)
10 days ago
Champion, thank you. I'm available if you need any more information. On Discord or publicly here
10 days ago
(Btw, as an Enterprise user, tickets should be created via Slack)
(I've also been told by a Team member that it's best if you could create your own ticket in Slack as well)
0x5b62656e5d
Have you tried using a VPN to access the sites? Also, you won't be able to access the sites from `gyaf9o8m.up.railway.app` directly. You'd need to use the custom domain you've added to the service.
9 days ago
I tried VPN.
I have two different network providers for home and work.
And home one was the first to experience this , so I vpn to works network .
And today the works network also is effected by the same issue.
Only thing not effected is the 5G Mobile which I am using as hotspot for debugging.
delphi-17
I tried VPN. I have two different network providers for home and work. And home one was the first to experience this , so I vpn to works network . And today the works network also is effected by the same issue. Only thing not effected is the 5G Mobile which I am using as hotspot for debugging.
9 days ago
Hi delphi-17, I can't find any other information on this issue. But now this station.railway.com is failing also from Melbourne. Here's an update from Railway support to help you and any others experiencing this:
Brody (11:39am AEST): I am waiting for a response from the network engineer on call, but the networking issue itself would be with our external providers, since this is in regards to the CDN edge network, and we were told this region had issues and was fixed many hours ago, so this may be something that has an extended timeframe.
Me (12:48pm AEST): Hi Brody, any updates your end please? These environments are customer-facing environments so we’re down for them, and demo environments for our sales team
Brody (1:05pm AEST): Apologies, no response yet, and we are not seeing mass reports, so this falls outside of what we would page for. ... It's midday for them, but we have no set work hours, so I really can't say when they will be on. My deepest apologies that I cannot give you more information here.
9 days ago
Another update. From our team in Melbourne, https://station.railway.com and https://railway.com is also down
9 days ago
Just to add, this is from multiple offices. Our team, and also our customers from different cities in Australia, are experiencing it too
9 days ago
Hi Nick,
I am able to temporarily fix it by proxying my domain with my DNS server.
Basically using proxy as my “VPN”.
But if your domain dns server is also in Australia and also has issue with connecting to Railway.
Then the proxy also won’t help.
But yeah I am able to have our domain working for now by using proxy.
Hope that helps .
9 days ago
We've spun up a test service in Amsterdam, US East, and still the same behaviour
9 days ago
We have a plan to fix root cause but have updated with a temporary fix. Can you confirm the behaviour is ok for now?
Status changed to Awaiting User Response Railway • 9 days ago
dizzydes90
We have a plan to fix root cause but have updated with a temporary fix. Can you confirm the behaviour is ok for now?
9 days ago
Thank you for the update .
My work network is able to connect to railway now.
Home network which is with Optus is still unable to connect.
So it’s partially fixed .
Hopefully you guys can fix the root cause soon.
Status changed to Awaiting Railway Response Railway • 9 days ago
9 days ago
Thanks for confirming. Noted that the temporary fix restored connectivity on your work network but Optus is still affected. The root cause fix our colleague mentioned is still being worked on, which should address the remaining networks.
Status changed to Awaiting User Response Railway • 9 days ago
9 days ago
Thanks @noahd. We seem to be up and running now after your fix, look forward to updates on the root cause
Status changed to Awaiting Railway Response Railway • 9 days ago
Status changed to Awaiting User Response noahd • 9 days ago
Status changed to Awaiting Railway Response Railway • 8 days ago
Status changed to Solved delphi-17 • 8 days ago

