15 days ago
My custom domain myremindme.app appears to be stuck on a stale Railway service/domain binding after the May 2026 Railway / Google Cloud outage.
Current DNS/CNAME shows:
myremindme.app -> 8eaueqv1.up.railway.app
But my healthy current Railway app is:
https://myremindme-production.up.railway.app
Current project:
14b45356-8c03-476b-a7bb-34cce22aae93
Current service:
d621fc38-8763-49fa-87e7-d40786e9ddc1
The healthy service returns 200 from /healthz and is working correctly.
The problem is that myremindme.app still appears bound to the stale Railway domain/service. The Railway dashboard says the domain is unavailable, and I cannot release or reassign it through the UI or CLI.
Can Railway staff please release the stale myremindme.app binding from 8eaueqv1.up.railway.app so I can attach it to my current active service?
Once released, I will reattach myremindme.app to the current service and set PUBLIC_URL back to https://myremindme.app.
6 Replies
15 days ago
We can remove the domain for you, but we need to verify ownership first. Please add a TXT record at _railway.verify.myremindme.app with the value k7xm3qw2, then let us know once it has propagated.
Status changed to Awaiting User Response Railway • 15 days ago
15 days ago
The TXT verification record has propagated:
_railway.verify.myremindme.app TXT "k7xm3qw2"
Please release the stale myremindme.app binding from 8eaueqv1.up.railway.app so I can attach it to my current Railway service:
Project ID: 14b45356-8c03-476b-a7bb-34cce22aae93
Service ID: d621fc38-8763-49fa-87e7-d40786e9ddc1
Status changed to Awaiting Railway Response Railway • 15 days ago
14 days ago
Thanks for adding the TXT record.
We have the verification value on the thread:
_railway.verify.myremindme.app -> k7xm3qw2
The requested action is to release the stale myremindme.app binding currently pointing at 8eaueqv1.up.railway.app so you can attach it to service d621fc38-8763-49fa-87e7-d40786e9ddc1 in project 14b45356-8c03-476b-a7bb-34cce22aae93.
This needs staff-side domain cleanup. We will verify the TXT record and follow up once the stale binding has been released or if the record does not match what we need.
Status changed to Awaiting User Response Railway • 14 days ago
10 days ago
Hi Angelo, checking in on this.
The TXT record is still live and propagated:
_railway.verify.myremindme.app TXT "k7xm3qw2"
As of now, myremindme.app still resolves to the stale Railway target:
8eaueqv1.up.railway.app
The current healthy service remains:
myremindme-production.up.railway.app
Please let me know once the stale binding has been released so I can attach myremindme.app to service d621fc38-8763-49fa-87e7-d40786e9ddc1.
Status changed to Awaiting Railway Response Railway • 10 days ago
Status changed to Awaiting User Response Railway • 8 days ago
5 days ago
thank you, i hope your stuff doesnt go down again that was brutal, had lost the old one and the new one wasnt being used, issues when installing as an app not knowing which one was running etc
Status changed to Awaiting Railway Response Railway • 5 days ago
Status changed to Solved Railway • 5 days ago