Project ID: 045d99d7-7067-4845-943d-fafcbe4b4325

Service: api

Issue: Custom domain won't persist in service networking config

Timeline: Started today after environment variables disappeared

Env vars and domains are both attached to the service/environment record - they don't disappear independently. If 20+ variables and your domain vanished together, the service or environment itself was deleted or recreated at some point in that month. That also explains the domain: .up.railway.app names are globally unique, so when the old service record was released, the name became claimable by anyone - "not available" means it's now taken or reserved. Only Railway staff can check/release that, so Awaiting Railway Response is the right status.

Things you can do right now:

1. Open your project's Activity feed in the dashboard - it shows every change with a timestamp and who/what did it (user, token, or automation). This tells you exactly what happened and when.

2. Check the environment dropdown - make sure you're not just looking at a different/new environment than the one that had your variables.

3. Check Account Settings -> Tokens and your team members list. If a token leaked, something may have run destructive API calls - rotate all tokens regardless.

4. If the deletion was recent: Railway has a 48-hour grace period for deletions (workspace settings -> deleted projects). Past that window, staff intervention is the only path.

5. Check your repo for railway.json / railway.toml or CI that syncs config - a bad sync can recreate a service with empty config.

Going forward: railway variables --json > backup.json before walking away from a project.