14 days ago
Hello, I need help with a stale Railway custom domain mapping.
I previously used a subdomain on Railway, then removed it and pointed DNS to Vercel.
Public DNS now resolves to the Vercel target correctly, but requests to the domain are still being answered by Railway with:
server: railway-hikari
x-railway-fallback: true
404 Not Found
It seems Railway edge is still catching the hostname even though DNS no longer points to Railway.
Can someone from the Railway team help check whether this domain is still reserved, cached, or attached somewhere on the Railway side, and clear the stale mapping?
Thank you.
8 Replies
14 days ago
We can help get that stale domain mapping cleared. Could you share the exact domain (or subdomain) you need removed? Once we have it, we'll run a quick TXT-record ownership verification and then remove it for you.
Status changed to Awaiting User Response Railway • 14 days ago
Railway
We can help get that stale domain mapping cleared. Could you share the exact domain (or subdomain) you need removed? Once we have it, we'll run a quick TXT-record ownership verification and then remove it for you.
13 days ago
Status changed to Awaiting Railway Response Railway • 13 days ago
Status changed to Awaiting User Response Railway • 13 days ago
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
We don't see harkai.beyondaigen.com attached to any Railway project, so there is no stale mapping on our side to remove. The domain is currently resolving to Vercel and returning a 200 with a valid certificate. If you were previously seeing x-railway-fallback headers, that has since cleared, and you should be all set.
Status changed to Awaiting User Response Railway • 13 days ago
Railway
We don't see `harkai.beyondaigen.com` attached to any Railway project, so there is no stale mapping on our side to remove. The domain is currently resolving to Vercel and returning a 200 with a valid certificate. If you were previously seeing `x-railway-fallback` headers, that has since cleared, and you should be all set.
13 days ago
I can still see this Not Found
The train has not arrived at the station.
Please check your network settings to confirm that your domain has provisioned.
If you are a visitor, please let the owner know you're stuck at the station.
Request ID:
99q_Pw2GReijy1ThV7rehQ
Status changed to Awaiting Railway Response Railway • 13 days ago
Status changed to Awaiting User Response Railway • 13 days ago
Railway
We don't see `harkai.beyondaigen.com` attached to any Railway project, so there is no stale mapping on our side to remove. The domain is currently resolving to Vercel and returning a 200 with a valid certificate. If you were previously seeing `x-railway-fallback` headers, that has since cleared, and you should be all set.
13 days ago
My Local call PS C:\Users\vsb> curl.exe -k -I https://harkai.beyondaigen.com
HTTP/1.1 404 Not Found
Cache-Control: public, max-age=5
Content-Type: application/json
Server: railway-hikari
x-railway-fallback: true
x-railway-request-id: m_TEEQfeR2-jvYkHacI7Nw
Content-Length: 101
Date: Mon, 13 Jul 2026 13:40:46 GMT
x-hikari-trace: sin1.98a6
x-railway-edge: sin1
Connection: keep-alive
PS C:\Users\vsb>
Status changed to Awaiting Railway Response Railway • 13 days ago
Status changed to Awaiting User Response Railway • 13 days ago
13 days ago
Still same check PS C:\Users\vsb> curl.exe -k -I https://harkai.beyondaigen.com
HTTP/1.1 404 Not Found
Cache-Control: public, max-age=5
Content-Type: application/json
Server: railway-hikari
x-railway-fallback: true
x-railway-request-id: m_TEEQfeR2-jvYkHacI7Nw
Content-Length: 101
Date: Mon, 13 Jul 2026 13:40:46 GMT
x-hikari-trace: sin1.98a6
x-railway-edge: sin1
Connection: keep-alive
PS C:\Users\vsb>
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 13 days ago
13 days ago
This could just be DNS cache. I can access your site just fine.
➜ curl -I https://harkai.beyondaigen.com/
HTTP/2 200
accept-ranges: bytes
access-control-allow-origin: *
age: 10453
cache-control: public, max-age=0, must-revalidate
content-disposition: inline
content-type: text/html; charset=utf-8
date: Mon, 13 Jul 2026 14:42:13 GMT
etag: "6ed6caca123ca7d8539b28295ada4dbf"
server: Vercel
strict-transport-security: max-age=63072000
vary: RSC, Next-Router-State-Tree, Next-Router-Prefetch
x-matched-path: /
x-vercel-cache: HIT
x-vercel-id: hkg1::pmhlm-1783953733720-cfc4cfa53200
content-length: 19270
Attachments