Problem and desired outcome

We previously hosted a service on Railway and pointed a custom domain, jobsearch.besttopcareer.com, at it. We have since deleted that Railway project entirely and migrated the site to GitHub Pages (https://besttopeducationtechlc.github.io/JobSpy/). We expected that once the Railway project was deleted, the custom domain would be free to repoint, or that removing the domain from Railway's settings would release it. Instead, jobsearch.besttopcareer.com still redirects to Railway instead of reaching the GitHub Pages site. This is an ongoing, current problem — it is happening right now, not a one-time past event. We want Railway to fully release/detach this domain from its systems so we can point it at GitHub Pages instead, and we'd like to understand why the domain link persisted after the owning project was deleted.

Resources and timing

Request ID (support form submission reference): wwJi13sfTyWcW9TI7fhULg

Affected custom domain: jobsearch.besttopcareer.com

Intended destination: GitHub Pages site at https://besttopeducationtechlc.github.io/JobSpy/

Railway project/service: no longer identifiable — the project has already been deleted, and we do not have its project ID, service ID, or workspace name on hand.

We do not have an exact timestamp for when the project was deleted or when the domain was first noticed to still be redirecting; this is an ongoing state we observed during the current session (October 2026).

Evidence and attempts

We attempted to remove the custom domain from within the Railway dashboard's domain settings. The domain removal did not resolve the issue — jobsearch.besttopcareer.com continues to redirect to Railway rather than reaching GitHub Pages.

We have not yet changed DNS records at our registrar/DNS provider, since the expectation was that detaching the domain in Railway (or deleting the project outright) would be sufficient on Railway's side.

No specific error message or log output is available from Railway's side for this case — the observed behavior is a redirect away from the intended destination rather than an explicit error screen.

Why contact support?

The AI assistant (Claude) recommended contacting Railway support after the user reported this issue directly. The concrete blocker: this is a DNS/domain-binding state held on Railway's infrastructure, tied to a project that the user has already deleted through normal means available to them. Removing the domain from the Railway dashboard did not release it, and there is no remaining Railway project or service for the user to act on further — the assistant has no tool or API access to Railway's account/infrastructure to diagnose or clear this binding. We are asking Railway to check why the domain remains linked/redirected despite the owning project's deletion and the dashboard-level domain removal, and to fully release the domain so it can be pointed elsewhere.

Uncertainty and constraints

Observed fact: the domain currently redirects to Railway instead of resolving to the GitHub Pages site.

Observed fact: the user removed the custom domain via the Railway dashboard, and the redirect persisted afterward.

Hypothesis (not confirmed): Railway may retain a domain-routing/edge record independently of the project or domain-settings deletion, which would require Railway-side cleanup rather than any user-facing action.

We have not ruled out a DNS propagation delay, but the user has not yet changed any DNS records at the registrar, so propagation delay is not yet a relevant factor from our side.

No data-loss or downtime constraints apply here — the underlying Railway project is already deleted and no data recovery is being requested. We are only asking Railway to check/clear the domain's routing state; we are not asking Railway to modify our GitHub Pages site or any external DNS records.

Prepared with Railway's support template (v1).