Railway
Day 8 after signup
Urgent: Railway Security Disclosure - Rotate Credentials
Why it works
- Lead with a direct disclosure of the incident so recipients quickly understand why the message matters.
- Follow the explanation with concrete security steps, making the most urgent action easy to find.
- Close with service impact and a clear way to follow ongoing updates.
How it is built
- Incident disclosure
- Scope and context
- Credential rotation steps
- Service availability note
Email copy
Earlier this morning, Railway detected anomalous activity involving systems that store customer environment variables. After further investigation, our investigation to date indicates that an unauthorized third party may have accessed encrypted environment variables and, for some of them, obtained the decrypted contents. Environment variables may contain secrets such as API keys or database and registry credentials. We believe this is part of a series of attacks recently targeting platform companies with the aim of compromising AI inference providers. We have notified these upstream providers to revoke all keys proactively, as we take these kinds of events extremely seriously. What you should do Immediately revoke and reissue all environment variables, including any API keys, stored in Railway. If you have any credentials on an external registry, . Review logs for those services for unusual activity. Until builds are restored, you will not be able to roll out new versions. We apologize for this inconvenience. Follow this incident to be notified when builds resume and for further updates. We will provide new updates on this announcement, and on status.railway.com as we gather all facts about the scope of impact. Manage email preferences © 2026 Railway Corp. All rights reserved.