2 months ago
Today, we started getting reports of users not being able to load our app. We had not made any changes to our DNS settings prior to this.
The only thing that fixed it was to change the custom domain CNAME from what is stated in the networking [random-characters].up.railway.app , to the [product].up.railway.app
I'm not sure what's going on.
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey,
Everything should be back to normal, here is a quick summary of what happened.
We were migrating a subset of custom domains to a new Edge network ahead of an upcoming Fastly configuration change. The new Fastly config will temporarily enforce a 180-second request limit until their engineering team increases that threshold, so we proactively moved domains that require longer-lived connections.
During that process, your domain was entered without the fully qualified domain name (FQDN), which caused the SERVFAIL you observed.
We've corrected the entries and updated our tooling to handle both formats going forward.
Apologies for the disruption.
Status changed to Awaiting User Response Railway • about 2 months ago
2 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 • about 2 months ago