a year ago
So I just deployed a new static site. It's built using astro, but I don't think that much matters. I added some public networking <project>.up.railway.app (no custom domains or anything) and it looks like it put the project on the new "metal edge" network. I was testing everything from my computer and it seemed to work fine until I noticed a weird bug last night -- I couldn't load the site on mobile. This morning I did a bunch more digging and this issue seems to be isolated to the Chrome browser (version 133.0.6943.138) on mobile (android 15, pixel 6, build AP4A.250205002) over WiFi.
In other words, the site loaded fine on my phone over cellular data, and in a firefox browser over cellular and WiFi.
When I downgraded back to the "legacy network" (I forget the actual tooltip) that fixed things.
2 Replies
a year ago
Hey Clayton,
Thanks for reporting. This does line up with a latency spike which implies the metal edge was affected for that period. Before we move everyone over- we’ll polish it further. Thanks again for trying it out.
Best,
Angelo
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Hey Clayton- update from the team.
It didn't appear to be an issue with the edge network since that was only on the EU. It seems to be more likelier to be an issue with your mobile network and DNS.
7 months 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 • 7 months ago