We are experiencing a critical production outage caused by Railway's internal variable references (${{ServiceName.VAR}}) failing to resolve between services in the same environment. Our services are configured to communicate using Railway's own recommended variable reference syntax, such as: - ${{PgBouncer.RAILWAYPRIVATEDOMAIN}} — referenced in the API service to reach PgBouncer - ${{DB-API-PRD.PGPASSWORD}} — referenced in PgBouncer to authenticate against PostgreSQL - ${{DB-API-PRD.PGUSER}} — same as above - ${{DB-API-PRD.RAILWAYPRIVATEDOMAIN}} — referenced in PgBouncer to reach the database host None of these references are resolving. The variables are being passed as literal strings or empty values to the containers, causing our entire infrastructure to fail at startup. This is not a misconfiguration on our end. These are standard Railway variable references following the exact syntax documented by Railway. The services are in the same project and environment. There were no changes to the service names or variable references. This issue started after a reported Railway infrastructure incident that forced us to redeploy our services. Since then, internal variable references have simply stopped working — something that was functioning correctly before and that we have no control over. The impact is severe: our production environment is completely down. We had to resort to hardcoding sensitive credentials directly into environment variables as a workaround, which is a security concern and something we should never have to do on a platform like Railway. We expect internal variable references to be a core, reliable feature of Railway. Having production go down because of a platform-level failure in variable resolution is unacceptable. We need this investigated and fixed urgently. Environment details: - Project: Golf Billions — User API PRD - Services affected: API, PgBouncer, DB-API-PRD - All services are in the same Railway environment

My managed Postgres service has been crash-looping for 3 days with catatonit: failed to exec pid1: No such file or directory. Volume: volti87dkxzgoysf8wo. The postgres-volume is mounted but the container fails to start. I need help restoring the service without data loss.

Hello, since the issue of being unable to access the platform because Google blocked it, I haven't been able to upload updates to this application. It was in sleep mode. Could you please help me upload updates? image.png

Description: Open Source Voice Agent Platform Category: AI/ML URL: https://railway.com/deploy/dograh

Seems like my app urls are not available when accessed. It shows online , and being properly deployed But not online

Description: Deploy and Host RustyRed-GraphDB with Railway Category: Other URL: https://railway.com/deploy/rustyred-graphdb

I just made my account and am trying to deploy my application, but am getting an error that says "Bad Credentials" under the Source section titled "Branch connected to production" I have logged into Railway with my GitHub and made sure that the Railway GitHub integration has access to the repo. It shows up when I create a new service to deploy from GitHub. But it fails to actually pull from the repo. It even is able to actually deploy! It just can't monitor for updates or see when I push a change to the repo. I have tried completely disconnecting my GitHub and deleting the Railway integration, then reconnecting, but that did not change anything. Can anyone please help me?

I keep having this error page when i try link my account to my discord : Error authenticating with Discord Problem completing OAuth login. I tried through the browser along with the app and no luck :( I seen that a similar question was asked a couple of months back and see that it was resolved but not sure why it's still happening to me?

Contact Railway support directly — Provide them with the deployment IDs (47a772aa-87de-45dd-8f09-f673109a89b0, 4a5b2124-24a2-4fa2-ae9c-777bfbe6299c) and mention the secret Service not found error. This is a known issue on their end. This is what the virtual agent gave me.

Hello Railway Team, I’m facing a critical issue with my Railway-hosted services and would appreciate your assistance. My user-id is Keshu92. Summary of the Problem None of my deployed services are reachable via their public Railway URLs. This issue is affecting multiple projects simultaneously, which suggests it is not application-specific. The services appear to start successfully, but then become unreachable, and containers sometimes restart. What I’m Observing Logs show: Server starts successfully (Server running on PORT) Database initialization completes Shortly after, the container stops or restarts No incoming requests are logged when accessing the public URL. DNS resolution for the Railway domains is working correctly. Even after regenerating domains and redeploying, the issue persists. Important Context (Billing) There was an unpaid invoice ($8.05) earlier. This invoice has now been successfully paid (Receipt available, dated April 19, 2026). The issue began around the time of the billing restriction and has continued even after payment. Troubleshooting Already Done Verified application code: Server binds to 0.0.0.0 Uses process.env.PORT No crashes or unhandled exceptions Ensured single process execution (no conflicting start scripts) Redeployed services multiple times Deleted and regenerated Railway domains Tested via incognito and cleared DNS cache Added health endpoint and request logging (no requests are reaching the app) Key Concern Since: All services are affected DNS works but routing does not Containers start but are not consistently reachable I suspect this may be related to: Account-level restrictions not fully lifted after payment Stale or broken routing/domain mappings Health check or service exposure issues at the platform level Request Could you please: 1. Verify if my account/services are fully restored after the invoice payment 2. Check if there are any routing, networking, or healthcheck issues affecting my deployments 3. Confirm whether my services are correctly exposed to public traffic 4. Advise if any manual intervention is required on my end This issue is blocking access to all my deployed applications, so any help would be greatly appreciated.